• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Ubuntu 11.10 ping6 problem

Started by JeanPascal, November 30, 2011, 02:19:39 PM

Previous topic - Next topic

JeanPascal

Hello,

i have Ubuntu 11.10 and no router before my server - direct on cable modem

when i do ping6 ipv6.google.com
it only starts after a few moments..
then its fine.. if i stop and wait just a few seconds its working.. if i wait 2-3min.. same procedure..
from otherside TO me its the same thing..

It looks like the tunnel is not up every time ?

cholzhauer

Are you running a firewall on your Ubuntu machine?

JeanPascal

No, no firewall

i also tested with MTU 1480, 1280 ,576.. no chance :(

JeanPascal

Here is a tcpdump while i am starting ping6 ipv6.google.com
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
21:07:36.896005 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 2, length 64
21:07:37.904006 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 3, length 64
21:07:38.912002 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 4, length 64
21:07:39.920019 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 5, length 64
21:07:40.928018 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 6, length 64
21:07:41.936021 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 7, length 64
21:07:42.944024 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 8, length 64
21:07:43.952030 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 9, length 64
21:07:43.964220 IP6 fra07s07-in-x67.1e100.net > ipv6.x86.be: ICMP6, echo reply, seq 9, length 64
21:07:47.973232 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 13, length 64
21:07:47.985209 IP6 fra07s07-in-x67.1e100.net > ipv6.x86.be: ICMP6, echo reply, seq 13, length 64
21:07:48.975161 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 14, length 64
21:07:48.987063 IP6 fra07s07-in-x67.1e100.net > ipv6.x86.be: ICMP6, echo reply, seq 14, length 64
21:07:49.976295 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 15, length 64
21:07:50.005102 IP6 fra07s07-in-x67.1e100.net > ipv6.x86.be: ICMP6, echo reply, seq 15, length 64
21:07:50.976398 IP6 ipv6.x86.be > fra07s07-in-x67.1e100.net: ICMP6, echo request, seq 16, length 64
21:07:51.005341 IP6 fra07s07-in-x67.1e100.net > ipv6.x86.be: ICMP6, echo reply, seq 16, length 64


kasperd

A traceroute from my end confirms that the connection between the tunnel server on 216.66.80.30 / 2001:470:0:69::2 and your gateway on 2001:470:1f0b:1140::2 is flaky. That is all I can see from here, it doesn't give me much hint about where the problem is. And I don't know the IPv4 address of your end of the tunnel, so I can't traceroute your IPv4 address to see if it is an IPv4 problem.

Your tcpdump is not as useful as it could have been. Instead of running a tcpdump on the virtual interface try running it on the physical interface that carries the traffic. Run it with -n such that DNS lookups aren't going to mess with the outcome.

In addition try to ping the IPv4 and IPv6 addresses of the tunnel server.

JeanPascal

Ok i got news..

i run ping6 ipv6.x86.be from another host while tcpdump was running... view this:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
20:06:13.125906 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 1, length 64
20:06:14.126998 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 2, length 64
20:06:15.128073 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 3, length 64
20:06:16.129252 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 4, length 64
20:06:17.129021 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 5, length 64
20:06:18.129109 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 6, length 64
20:06:19.129205 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 7, length 64
20:06:20.129299 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 8, length 64
20:06:21.128953 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 9, length 64
20:06:22.129049 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 10, length 64
20:06:22.129085 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2607:ff50:0:12::15cf:bea6: ICMP6, echo reply, seq 10, length 64
20:06:23.130339 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 11, length 64
20:06:24.129668 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 12, length 64
20:06:25.129763 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 13, length 64
20:06:26.129860 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 14, length 64
20:06:27.129525 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 15, length 64
20:06:27.129551 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2607:ff50:0:12::15cf:bea6: ICMP6, echo reply, seq 15, length 64
20:06:28.128989 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 16, length 64
20:06:28.129015 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2607:ff50:0:12::15cf:bea6: ICMP6, echo reply, seq 16, length 64
20:06:29.129731 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 17, length 64
20:06:29.129756 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2607:ff50:0:12::15cf:bea6: ICMP6, echo reply, seq 17, length 64
20:06:30.130667 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 18, length 64
20:06:30.130692 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2607:ff50:0:12::15cf:bea6: ICMP6, echo reply, seq 18, length 64
20:06:31.131602 IP 216.66.80.30 > 78.94.28.93: IP6 2607:ff50:0:12::15cf:bea6 > 2001:470:1f0b:1140::2: ICMP6, echo request, seq 19, length 64
20:06:31.131627 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2607:ff50:0:12::15cf:bea6: ICMP6, echo reply, seq 19, length 64

any idea why it only replys after a few packages?

JeanPascal

When i do ping6 from the sysstem:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
20:09:46.259833 IP 78.94.28.93.50931 > 80.69.100.230.53: 54853+ AAAA? ipv6.google.com. (33)
20:09:46.267336 IP 80.69.100.230.53 > 78.94.28.93.50931: 54853 2/0/0 CNAME ipv6.l.google.com., AAAA 2a00:1450:8007::68 (82)
20:09:46.267591 IP 78.94.28.93.45694 > 80.69.100.230.53: 16983+ PTR? 8.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.0.0.8.0.5.4.1.0.0.a.2.ip6.arpa. (90)
20:09:46.285795 IP 80.69.100.230.53 > 78.94.28.93.45694: 16983 1/0/0 PTR fx-in-x68.1e100.net. (123)
20:09:54.349229 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2a00:1450:8007::68: ICMP6, echo request, seq 9, length 64
20:09:54.360297 IP 216.66.80.30 > 78.94.28.93: IP6 2a00:1450:8007::68 > 2001:470:1f0b:1140::2: ICMP6, echo reply, seq 9, length 64
20:09:54.360436 IP 78.94.28.93.52117 > 80.69.100.230.53: 50200+ PTR? 8.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.0.0.8.0.5.4.1.0.0.a.2.ip6.arpa. (90)
20:09:54.366786 IP 80.69.100.230.53 > 78.94.28.93.52117: 50200 1/0/0 PTR fx-in-x68.1e100.net. (123)
20:09:58.351232 IP 78.94.28.93.33226 > 80.69.100.230.53: 10781+ PTR? 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.1.1.b.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. (90)
20:09:58.357731 IP 80.69.100.230.53 > 78.94.28.93.33226: 10781 1/0/0 PTR ipv6.x86.be. (115)
20:09:58.357893 IP 78.94.28.93.38457 > 80.69.100.230.53: 2597+ PTR? 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.1.1.b.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. (90)
20:09:58.363715 IP 80.69.100.230.53 > 78.94.28.93.38457: 2597 1/0/0 PTR ipv6.x86.be. (115)
20:09:58.363872 IP 78.94.28.93.57583 > 80.69.100.230.53: 55340+ PTR? 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.1.1.b.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa. (90)
20:09:58.369746 IP 80.69.100.230.53 > 78.94.28.93.57583: 55340 1/0/0 PTR ipv6.x86.be. (115)
20:09:58.369855 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2a00:1450:8007::68: ICMP6, echo request, seq 13, length 64
20:09:58.382125 IP 216.66.80.30 > 78.94.28.93: IP6 2a00:1450:8007::68 > 2001:470:1f0b:1140::2: ICMP6, echo reply, seq 13, length 64
20:09:58.382256 IP 78.94.28.93.34911 > 80.69.100.230.53: 45670+ PTR? 8.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.0.0.8.0.5.4.1.0.0.a.2.ip6.arpa. (90)
20:09:58.387755 IP 80.69.100.230.53 > 78.94.28.93.34911: 45670 1/0/0 PTR fx-in-x68.1e100.net. (123)
20:09:59.370853 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2a00:1450:8007::68: ICMP6, echo request, seq 14, length 64
20:09:59.380929 IP 216.66.80.30 > 78.94.28.93: IP6 2a00:1450:8007::68 > 2001:470:1f0b:1140::2: ICMP6, echo reply, seq 14, length 64
20:09:59.381059 IP 78.94.28.93.53453 > 80.69.100.230.53: 51811+ PTR? 8.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.0.0.8.0.5.4.1.0.0.a.2.ip6.arpa. (90)
20:09:59.388274 IP 80.69.100.230.53 > 78.94.28.93.53453: 51811 1/0/0 PTR fx-in-x68.1e100.net. (123)
20:10:00.372390 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2a00:1450:8007::68: ICMP6, echo request, seq 15, length 64
20:10:00.383578 IP 216.66.80.30 > 78.94.28.93: IP6 2a00:1450:8007::68 > 2001:470:1f0b:1140::2: ICMP6, echo reply, seq 15, length 64
20:10:00.383708 IP 78.94.28.93.56328 > 80.69.100.230.53: 14970+ PTR? 8.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.0.0.8.0.5.4.1.0.0.a.2.ip6.arpa. (90)
20:10:00.389729 IP 80.69.100.230.53 > 78.94.28.93.56328: 14970 1/0/0 PTR fx-in-x68.1e100.net. (123)
20:10:01.373843 IP 78.94.28.93 > 216.66.80.30: IP6 2001:470:1f0b:1140::2 > 2a00:1450:8007::68: ICMP6, echo request, seq 16, length 64
20:10:01.385820 IP 216.66.80.30 > 78.94.28.93: IP6 2a00:1450:8007::68 > 2001:470:1f0b:1140::2: ICMP6, echo reply, seq 16, length 64
20:10:01.385951 IP 78.94.28.93.51627 > 80.69.100.230.53: 22554+ PTR? 8.6.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.0.0.8.0.5.4.1.0.0.a.2.ip6.arpa. (90)
20:10:01.391885 IP 80.69.100.230.53 > 78.94.28.93.51627: 22554 1/0/0 PTR fx-in-x68.1e100.net. (123)