SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #845384
Ticket Status: User

PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)

Packet loss / severe latency over tunnel
[us] Shadow Hawkins on Monday, 10 November 2008 14:28:19
Folks: My tunnel was set up earlier today (T17876) and while the tunnel comes up just fine, there is either some bad packet loss or latency over the tunnel. There does not appear to be any issues between me and the PoP over IPv4, and I can ping my own endpoint just fine. Various command outputs follow since "aiccu test" displays nothing at all on my system. Let me know if you need more info and as always thanks for your time. # ifconfig eth0 Link encap:Ethernet HWaddr 00:b0:d0:71:4b:fb inet addr:10.50.1.76 Bcast:10.50.7.255 Mask:255.255.248.0 inet6 addr: fe80::2b0:d0ff:fe71:4bfb/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21013302 errors:0 dropped:0 overruns:1 frame:0 TX packets:13885184 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1122600222 (1.0 GiB) TX bytes:2508436607 (2.3 GiB) Interrupt:5 Base address:0xe800 eth1 Link encap:Ethernet HWaddr 00:01:02:2b:f2:4b inet addr:192.168.8.1 Bcast:192.168.8.255 Mask:255.255.255.0 inet6 addr: fe80::201:2ff:fe2b:f24b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10800665 errors:2 dropped:0 overruns:84 frame:2 TX packets:9848894 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1815089087 (1.6 GiB) TX bytes:2626810198 (2.4 GiB) Interrupt:10 Base address:0x2c00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:18703882 errors:0 dropped:0 overruns:0 frame:0 TX packets:18703882 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1266788571 (1.1 GiB) TX bytes:1266788571 (1.1 GiB) sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: 2001:4978:f:1dd::2/64 Scope:Global inet6 addr: fe80::4878:f:1dd:2/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1 RX packets:45 errors:0 dropped:0 overruns:0 frame:0 TX packets:50 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:4680 (4.5 KiB) TX bytes:5200 (5.0 KiB) # ip -6 route show 2001:4978:f:1dd::/64 dev sixxs metric 256 expires 21334039sec mtu 1280 advmss 1220 hoplimit 4294967295 fe80::/64 dev eth1 metric 256 expires 20076317sec mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0 metric 256 expires 20731146sec mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev sixxs metric 256 expires 21334039sec mtu 1280 advmss 1220 hoplimit 4294967295 ff00::/8 dev eth1 metric 256 expires 20076317sec mtu 1500 advmss 1440 hoplimit 4294967295 ff00::/8 dev eth0 metric 256 expires 20731146sec mtu 1500 advmss 1440 hoplimit 4294967295 ff00::/8 dev sixxs metric 256 expires 21334039sec mtu 1280 advmss 1220 hoplimit 4294967295 default via 2001:4978:f:1dd::1 dev sixxs metric 1024 expires 21334039sec mtu 1280 advmss 1220 hoplimit 4294967295 # netstat -unp Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name udp 0 0 10.50.1.76:1037 216.14.98.22:5072 ESTABLISHED 875/aiccu # ping -c15 216.14.98.22 PING 216.14.98.22 (216.14.98.22) 56(84) bytes of data. 64 bytes from 216.14.98.22: icmp_seq=1 ttl=50 time=24.5 ms 64 bytes from 216.14.98.22: icmp_seq=2 ttl=50 time=23.2 ms 64 bytes from 216.14.98.22: icmp_seq=3 ttl=50 time=23.9 ms 64 bytes from 216.14.98.22: icmp_seq=4 ttl=50 time=23.2 ms 64 bytes from 216.14.98.22: icmp_seq=5 ttl=50 time=24.8 ms 64 bytes from 216.14.98.22: icmp_seq=6 ttl=50 time=23.8 ms 64 bytes from 216.14.98.22: icmp_seq=7 ttl=50 time=23.1 ms 64 bytes from 216.14.98.22: icmp_seq=8 ttl=50 time=22.9 ms 64 bytes from 216.14.98.22: icmp_seq=9 ttl=50 time=22.6 ms 64 bytes from 216.14.98.22: icmp_seq=10 ttl=50 time=22.2 ms 64 bytes from 216.14.98.22: icmp_seq=11 ttl=50 time=22.3 ms 64 bytes from 216.14.98.22: icmp_seq=12 ttl=50 time=22.4 ms 64 bytes from 216.14.98.22: icmp_seq=13 ttl=50 time=22.8 ms 64 bytes from 216.14.98.22: icmp_seq=14 ttl=50 time=26.1 ms 64 bytes from 216.14.98.22: icmp_seq=15 ttl=50 time=22.3 ms --- 216.14.98.22 ping statistics --- 15 packets transmitted, 15 received, 0% packet loss, time 14005ms rtt min/avg/max/mdev = 22.282/23.389/26.106/1.086 ms # ping6 -c15 2001:4978:f:1dd::2 PING 2001:4978:f:1dd::2(2001:4978:f:1dd::2) 56 data bytes 64 bytes from 2001:4978:f:1dd::2: icmp_seq=1 ttl=64 time=0.091 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=2 ttl=64 time=0.064 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=3 ttl=64 time=0.098 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=4 ttl=64 time=0.092 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=5 ttl=64 time=0.076 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=6 ttl=64 time=0.095 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=7 ttl=64 time=0.092 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=8 ttl=64 time=0.093 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=9 ttl=64 time=0.102 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=10 ttl=64 time=0.080 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=11 ttl=64 time=0.095 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=12 ttl=64 time=0.093 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=13 ttl=64 time=0.078 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=14 ttl=64 time=0.089 ms 64 bytes from 2001:4978:f:1dd::2: icmp_seq=15 ttl=64 time=0.088 ms --- 2001:4978:f:1dd::2 ping statistics --- 15 packets transmitted, 15 received, 0% packet loss, time 13999ms rtt min/avg/max/mdev = 0.064/0.088/0.102/0.012 ms # ping6 -c15 2001:4978:f:1dd::1 PING 2001:4978:f:1dd::1(2001:4978:f:1dd::1) 56 data bytes 64 bytes from 2001:4978:f:1dd::1: icmp_seq=1 ttl=64 time=20313 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=2 ttl=64 time=19305 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=3 ttl=64 time=18305 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=4 ttl=64 time=17305 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=5 ttl=64 time=16306 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=6 ttl=64 time=15306 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=7 ttl=64 time=14306 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=8 ttl=64 time=13306 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=9 ttl=64 time=12306 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=10 ttl=64 time=11307 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=11 ttl=64 time=10307 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=12 ttl=64 time=9307 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=13 ttl=64 time=8307 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=14 ttl=64 time=7307 ms 64 bytes from 2001:4978:f:1dd::1: icmp_seq=15 ttl=64 time=6308 ms --- 2001:4978:f:1dd::1 ping statistics --- 15 packets transmitted, 15 received, 0% packet loss, time 14009ms rtt min/avg/max/mdev = 6308.198/13307.318/20313.729/4320.553 ms, pipe 15
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Monday, 10 November 2008 15:06:46
Message is Locked
The state of this ticket has been changed to user
Packet loss / severe latency over tunnel
[ch] Jeroen Massar SixXS Staff on Monday, 10 November 2008 15:12:48
I can't reproduce this, do you have more data?
Packet loss / severe latency over tunnel
[us] Shadow Hawkins on Monday, 10 November 2008 16:44:19
Actually, I can't reproduce it anymore either. Maybe it was related to the initial setup of the tunnel. Anyway, sorry for the bother, everything is working great now.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker