SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #460890
Ticket Status: Resolved

PoP: nlams05 - SURFnet (Amsterdam)

routing issue
[nl] Shadow Hawkins on Tuesday, 19 December 2006 20:31:46
I have ipv6 connectivity again, but it looks like we still have a routing issue on nlams05. I can't reach my subnet from the outside. A traceroute shows that it doesn't forward the traffic to my router: traceroute6 Results For : 2001:610:6ab::1 1 gw-292.ams-01.nl.sixxs.net (2001:838:300:123::1) 7.089 ms 6.722 ms * 2 2001:838:2:1::1 (2001:838:2:1::1) 6.976 ms 7.178 ms 7.22 ms 3 se2.ams-ix.ipv6.concepts-ict.net (2001:838:0:10::1) 8.381 ms 8.155 ms 8.67 ms 4 XSR03.Asd001A.surf.net (2001:7f8:1::a500:1103:1) 9.054 ms 9.351 ms 9.606 ms 5 AF-500.XSR01.Asd001A.surf.net (2001:610:e08:8::9) 9.817 ms 10.243 ms 12.176 ms 6 surfnet-router.Customer.surf.net (2001:610:f01:9168::170) 9.538 ms 9.439 ms 9.07 ms 7 sixxs.surfnet.nl (2001:610:1:80bb:192:87:102:107) 9.45 ms 10.315 ms 8.868 ms 8 sixxs.surfnet.nl (2001:610:1:80bb:192:87:102:107) 9.584 ms !H 9.94 ms !H 9.291 ms !H
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 19 December 2006 22:26:54
Message is Locked
The state of this ticket has been changed to resolved
routing issue
[ch] Jeroen Massar SixXS Staff on Tuesday, 19 December 2006 22:28:26
6 sixxs.surfnet.nl (2001:610:1:80bb:192:87:102:107) 3.924 ms 3.712 ms 3.718 ms 7 2001:610:6ab::1 (2001:610:6ab::1) 14.705 ms !H 17.679 ms !H 14.222 ms !H The host you are trying to send it to doesn't know where to route it, nothing we can do about. Please configure your network correctly. Next to that read the big green box which clearly reads: -- In the event that there is a problem, include a sufficient description as mentioned in the Reporting Problems section of the contact page, we can not handle the problem otherwise. -- Thus please do so.

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

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