SixXS::Sunset 2017-06-06

Confusing
[at] Carmen Sandiego on Sunday, 02 March 2014 20:03:24
I got 2 things a tunnel: SixXS IPv6 : 2001:xxxx:yyyy:7d4::1/64 Your IPv6 : 2001:xxxx:yyyy:7d4::2/64 and a subnet Prefix : 2001:xxxx:yyyy:87d4::/64 the SixXS whois shows this: This route goes to an endpoint of xxxx-SIXXS This route is routed to 2001:xxxx:yyyy:7d4::2 Via ayiya tunnel to my IPv4-address the tunnel itself works perfekt; Here in the FAQs How do I give connectivity to other hosts on my subnet? this subnet is called the "Default subnet"; my thoughts: one linux box has the aiccu service running for the tunnel; the eth0 device has e.g. 2001:xxxx:yyyy:87d4::1/64 as IPv6-address and another linux box has 2001:xxxx:yyyy:87d4::2/64 as IPv6-address; both linux boxes ping each other; the one linux box that runs the aiccu service allows e.g. ping6 ipv6.google.com but the other shows this when doing the same: From 2001:xxxx:yyyy:7d4::1 icmp_seq=# Destination unreachable: Administratively prohibited why this? the same when the one linux box with the running aiccu service has also running radvd and the other gets its IPv6-address automatically; can someone please explain, what I did wrong ..., or why this doesn't work ... Thanks, Walter
Confusing
[ch] Jeroen Massar SixXS Staff on Sunday, 02 March 2014 20:17:29
From 2001:xxxx:yyyy:7d4::1 icmp_seq=# Destination unreachable: Administratively prohibited
Firewall rule? Are you sure that 2001:xxxx:yyyy:7d4::1 replies (as that is the PoP side) and not 2001:xxxx:yyyy:87d4::1 which would be your end... I do see:
$ traceroute6 2001:15c0:65ff:87d4::2 [..] 9 simbx01.sixxs.net (2001:15c0:ffff:7::2) 23.287 ms 23.261 ms 23.233 ms 10 gw-2005.mbx-01.si.sixxs.net (2001:15c0:65ff:7d4::1) 23.485 ms 23.533 ms 23.846 ms 11 cl-2005.mbx-01.si.sixxs.net (2001:15c0:65ff:7d4::2) 46.205 ms !X 42.974 ms !X 42.776 ms !X
$ traceroute6 2001:15c0:65ff:87d4::1 [..] 9 simbx01.sixxs.net (2001:15c0:ffff:7::2) 31.759 ms 31.755 ms 26.146 ms 10 gw-2005.mbx-01.si.sixxs.net (2001:15c0:65ff:7d4::1) 30.308 ms 25.939 ms 25.877 ms 11 2001:15c0:65ff:87d4::1 (2001:15c0:65ff:87d4::1) 48.772 ms !X 55.888 ms !X 63.322 ms !X
$ traceroute6 2001:15c0:65ff:87d4::2 [..] 9 simbx01.sixxs.net (2001:15c0:ffff:7::2) 23.306 ms 23.316 ms 23.150 ms 10 gw-2005.mbx-01.si.sixxs.net (2001:15c0:65ff:7d4::1) 23.514 ms 23.439 ms 23.603 ms 11 cl-2005.mbx-01.si.sixxs.net (2001:15c0:65ff:7d4::2) 3021.315 ms !H 3020.354 ms !H 3020.244 ms !H
As such, check your firewall rules.
Confusing
[at] Carmen Sandiego on Monday, 03 March 2014 10:36:09
Jeroen Massar wrote:
> From 2001:xxxx:yyyy:7d4::1 icmp_seq=# Destination unreachable: Administratively prohibited Firewall rule? Are you sure that 2001:xxxx:yyyy:7d4::1 replies (as that is the PoP side) and not 2001:xxxx:yyyy:87d4::1 which would be your end...
As you say this; yes it was a firewall rule on the linux box running the aiccu service; I'm a little bit confused why the subnet prefix differs from the tunnel prefix; Thanks, Walter
Confusing
[ch] Jeroen Massar SixXS Staff on Monday, 03 March 2014 10:49:16
Walter Hoehlhubmer wrote: [..]
I'm a little bit confused why the subnet prefix differs from the tunnel prefix;
Because they live on two different interfaces (tunnel and eth0) and thus have two different broadcast/multicast domains, hence they have to be different. See also SixXS Prefixes

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

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