Strange IPv6 reachability problem

Jeroen Massar jeroen at unfix.org
Mon Jun 20 00:38:36 CEST 2011


On 2011-06-20 00:19 , Seth Mattinen wrote:
[..]
> I *can not* reach it from a server at my parent's house:
> 
> source: 2607:fe70:1002:0:202:b3ff:fe30:f633
> dest: 2001:500:61:28::70
> 
> PING 2001:500:61:28::70(2001:500:61:28::70) 56 data bytes

I suggest you try this magical tool called 'traceroute' or if available
tracepath6 it will open your eyes.

traceroute to 2607:fe70:1002:0:202:b3ff:fe30:f633
[..]
14  2607:fe70::4:2 (2607:fe70::4:2)  169.402 ms
sl-gw34-stk-se10-0-2-out.v6.sprintlink.net (2600:6:300::7)  167.318 ms
2607:fe70::4:2 (2607:fe70::4:2)  168.976 ms
15  2607:fe70::4:2 (2607:fe70::4:2)  168.145 ms 2607:fe70::a:2
(2607:fe70::a:2)  170.529 ms 2607:fe70::4:2 (2607:fe70::4:2)  167.835 ms
16  2607:fe70::a:2 (2607:fe70::a:2)  169.900 ms  170.066 ms
2607:fe70::5:1 (2607:fe70::5:1)  170.408 ms
17  2607:fe70::14:2 (2607:fe70::14:2)  175.853 ms 2607:fe70::5:1
(2607:fe70::5:1)  169.892 ms  169.682 ms
18  2607:fe70::14:2 (2607:fe70::14:2)  170.746 ms  175.756 ms  172.394 ms
19  2607:fe70:1001::2 (2607:fe70:1001::2)  178.461 ms  178.177 ms *
20  2607:fe70:1001::2 (2607:fe70:1001::2)  180.631 ms !N  177.091 ms !N
 177.261 ms !N

As you can see one of the boxes close to it does not know what to do
with it.

[..]
> nfdump filter:
> proto icmp6 and host 2001:500:61:28::70

Where on the network are you getting netflow from and why not just
tcpdump which can give you per packet details, avoiding any issues that
might be on the netflow level.

Anyway, above is your answer already.

Greets,
 Jeroen


More information about the ipv6-ops mailing list