Ticket ID: SIXXS #944036 Ticket Status: Resolved PoP: nlhaa01 - Leaseweb B.V. (Haarlem)
nlhaa01 routing issues
Shadow Hawkins on Saturday, 17 January 2009 15:36:10
My tunnel works, but beyond nlhaa01 nothing happends:
root@HackBookPro-b00ntu:/home/jeroen# traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2001:4860:0:1001::68) from 2001:1af8:fe00:12::2, 30 hops max, 16 byte packets
1 2001:1af8:fe00:12::1 (2001:1af8:fe00:12::1) 34.083 ms 34.014 ms 35.44 ms
2 * 2001:1af8:1:f006:218:74ff:fe46:3200 (2001:1af8:1:f006:218:74ff:fe46:3200) 42.936 ms 34.499 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 *^C
root@HackBookPro-b00ntu:/home/jeroen#
root@HackBookPro-b00ntu:/home/jeroen# traceroute6 sixxs.net
traceroute to sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:1af8:fe00:12::2, 30 hops max, 16 byte packets
1 2001:1af8:fe00:12::1 (2001:1af8:fe00:12::1) 32.284 ms 32.021 ms 32.168 ms
2 2001:1af8:1:f006:218:74ff:fe46:3200 (2001:1af8:1:f006:218:74ff:fe46:3200) 32.766 ms 33.188 ms 34.591 ms
3 * * *
4 * * *
5 * * *
^C
root@HackBookPro-b00ntu:/home/jeroen#
I tested both linux and MacOSX
same failure when I traceroute6 first I thought it was my dodgy routing skills, but I'm afraid its not..
Jeroen
[Admin Edit: Routing issues internally at Leaseweb]
nlhaa01 fails
Shadow Hawkins on Saturday, 17 January 2009 14:09:16
~ $ uname -a
OpenBSD amd4600.flupzor.nl 4.4 GENERIC.MP#2063 amd64
this is OpenBSD -current; latest snapshot.
Network configuration (ifconfig gif0):
gif0: flags=8050<POINTOPOINT,RUNNING,MULTICAST> mtu 1280
priority: 0
groups: gif egress
physical address inet 192.168.0.150 --> 94.75.219.73
inet6 fe80::21d:92ff:fe85:b280%gif0 -> prefixlen 64 scopeid 0x4
inet6 2001:1af8:fe00:29::2 -> 2001:1af8:fe00:29::1 prefixlen 128
routes (route -n show):
Internet6:
Destination Gateway Flags Refs Use Mtu Prio Iface
::/104 ::1 UGRS 0 0 - 8 lo0
::/96 ::1 UGRS 0 0 - 8 lo0
default ::1 GS 0 6091 - 8 gif0
::1 ::1 UH 15 12 33160 4 lo0
::127.0.0.0/104 ::1 UGRS 0 0 - 8 lo0
::224.0.0.0/100 ::1 UGRS 0 0 - 8 lo0
::255.0.0.0/104 ::1 UGRS 0 0 - 8 lo0
::ffff:0.0.0.0/96 ::1 UGRS 0 0 - 8 lo0
2001:1af8:fe00:29::1 2001:1af8:fe00:29::2 H 0 127 - 4 gif0
2001:1af8:fe00:29::2 link#4 UHL 1 4 - 4 lo0
2002::/24 ::1 UGRS 0 0 - 8 lo0
2002:7f00::/24 ::1 UGRS 0 0 - 8 lo0
2002:e000::/20 ::1 UGRS 0 0 - 8 lo0
2002:ff00::/24 ::1 UGRS 0 0 - 8 lo0
fe80::/10 ::1 UGRS 0 0 - 8 lo0
fe80::%re0/64 link#1 UC 0 0 - 4 re0
fe80::21d:92ff:fe85:b280%re0 00:1d:92:85:b2:80 HL 0 0 - 4 lo0
fe80::%lo0/64 fe80::1%lo0 U 0 0 - 4 lo0
fe80::1%lo0 link#3 UHL 0 0 - 4 lo0
fe80::%gif0/64 link#4 C 0 0 - 4 gif0
fe80::21d:92ff:fe85:b280%gif0 link#4 UHL 0 0 - 4 lo0
fec0::/10 ::1 UGRS 0 0 - 8 lo0
ff01::/16 ::1 UGRS 0 0 - 8 lo0
ff01::%re0/32 link#1 UC 0 0 - 4 re0
ff01::%lo0/32 ::1 UC 0 0 - 4 lo0
ff01::%gif0/32 link#4 C 0 0 - 4 gif0
ff02::/16 ::1 UGRS 0 0 - 8 lo0
ff02::%re0/32 link#1 UC 0 0 - 4 re0
ff02::%lo0/32 ::1 UC 0 0 - 4 lo0
ff02::%gif0/32 link#4 C 0 0 - 4 gif0
traceroute:
alex@amd4600.flupzor.nl
~ $ traceroute6 ipv6.google.com
traceroute6 to ipv6.l.google.com (2001:4860:0:1001::68) from 2001:1af8:fe00:29::2, 64 hops max, 12 byte packets
1 2001:1af8:fe00:29::1 7.257 ms 7.445 ms 8.388 ms
2 2001:1af8:1:f006:218:74ff:fe46:3200 7.858 ms 10.162 ms 8.002 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
I have the same problem as Jeroen has.
Yesterday it was still working. This morning it was't working anymore.
Thanks,
Alexander
State change: confirmed
Jeroen Massar on Saturday, 17 January 2009 15:33:18
The state of this ticket has been changed to confirmed
State change: resolved
Jeroen Massar on Saturday, 17 January 2009 22:25:17
The state of this ticket has been changed to resolved
nlhaa01 routing issues
Jeroen Massar on Saturday, 17 January 2009 22:25:55
There was an OSPFv3 issue, the /39 is now in BGP to resolve this. All should be fine again.
Posting is only allowed when you are logged in. |