ping 172.16.2.14 PING 172.16.2.14 (172.16.2.14): 56 data bytes 64 bytes from 172.16.2.14: seq=0 ttl=64 time=93.543 ms 64 bytes from 172.16.2.14: seq=1 ttl=64 time=97.719 ms 64 bytes from 172.16.2.14: seq=2 ttl=64 time=84.322 ms 64 bytes from 172.16.2.14: seq=3 ttl=64 time=86.741 ms 64 bytes from 172.16.2.14: seq=4 ttl=64 time=84.384 ms 64 bytes from 172.16.2.14: seq=5 ttl=64 time=92.789 ms 64 bytes from 172.16.2.14: seq=6 ttl=64 time=92.552 ms 64 bytes from 172.16.2.14: seq=7 ttl=64 time=85.477 ms 64 bytes from 172.16.2.14: seq=8 ttl=64 time=84.115 ms 64 bytes from 172.16.2.14: seq=9 ttl=64 time=82.746 ms 64 bytes from 172.16.2.14: seq=10 ttl=64 time=82.404 ms 64 bytes from 172.16.2.14: seq=11 ttl=64 time=83.059 ms 64 bytes from 172.16.2.14: seq=12 ttl=64 time=82.839 ms 64 bytes from 172.16.2.14: seq=13 ttl=64 time=84.569 ms 64 bytes from 172.16.2.14: seq=14 ttl=64 time=82.126 ms 64 bytes from 172.16.2.14: seq=15 ttl=64 time=84.781 ms 64 bytes from 172.16.2.14: seq=16 ttl=64 time=81.558 ms 64 bytes from 172.16.2.14: seq=17 ttl=64 time=92.970 ms
Pings from the server to the client gradually decrease then spike in a repeating pattern:
PING 172.16.2.30 (172.16.2.30) 56(84) bytes of data. 64 bytes from 172.16.2.30: icmp_req=1 ttl=64 time=79.0 ms 64 bytes from 172.16.2.30: icmp_req=2 ttl=64 time=358 ms 64 bytes from 172.16.2.30: icmp_req=3 ttl=64 time=317 ms 64 bytes from 172.16.2.30: icmp_req=4 ttl=64 time=275 ms 64 bytes from 172.16.2.30: icmp_req=5 ttl=64 time=236 ms 64 bytes from 172.16.2.30: icmp_req=6 ttl=64 time=201 ms 64 bytes from 172.16.2.30: icmp_req=7 ttl=64 time=150 ms 64 bytes from 172.16.2.30: icmp_req=8 ttl=64 time=110 ms 64 bytes from 172.16.2.30: icmp_req=9 ttl=64 time=389 ms 64 bytes from 172.16.2.30: icmp_req=10 ttl=64 time=348 ms 64 bytes from 172.16.2.30: icmp_req=11 ttl=64 time=306 ms 64 bytes from 172.16.2.30: icmp_req=12 ttl=64 time=265 ms 64 bytes from 172.16.2.30: icmp_req=13 ttl=64 time=224 ms 64 bytes from 172.16.2.30: icmp_req=14 ttl=64 time=182 ms 64 bytes from 172.16.2.30: icmp_req=15 ttl=64 time=140 ms 64 bytes from 172.16.2.30: icmp_req=16 ttl=64 time=100 ms 64 bytes from 172.16.2.30: icmp_req=17 ttl=64 time=378 ms 64 bytes from 172.16.2.30: icmp_req=18 ttl=64 time=337 ms 64 bytes from 172.16.2.30: icmp_req=19 ttl=64 time=297 ms 64 bytes from 172.16.2.30: icmp_req=20 ttl=64 time=254 ms 64 bytes from 172.16.2.30: icmp_req=21 ttl=64 time=214 ms 64 bytes from 172.16.2.30: icmp_req=22 ttl=64 time=172 ms 64 bytes from 172.16.2.30: icmp_req=23 ttl=64 time=130 ms 64 bytes from 172.16.2.30: icmp_req=24 ttl=64 time=89.1 ms 64 bytes from 172.16.2.30: icmp_req=25 ttl=64 time=367 msI've enabled logging at level 7 on both client and server, but don't see anything interesting. This one-way graduating latency is quite consistent. I'm hoping someone will see this pattern and know what's causing it.
Thanks. -Randall
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
