|
Ticket ID: SIXXS #3476105 Ticket Status: Resolved PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)
subnet not working
![[de]](/s/countries/de.gif) Shadow Hawkins on Tuesday, 25 January 2011 18:28:42
Since about 17:00 the subnet routed via my tunnel T18571 does not longer work, only the tunnel endpoint is reachable:
This is from an external server to the tunnel endpoint:
traceroute to 2a01:198:200:2be::2 (2a01:198:200:2be::2) from 2a01:238:42b4:5300::53, port 33434, from port 38405, 30 hops max, 60 byte packets
1 2a01:238:4000::2 1.794 ms * *
2 2a01:238:b:105::1 3.311 ms 2.290 ms 2.598 ms
3 2a01:238:0:b1a3::2 14.030 ms 13.028 ms 13.230 ms
4 2001:7f8::a2dc:0:1 15.874 ms 14.926 ms 14.370 ms
5 2001:7f8:8::85b1:0:1 13.284 ms 13.994 ms 13.686 ms
6 2a01:198:200::2 15.427 ms 15.620 ms 15.082 ms
7 2a01:198:200:2be::2 28.630 ms 38.949 ms 30.259 ms
And this is to an IP inside my subnet:
traceroute to 2a01:198:329:1::1 (2a01:198:329:1::1) from 2a01:238:42b4:5300::53, port 33434, from port 38113, 30 hops max, 60 byte packets
1 2a01:238:4000::2 28.015 ms 4.439 ms *
2 2a01:238:b:105::1 2.458 ms 1.346 ms 2.977 ms
3 2a01:238:0:b1a3::2 14.393 ms 13.021 ms 13.005 ms
4 2001:7f8::a2dc:0:1 14.854 ms 14.404 ms 15.076 ms
5 2001:7f8:8::85b1:0:1 14.254 ms 13.240 ms 13.082 ms
6 2a01:198:200::2 14.852 ms !N 19.559 ms !N 15.399 ms !N
And here from the inside, first from the router with the tunnel endpoint:
traceroute to 2a01:238:42b4:5300::53 (2a01:238:42b4:5300::53) from 2a01:198:200:2be::2, port 33434, from port 50774, 30 hops max, 60 byte packets
1 2a01:198:200:2be::1 18.051 ms 15.001 ms 13.996 ms
2 2a01:198:200::1 17.049 ms 18.882 ms 14.859 ms
3 2001:7f8:8::1536:0:1 18.911 ms 19.594 ms 23.871 ms
4 2001:748:0:15::1 23.845 ms 30.253 ms 27.162 ms
5 2001:748:0:1::206 30.847 ms 27.209 ms 21.696 ms
6 2001:748:0:1f::2 30.524 ms 24.203 ms 21.204 ms
7 2001:748:10:1::2 29.033 ms 30.374 ms 49.879 ms
8 2a01:238:b:205::2 30.287 ms 50.202 ms 32.489 ms
9 2a01:238:42b4:5300::53 50.218 ms 44.473 ms 33.060 ms
And now from a system inside the subnet:
traceroute to 2a01:238:42b4:5300::53 (2a01:238:42b4:5300::53) from 2a01:198:329:1::14, port 33434, from port 59440, 30 hops max, 60 byte packets
1 2a01:198:329:1::1 0.138 ms 0.129 ms 0.147 ms
2 * * *
3 * * *
4 * * *
5 * * *
tshark shows packets are leaving my router via the tunnel:
1919.947667 2a01:198:329:1::14 -> 2a01:238:42b4:5300::53 UDP Source port: 59440 Destination port: 33439
1919.947720 2a01:198:329:1::14 -> 2a01:238:42b4:5300::53 UDP Source port: 59440 Destination port: 33440
1919.947745 2a01:198:329:1::14 -> 2a01:238:42b4:5300::53 UDP Source port: 59440 Destination port: 33441
1924.948548 2a01:198:329:1::14 -> 2a01:238:42b4:5300::53 UDP Source port: 59440 Destination port: 33440
1924.948579 2a01:198:329:1::14 -> 2a01:238:42b4:5300::53 UDP Source port: 59440 Destination port: 33441
1924.948603 2a01:198:329:1::14 -> 2a01:238:42b4:5300::53 UDP Source port: 59440 Destination port: 33442
This look familiar to #3402205.
subnet not working
Shadow Hawkins on Tuesday, 25 January 2011 18:42:54
Whoever just kicked the PoP back into life: Thank you.
Everything seems to be working again, the subnet is routed correctly now:
traceroute to 2a01:198:329:1::1 (2a01:198:329:1::1) from 2a01:238:42b4:5300::53, port 33434, from port 54669, 30 hops max, 60 byte packets
1 * * *
2 2a01:238:b:105::1 2.329 ms 1.476 ms 1.498 ms
3 2a01:238:0:b1a3::2 14.053 ms 14.110 ms 12.999 ms
4 2001:7f8::a2dc:0:1 14.196 ms 13.852 ms 15.588 ms
5 2001:7f8:8::85b1:0:1 13.044 ms 13.497 ms 14.505 ms
6 2a01:198:200::2 13.579 ms 14.611 ms 14.496 ms
7 2a01:198:329:1::1 31.275 ms 33.219 ms 29.992 ms
subnet not working
As I was cooking & eating... it was not me.
Do note that the PoPs are reconfigured automatically thus if something sneak up, it might be resolved by the reconfiguration. The bigger question is why the route went missing in the first place though.
State change: resolved
The state of this ticket has been changed to resolved
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 25 January 2011 19:40:28
Posting is only allowed when you are