Show Posts
1
Troubleshooting / Strange delay through wan interface - KVM
« on: March 03, 2015, 09:37:26 PM »
Hello.
I have a problem with wanos.
Could you please give an advice?
I have a configuration with wanos VM and proxy VM on virtualization server.
Network looks like this:
HOST -<bridge>- (lan) WANOS (wan) -<bridge>- PROXY
Sometimes ping from WANOS to PROXY through the wan interface looks like this:
In the same time ping from WANOS to HOST through lan looks fine:
I can see very accurate delay (30 seconds, 29, 28, etc) between WANOS and PROXY.
It's very strange, because they connected directly.
They are don't have heavy load, and there are no traffic between them, only ping.
I noticed that this problem only through wan interface.
Maybe WANOS generate delay in some circumstances?
details:
HOST OS: ubuntu 14.04
HOST VM type: libvirt+qemu-kvm
WANOS ver: 1.4.1
PROXY OS: ubuntu 14.04
bridge stp: off (i tried on and off)
I have a problem with wanos.
Could you please give an advice?
I have a configuration with wanos VM and proxy VM on virtualization server.
Network looks like this:
HOST -<bridge>- (lan) WANOS (wan) -<bridge>- PROXY
Sometimes ping from WANOS to PROXY through the wan interface looks like this:
Code: [Select]
tc@wanos:~$ ping 10.250.254.3
PING 10.250.254.3 (10.250.254.3): 56 data bytes
64 bytes from 10.250.254.3: seq=18 ttl=64 time=21004.807 ms
64 bytes from 10.250.254.3: seq=19 ttl=64 time=20004.707 ms
64 bytes from 10.250.254.3: seq=20 ttl=64 time=19003.630 ms
64 bytes from 10.250.254.3: seq=21 ttl=64 time=18003.504 ms
64 bytes from 10.250.254.3: seq=22 ttl=64 time=17003.300 ms
64 bytes from 10.250.254.3: seq=23 ttl=64 time=16003.196 ms
64 bytes from 10.250.254.3: seq=24 ttl=64 time=15003.083 ms
64 bytes from 10.250.254.3: seq=25 ttl=64 time=14002.993 ms
64 bytes from 10.250.254.3: seq=26 ttl=64 time=13002.876 ms
64 bytes from 10.250.254.3: seq=27 ttl=64 time=12002.761 ms
64 bytes from 10.250.254.3: seq=28 ttl=64 time=11002.689 ms
64 bytes from 10.250.254.3: seq=29 ttl=64 time=10002.627 ms
64 bytes from 10.250.254.3: seq=30 ttl=64 time=9002.477 ms
64 bytes from 10.250.254.3: seq=31 ttl=64 time=8002.272 ms
64 bytes from 10.250.254.3: seq=32 ttl=64 time=7002.107 ms
64 bytes from 10.250.254.3: seq=33 ttl=64 time=6001.997 ms
64 bytes from 10.250.254.3: seq=34 ttl=64 time=5001.834 ms
64 bytes from 10.250.254.3: seq=35 ttl=64 time=4001.695 ms
64 bytes from 10.250.254.3: seq=36 ttl=64 time=3001.530 ms
64 bytes from 10.250.254.3: seq=37 ttl=64 time=2001.370 ms
64 bytes from 10.250.254.3: seq=38 ttl=64 time=1001.267 ms
64 bytes from 10.250.254.3: seq=40 ttl=64 time=28009.804 ms
64 bytes from 10.250.254.3: seq=41 ttl=64 time=27009.673 ms
64 bytes from 10.250.254.3: seq=42 ttl=64 time=26009.510 ms
64 bytes from 10.250.254.3: seq=43 ttl=64 time=25009.394 ms
64 bytes from 10.250.254.3: seq=44 ttl=64 time=24009.448 ms
64 bytes from 10.250.254.3: seq=45 ttl=64 time=23009.321 ms
64 bytes from 10.250.254.3: seq=46 ttl=64 time=22009.173 ms
64 bytes from 10.250.254.3: seq=47 ttl=64 time=21009.041 ms
64 bytes from 10.250.254.3: seq=48 ttl=64 time=20008.946 ms
64 bytes from 10.250.254.3: seq=49 ttl=64 time=19008.809 ms
64 bytes from 10.250.254.3: seq=50 ttl=64 time=18008.672 ms
64 bytes from 10.250.254.3: seq=51 ttl=64 time=17008.527 ms
64 bytes from 10.250.254.3: seq=52 ttl=64 time=16008.402 ms
64 bytes from 10.250.254.3: seq=53 ttl=64 time=15008.245 ms
64 bytes from 10.250.254.3: seq=54 ttl=64 time=14008.103 ms
64 bytes from 10.250.254.3: seq=55 ttl=64 time=13008.033 ms
64 bytes from 10.250.254.3: seq=68 ttl=64 time=31005.465 ms
64 bytes from 10.250.254.3: seq=69 ttl=64 time=30005.320 ms
64 bytes from 10.250.254.3: seq=70 ttl=64 time=29005.229 ms
64 bytes from 10.250.254.3: seq=71 ttl=64 time=28005.096 ms
64 bytes from 10.250.254.3: seq=72 ttl=64 time=27004.903 ms
64 bytes from 10.250.254.3: seq=73 ttl=64 time=26004.760 ms
64 bytes from 10.250.254.3: seq=74 ttl=64 time=25004.613 ms
64 bytes from 10.250.254.3: seq=75 ttl=64 time=24004.519 ms
64 bytes from 10.250.254.3: seq=76 ttl=64 time=23004.373 ms
64 bytes from 10.250.254.3: seq=77 ttl=64 time=22004.235 ms
64 bytes from 10.250.254.3: seq=78 ttl=64 time=21004.128 ms
64 bytes from 10.250.254.3: seq=79 ttl=64 time=20004.005 ms
64 bytes from 10.250.254.3: seq=80 ttl=64 time=19003.870 ms
64 bytes from 10.250.254.3: seq=81 ttl=64 time=18003.674 ms
64 bytes from 10.250.254.3: seq=82 ttl=64 time=17003.534 ms
In the same time ping from WANOS to HOST through lan looks fine:
Code: [Select]
tc@wanos:~$ ping 10.250.254.1
PING 10.250.254.1 (10.250.254.1): 56 data bytes
64 bytes from 10.250.254.1: seq=0 ttl=64 time=0.522 ms
64 bytes from 10.250.254.1: seq=1 ttl=64 time=0.451 ms
64 bytes from 10.250.254.1: seq=2 ttl=64 time=0.334 ms
64 bytes from 10.250.254.1: seq=3 ttl=64 time=0.380 ms
64 bytes from 10.250.254.1: seq=4 ttl=64 time=0.417 ms
64 bytes from 10.250.254.1: seq=5 ttl=64 time=0.532 ms
64 bytes from 10.250.254.1: seq=6 ttl=64 time=0.526 ms
64 bytes from 10.250.254.1: seq=7 ttl=64 time=0.534 ms
64 bytes from 10.250.254.1: seq=8 ttl=64 time=0.300 ms
64 bytes from 10.250.254.1: seq=9 ttl=64 time=0.308 ms
I can see very accurate delay (30 seconds, 29, 28, etc) between WANOS and PROXY.
It's very strange, because they connected directly.
They are don't have heavy load, and there are no traffic between them, only ping.
I noticed that this problem only through wan interface.
Maybe WANOS generate delay in some circumstances?
details:
HOST OS: ubuntu 14.04
HOST VM type: libvirt+qemu-kvm
WANOS ver: 1.4.1
PROXY OS: ubuntu 14.04
bridge stp: off (i tried on and off)