ping rtt on fw4b

johnpoz

I would expect no delay

Well then you don't understand how stuff works ;) It could be a gawd damn cray super computer, and there is still going to be delay.. Because your adding process!!!

If you don't want the couple of ms of added delay your seeing while doing stuff in VM, then do it all in hardware!

Again think about what is going on here... And your seeing 0.001 extra in your ping.

netgpf

again sorry and thanks again

p.s. however it is not "couple of ms of added delay", delay almost doubled

johnpoz

Do you really think 0.001 is going to be noticeable when your talking to something say .030 seconds away? Really??

stephenw10

Yeah 2ms through a VM is expected. No fault found.

johnpoz

Is not just 1 VM - he has 2, he has a VM talking to another VM on the same host, where this other vm (pfsense) is then routing and natting the traffic (going to be a delay there even in hardware) and then having to software bridge that to the physical nic though through the VM software..

No freaking shit there is going to be a bit of added delay ;)

netgpf

@johnpoz
no no, it was single vm runing on hyper-v pinging physical router

johnpoz

Well maybe hyperV is just crap then ;) I only see around 0.2 ms delay from vms running on my nas, vs the nas itself pinging the physical pfsense.

Some delay is to be expected... unless you were talking 10s of ms I wouldn't be concerned that something is not right.

Are you natting in hyper-v or bridge?

netgpf

These ping results were with bridge.
After your question I switched to natted adapter and surely no delay between two VMs within natted virtual network but then again I would need bridge as said to be able access physical appliances, I mean without modifications to existing LAN.
My problem description is somewhat similar to this one:
https://forum.netgate.com/topic/148937/gateway-increased-ping-latency-depending-on-the-esxi-version-from-the-web-interface-not-from-ssh

Presumably he solved issue with different drivers, but he had like 6ms pings not 2ms.
Should I go to virtualization forum?

P.S. just to clarify:
with natted adapter there is no delay within natted virtual network but there is same delay when pinging LAN gateway.

stephenw10

Yeah 2ms is not something that would concern me but it is a virtualisation issue so better to open a thread there to investigate it.

Steve

johnpoz

When you say natted no delay you mean between vms behind the same natted connection? Or from natted connection to your gateway.. You can still function with a natted network to your physical network. Other than port forwarding from your physical to your natted devices would be required for unsolicited traffic from your physical to your natted vms..

If you feel your VM solution is adding unwarranted extra delay - then yeah you would need to get with your VM software solution support... This has zero to do with pfsense..