|
Ticket ID: SIXXS #9862542 Ticket Status: User PoP: gblon03 - Gyron Internet LTD - Limited UK Company (London)
Tunnel working but /64 subnet not being routed.
![[it]](/s/countries/it.gif) Shadow Hawkins on Saturday, 03 August 2013 23:46:37
This is my situation:
My tunnel 2a00:14f0:e000:130::2 works properly and I'm able to ping it from the outside, e.g.
[root ~]# ping6 2a00:14f0:e000:130::2
PING 2a00:14f0:e000:130::2(2a00:14f0:e000:130::2) 56 data bytes
64 bytes from 2a00:14f0:e000:130::2: icmp_seq=1 ttl=116 time=37.0 ms
According to my SixXS home page, that tunnel has associated a subnet 2a00:14f0:e000:8130::/64, which endpoint corresponds to my tunnel IPv6 (130::2).
However, if I try to traceroute any address in the 8130 subnet, the traceroute stops at the London POP and never reaches my endpoint, e.g.:
[root ~]# tracepath6 2a00:14f0:e000:8130::1 -n
1?: [LOCALHOST] pmtu 1500
1: no reply
2: 2a01:4f8:d12:4::1 1.872ms
3: 2a01:4f8:0:d0:4:0:12:3 0.807ms
4: 2a01:4f8:0:2::1:4 6.687ms
5: 2001:7f8::1b1b:0:1 12.608ms
6: 2001:470:0:225::1 21.041ms
7: 2001:7f8:1::a502:9017:1 20.036ms
8: 2a00:14f0:0:1::1a 19.904ms
9: 2a00:14f0:0:1::a 21.003ms
10: 2a00:14f0:1:2::5 21.239ms asymm 11
11: 2a00:14f0:e000:130::1 21.112ms pmtu 1280
11: 2a00:14f0:e000:130::1 21.034ms asymm 12
11: 2a00:14f0:e000:130::1 21.139ms asymm 12
12: no reply
13: no reply
It seems that the POP is not routing ingress traffic to the 8130::/64 subnet to my tunnel as expected.
Regards,
Primiano
Tunnel working but /64 subnet not being routed.
It seems that the POP is not routing ingress traffic to the 8130::/64 subnet to my tunnel as expected.
It is, but you need to configure your side correctly.
Tunnel working but /64 subnet not being routed.
Shadow Hawkins on Sunday, 04 August 2013 22:18:19
Even assuming that the subnet routing is not properly configured, I would expect to see the traceroute to reach at least 2a00:14f0:e000:130::2 (which is my endpoint) at step 12, but is not.
As you can see from the previous attachment, the traceroute dies at 130::1 (which is the POP endpoint). On the other side I'm 100% sure that my endpont (130::2) is reachable (I just pinged 2 seconds before the traceroute).
Whatever possible misconfiguration you can imagine, I can't see any possible explanation to the fact that the POP is not hopping to my tunnel.
In other words, from a networking viewpoint, I can't see how could I possibly (badly) configure things on my side such that the POP doesn't route datagrams targeted to my subnet (8130::/64) to my endpoint (130::2).
Do you have any plausible explanation to offer?
Kind regards,
Primiano Tucci
Tunnel working but /64 subnet not being routed.
I would expect to see the traceroute to reach at least 2a00:14f0:e000:130::2 (which is my endpoint) at step 12, but is not.
Check with tcpdump on your tunnel if that is true.
Whatever possible misconfiguration you can imagine, I can't see any possible explanation to the fact that the POP is not hopping to my tunnel.
As you are providing no details on how your endpoint is configured (even though that big orange bar shown while posting asks for it) there is little we can state about this.
As this really is not a problem on the SixXS side, please use the forums to figure this out.
Note that also there people will ask for full details.
Do you have any plausible explanation to offer?
That you configured the routing of the packets back wrongly, that you are filtering things, there are a lot of things that can go wrong there.
|
![[ch]](/s/countries/ch.gif)
on Sunday, 04 August 2013 12:21:13
Posting is only allowed when you are