My PoP doesn't route my packages? (bug?)
Shadow Hawkins on Tuesday, 21 October 2008 14:13:22
My tunnel is up, the infopage reports no package loss, and I can ping my tunnel endpoint.
But nothing else...
root@Sandnabba.se: /home/emil #> ping6 2001:16d8:ff00:2b9::1
PING 2001:16d8:ff00:2b9::1(2001:16d8:ff00:2b9::1) 56 data bytes
64 bytes from 2001:16d8:ff00:2b9::1: icmp_seq=1 ttl=64 time=31.6 ms
64 bytes from 2001:16d8:ff00:2b9::1: icmp_seq=2 ttl=64 time=31.3 ms
^C
--- 2001:16d8:ff00:2b9::1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 31.357/31.501/31.645/0.144 ms
root@Sandnabba.se: /home/emil #> ping6 ipv6.google.com
PING ipv6.google.com(2001:4860:0:1001::68) 56 data bytes
From cl-698.sto-01.se.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable
From cl-698.sto-01.se.sixxs.net icmp_seq=3 Destination unreachable: Address unreachable
From cl-698.sto-01.se.sixxs.net icmp_seq=4 Destination unreachable: Address unreachable
^C
--- ipv6.google.com ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
My PoP seems to up:
https://www.sixxs.net/misc/traffic/?pop=sesto01&last=1year
root@Sandnabba.se: /home/emil #> route -A inet6 -n
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::1/128 :: U 0 1038 1 lo
2001:16d8:ff00:2b9::/128 :: U 0 0 1 lo
2001:16d8:ff00:2b9::2/128 :: U 0 1922 1 lo
2001:16d8:ff00:2b9::/64 :: U 256 1470 0 sixxs
fe80::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::5b5f:e23e/128 :: U 0 0 1 lo
fe80::201:2ff:fe05:16f7/128 :: U 0 0 1 lo
fe80::21b:11ff:fef1:1c/128 :: U 0 0 1 lo
fe80::/64 :: U 256 0 0 sixxs
fe80::/64 :: U 256 0 0 eth-net
fe80::/64 :: U 256 0 0 eth-loc
ff02::1/128 ff02::1 UC 0 8396 0 eth-loc
ff00::/8 :: U 256 0 0 eth-loc
ff00::/8 :: U 256 0 0 sixxs
ff00::/8 :: U 256 0 0 eth-net
::/0 :: U 256 0 0 eth-loc
::/0 2001:16d8:ff00:2b9::1 UG 1024 269 0 sixxs
Anything wrong somewhere? It worked fine yesterday...
My PoP doesn't route my packages? (bug?)
Jeroen Massar on Tuesday, 21 October 2008 14:40:16 From cl-698.sto-01.se.sixxs.net icmp_seq=2 Destination unreachable: Address unreachable
CL == Client, also known as your endpoint, thus check the routing table, which shows the following problems:
::/0 :: U 256 0 0 eth-loc ::/0 2001:16d8:ff00:2b9::1 UG 1024 269 0 sixxs
Two default routes, and the first one has a lower metric thus wins, and that is where your packets are going to, and then your host figures out that it can't route them, thus indeed it replies with destination unreachable.
Your solution:
#ip -6 ro del default dev eth-loc
(And find out what set that route ;)
My PoP doesn't route my packages? (bug?)
Shadow Hawkins on Tuesday, 21 October 2008 21:53:12
OMG. How could I miss that!?
And then, how did that route came there!? (I think I have to stop geeking all nights ^^ :P)
Thanks!
My PoP doesn't route my packages? (bug?)
Shadow Hawkins on Wednesday, 12 November 2008 13:26:48
I've got an alike problem.... my router is a cisco-2821 and connected via a tunnel to sixx pop dedus01...from the router i can ping the pop endpoint and sixxs
gateway#ping 2A01:198:200:241::1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2A01:198:200:241::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms
gateway#ping www.sixxs.net
Translating "www.sixxs.net"...domain server (192.168.25.1) [OK]
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:838:1:1:210:DCFF:FE20:7C7C, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/43/44 ms
gateway#
i've got an /48 subnet splitted into /64 subnets
on one interface there is a sun solaris 10 server connected and up with an ipv6 address
root@t2000 ~ # ifconfig -a
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.25.1 netmask ffffff00 broadcast 192.168.25.255
ether 0:14:4f:**:**:**
e1000g0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
inet6 fe80::214:****:****:9c2a/10
ether 0:14:4f:**:**:**
e1000g0:1: flags=2080841<UP,RUNNING,MULTICAST,ADDRCONF,IPv6> mtu 1500 index 2
inet6 2a01:198:308:0:214:****:****:9c2a/64
root@t2000 ~ #
but if i ping form solaris to sixxs or to google there will be errors....
sebastian@t2000 ~ # ping -s -A inet6 2A01:198:200:241::1 <--POP ENDPOINT
PING 2A01:198:200:241::1: 56 data bytes
64 bytes from gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1): icmp_seq=0. time=30.0 ms
64 bytes from gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1): icmp_seq=1. time=30.5 ms
64 bytes from gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1): icmp_seq=2. time=30.8 ms
64 bytes from gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1): icmp_seq=3. time=30.0 ms
64 bytes from gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1): icmp_seq=4. time=30.4 ms
64 bytes from gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1): icmp_seq=5. time=31.1 ms
^C
----2A01:198:200:241::1 PING Statistics----
6 packets transmitted, 6 packets received, 0% packet loss
round-trip (ms) min/avg/max/stddev = 30.0/30.5/31.1/0.43
sebastian@t2000 ~ # ping -s -A inet6 www.sixxs.net
PING www.sixxs.net: 56 data bytes
ICMPv6 Address Unreachable from gateway gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1)
for icmp6 from 2a01:198:308:0:214:4fff:fe9d:9c2a to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c)
ICMPv6 Address Unreachable from gateway gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1)
for icmp6 from 2a01:198:308:0:214:4fff:fe9d:9c2a to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c)
ICMPv6 Address Unreachable from gateway gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1)
for icmp6 from 2a01:198:308:0:214:4fff:fe9d:9c2a to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c)
ICMPv6 Address Unreachable from gateway gw-578.dus-01.de.sixxs.net (2a01:198:200:241::1)
for icmp6 from 2a01:198:308:0:214:4fff:fe9d:9c2a to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c)
^C
----www.sixxs.net PING Statistics----
4 packets transmitted, 0 packets received, 100% packet loss
sebastian@t2000 ~ #
so has anyone any suggestion???
My PoP doesn't route my packages? (bug?)
Shadow Hawkins on Wednesday, 12 November 2008 13:42:13
now the problem is solved....i've entered in my cisco the route from 2000::/3 [POP-Endpoint] to ::/0 [POP-Endpoint] and everything is fine
My PoP doesn't route my packages? (bug?)
Jeroen Massar on Wednesday, 12 November 2008 13:50:58
Actually, it had to do with Ticket #847053.
Posting is only allowed when you are logged in. |