SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #994224
Ticket Status: User

PoP: (not applicable)

Subnet R1395 not reachable
[de] Shadow Hawkins on Sunday, 08 March 2009 22:05:59
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: For some days (I'm not sure how long it's been :-(, my Subnet isn't reachable from the Internet. Subnet in question: R1395 (2001:6f8:123d::/48) Used tunnel: T2176 (2001:6f8:900:fd::2 as endpoint on my side) My Handle: JH27-6BONE (Jörg Hoh) Symptoms: * I can ping6 some machines on the ipv6-internet from the machine A which acts as tunnel endpoint on my side * I can ping6 machine A from my workstation and can also ping the IP6 of the tunnel endpoint 2001:6f8:900:fd::2 on machine A. * I cannot ping6 the tunnel endpoint on your side (2001:6f8:900:fd::1) from my workstation. tcpdump on the machine A shows the outgoing requests, but no reply. * Friends report that pinging(6) my workstation from their ipv6-enabled hosts reports "no route to host". Pinging my tunnelendpoint 2001:6f8:900:fd::2 shows no routing problem. I've added the address 2001:6f8:123d:0:20f:eaff:fe2f:a059 to machine A which is running24/7; you can use it for testing purpose, I don't block ping6 on my side. * Subnet R1395 is marked as "enabled" in the webfrontend of This brings me to the conclusion that the routing on your side is broken. Thank you for fixing :-)
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 11 March 2009 21:35:35
Message is Locked
The state of this ticket has been changed to user
Subnet R1395 not reachable
[ch] Jeroen Massar SixXS Staff on Wednesday, 11 March 2009 21:36:03
Should work at the moment. We will be soon (hopefully) upgrading to new sixxsd version and then these kind of issues will be of the past.

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

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