SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #763500
Ticket Status: User

PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)

2001:4978:183:32::/48 routing is broken
[us] Shadow Hawkins on Sunday, 13 July 2008 00:25:03
Hi, This is Jason Roysdon (JRD1-SIXXS). 2001:4978:183::/48 (R6791) appears to be broken. It should be routing to my endpoint 2001:4978:f:12d::2/64 (T15157), which also has 2001:4978:183:32::1 assigned to eth0. It was working just fine a few weeks ago, and now appears to not route in past your.org (this is from another host I have connected via he.net): # traceroute6 2001:4978:183:32::1 traceroute to 2001:4978:183:32::1 (2001:4978:183:32::1), 30 hops max, 40 byte packets 1 jroysdonartoo.tunnel.tserv3.fmt2.ipv6.he.net (2001:470:1f04:366::1) 29.899 ms 31.099 ms 33.359 ms 2 gige-g3-20.core1.fmt2.he.net (2001:470:0:45::1) 35.273 ms 35.146 ms 36.890 ms 3 10gigabitethernet1-1.core1.sjc2.he.net (2001:470:0:31::2) 36.838 ms 37.903 ms 37.856 ms 4 10gigabitethernet1-1.core1.chi1.he.net (2001:470:0:3c::2) 92.463 ms 93.869 ms 93.822 ms 5 2001:470:0:7f::2 (2001:470:0:7f::2) 95.554 ms 102.822 ms 104.588 ms 6 unassigned.v6.your.org (2001:4978:1:400:202:b3ff:feb4:5974) 97.942 ms 90.063 ms 90.101 ms 7 unassigned.v6.your.org (2001:4978:1:400:202:b3ff:feb4:5974) 89.988 ms !H 95.183 ms !H 118.308 ms !H I can ping6 2001:4978:183:32::1 from other hosts on 2001:4978:183:32::/64. I also have routing working going through 2001:4978:183:32::1 to another router 2001:4978:183:32::2 for 2001:4978:183:33::/64, 2001:4978:183:34::/64 and can ping 2001:4978:183:33::1/64 and 2001:4978:183:34::1/64 which means routing is working just fine through 2001:4978:183:32::1. I just can't get traffic back in for anything sourced from 2001:4978:183::/48. Traffic sourced from my endpoint 2001:4978:f:12d::2/64 has no problem, so I know the tunnel is up. I just think nothing is routing back to me. Turning off ip6tables doesn't change anything (plus I'm allowing icmpv6 up to 30 packets per minute even with ip6tables up). I hope that's enough info and the problem is indeed not on my end. Thanks for the free service, Jason Roysdon. sixxs.20080420@jason.roysdon.net +1-209-656-5757
2001:4978:183:32::/48 routing is broken
[ch] Jeroen Massar SixXS Staff on Sunday, 13 July 2008 00:39:31
Please read through the contact page and especially the "Reporting Problems Checklist" section and provide more details. Tracerouting from some random place on the Internet is not very useful. Include the details requested, there is a reason why we ask for those details.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 13 July 2008 00:39:36
Message is Locked
The state of this ticket has been changed to user
2001:4978:183:32::/48 routing is broken
[us] Shadow Hawkins on Sunday, 13 July 2008 01:04:26
"Random site" made it to your.org and then dies. I think that shows enough. However, things are now working (no changes on my end), so I'm assuming someone bounced or reset something on your.org's end to make the route work. Go ahead and close this ticket.
2001:4978:183:32::/48 routing is broken
[us] Shadow Hawkins on Sunday, 13 July 2008 01:05:11
"Random site" made it to your.org and then dies. To me that shows enough since nothing ever changed on my site between working and broken states since the tunnel was first build and the /48 assigned. However, things are now working (again, no changes on my end), so I'm assuming someone bounced or reset something on your.org's end to make the route work. Go ahead and close this ticket.

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

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