|
SixXS tunnels to an Airport extreme
![[se]](/s/countries/se.gif) Shadow Hawkins on Thursday, 05 July 2007 18:50:29
Hi!
I wonder if anyone has tried to setup a tunnel between an Airport extreme and SixXS?
What I can see at http://www.apple.com/airportextreme/specs.html
it should support manual IPv6 tunnels.
Regards,
Claes Leufvén
SixXS tunnels to an Airport extreme
In theory "manual IPv6 tunnels" are static proto-41 tunnels, thus those should indeed work (not tested though).
I personally am more a fan of WRT alike products and from what I see except for the sleek white box there really is no advantage over a WRT actually.
SixXS tunnels to an Airport extreme
![[de]](/s/countries/de.gif) Shadow Hawkins on Thursday, 05 July 2007 23:03:27
Hi Claes i asked this question a while ago at the apple lists and this is what i got back
from a guy at apple:
*******
The other option is Manually Configured Tunnel, and it uses static 6in4 tunneling. It does not support TIC. Looking at the SixXS pages, I'm not sure you can use their service without using TIC. If so, and you still want to use your SixXS account, then you'll need to use AICCU and rtadvd and all that jazz on a machine with a static private address configured in AirPort Utility as the default private host address.
SixXS tunnels to an Airport extreme
One can definitely use SixXS services without the need for TIC, but only static proto-41 tunnels then work unless one hacks around things.
TIC is only a convenience factor so that one doesn't need to copy this information over and only user+pass is needed to make it work, avoiding wrongfully copying of details etc.
When not using TIC though, only static proto-41 tunnels are supported.
One can enable/disable/move these using the web interface or of course by telnetting into the TIC server. Just enable the tunnel and fill in the parameters on the box and it will all work.
TIC is also note entirely needed for Heartbeat/AYIYA tunnels, one could hack AICCU to simply cache it locally, but one would still then need that tool to exist on the box itself anyway, so why not keep it in.
You might want to pass it on to the list you mention.
I don't know what kind of Operating System is running on those Airport Extreme's, but most likely it is some form of Mac OS X but very stripped or some variant of BSD of Linux, in most cases getting AICCU to run on it the moment you have the ability to run something as a uid==0 or equivalent user should not be too hard (given availability of compilers etc of course)
SixXS tunnels to an Airport extreme
Shadow Hawkins on Wednesday, 01 August 2007 14:33:37
Ok, thanks for your replies!
Maybe it is best as you suggested to use something "WRT-enabled" instead.
SixXS tunnels to an Airport extreme
![[fr]](/s/countries/fr.gif) Shadow Hawkins on Monday, 08 October 2007 00:26:40
I got it working. I have one of the new AEBS with .11n and GigEthernet ports, which requires the newest "airport utility", version 5.2.1.4 at the time of this writing. (This is a whole new app compared to the older "airport admin utility", version 4.etvas.)
I could bring up my sixxs 6in4 tunnel with no problem, but getting it to subnet and route correctly was a major effort. The airport express has an entry for LAN Prefix Length, but if it is anything other than 64, the base station doesn't seem to route traffic. I tried it with various 80 and 96 entries, but it would only route with 64. Trying with manual configurations on my macs on the LAN didn't work, correctly formed packets went into the LAN port on the AXBS, but nothing came out the WAN port. I could ping the ::2 address from the internet, and see those packets on my tcpdump trace(running on a mac).
For a long time, I had my tunnel to a cisco router, which allowed me to declare the ::1 and ::2 tunnel endpoints to have a /112 prefix, leaving me with many /80 subnets to play with. But with a /80 prefix, autoconfiguration doesn't work well on some operating systems. Most of my servers use static configuration, so it was never really a problem.
On the Airport Utility advanced setup tab, I selected the IPv6 subtab and filled it in like this:
IPv6 Mode : Tunnel
Config ipv6 : Manually
Remote IPv4 : 212.100.184.146
Remote IPv6 : 2001:6f8:202:195::1
Local IPv6 : 2001:6f8:202:195::2
LAN IPv6 : 2001:6f8:3f4:1::1
LAN Prefix : 64
There is no way to tell the airport extreme the prefix for the tunnel, it appears hardcoded to use a /64. Other tests I've done with my cisco as an upstream router on the WAN port with /112 or /96 prefixes showed all kinds of problems with the AXBS (no tunneling, straight routing with IPv6 Mode set to Node).
So if you are new to Sixxs and don't have any credits to get a subnet, you'll just have to leave the tunnel up for a few weeks on the AXBS, then ask for a subnet. Put the subnet into the LAN field. Not optimal, but it should work.
I'll work on this some more now that I have a whole /48 to play around in, and get a bug report and maybe a feature request into Apple. I've been pushing on them to get a 6in4 tunnel into the Jaguar network prefs, but so far it hasn't happened. There has been a 6to4 function that is slightly hidden since 10.3.
Regards
SixXS tunnels to an Airport extreme
For the tunnel (which is a single /64) only ::1 (the PoP) and ::2 (your endpoint) work. The rest of the block is not used.
Thus when you want to route anything to another host you will need to request a subnet, which in general is a /48.
As IPv6 Autoconfiguration uses /64's, you will have to assign a /64 to each interface. But as you get a /48, you have 65536 of those and that should be enough. Autoconfiguration can't work with a non-/64 as the OS can't know what bits to use for the host-part of the prefix. With a /64 it knows that it can use EUI-64.
It is thus not so odd, due to autoconfig, that the Airport Extreme doesn't accept any other prefix. As such that definitely is not a bug, but an operator error.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 05 July 2007 19:05:23
Posting is only allowed when you are