Revision as of 15:29, 2 December 2014

For generic information on how AAISP do IPv6 on DSL lines, see: IPv6.

Technicolor TG582N

The TG582N is AAISPs current ADSL router, it was chosen due to its IPv6 support. The Firmware that AAISP use which supports IPv6 is 8.4.7.0.

The TG582N is a 4 port ADSL router, and can be configured so that one of the ethernet ports can support PPPoE - for connecting to a FTTC Modem. It has wifi too.

See the TG582N page for further information, and configuration notes (problems & fixes)

Other routers that we've used in the past:

Billion BiPAC 7800N

Factory IP: 192.168.1.254 Factory User/Pass: admin/admin

Firmware

Latest Firmware is from Billion As of October 2011 the version we ship is 1.06d

We have a copy of 1.06d here: media:UKBillion7800NV6_106d.zip

Another useful Billion page on spaldwick.com

Comtrend

Info here: *Comtrend

Thomson

We've tested a TG789vn router (Aug 2011) which had beta IPv6 firmware (10.1.0.3), and this works. A bit more info here: [1]

Apple Airport Extreme

The Airport Extreme claims to support native IPv6 over PPPoE but we don't know of anyone who has it working. It still works via tunnels though (tunnel configuration explained on the knowledge base). You need to set the remote tunnel endpoint address to 81.187.81.6, and you need two /64 subnets off us that are statically routed to the Airport's IPv4 address. Assign an IP from one /64 as the WAN address and set the default route to our ping address "bottomless", which is 2001:8b0:0:81::51bb:51bb. Set the LAN address to the first usable IP on the second /64 and it should just work.

Note that the firmware 7.6.3 breaks tunnels configured under earlier firmware but there is a simple fix. Using the latest version of Airport Utility you need to add an IPv6 Delegated Prefix. The easy way seems to be to copy and paste the address from the IPv6 LAN address field and add /64 to the end - otherwise it assumes a /48. Further details here: http://arstechnica.com/apple/2013/02/airport-extreme-update-breaks-ipv6-tunnels-but-heres-how-to-fix-it/

ASUS RT-N66U

The RT-N66U does pretty much "just work" with IPv6. Running the TomatoUSB firmware it was just a case of enabling "Native IPv6" in the IPv6 options and giving the router's LAN interface an address from the allocated /64. The router appears to have enabled RA by default, so everything on the LAN side "just works"

TP-Link TD-8817

From a customer:

"The current v8 firmware does support IPv6 properly, but for it to be distributed to connected devices, not only DHCPv6 needs to be enabled, but also RADVD (this setting is not currently described in the modem's user manual). Leaving the sub-settings for RADVD to their default seems fine."

@@ Line 1: / Line 1: @@
-*For generic information on how AAISP do IPv6 on DSL lines, see: [[IPv6]].
+*For generic information on how AAISP do [[IPv6]] on DSL lines, see: [[IPv6]].
 =Technicolor TG582N=
-The TG582N is AAISPs current ADSL router, it was chosen due to its IPv6 support. The Firmware that AAISP use which supports IPv6 is 8.4.7.0.
+The [[TG582N]] is AAISPs current [[ADSL Router|ADSL router]], it was chosen due to its [[IPv6]] support. The Firmware that AAISP use which supports [[IPv6]] is 8.4.7.0.
-The TG582N is a 4 port ADSL router, and can be configured so that one of the ethernet ports can support PPPoE - for connecting to a FTTC Modem. It has wifi too.
+The [[TG582N]] is a 4 port [[ADSL Router|ADSL router]], and can be configured so that one of the [[ethernet]] ports can support PPPoE - for connecting to a [[FTTC Modem]]. It has wifi too.
 See the [[TG582N]] page for further information, and configuration notes (problems & fixes)
@@ Line 34: / Line 34: @@
 ==Thomson==
-We've tested a TG789vn router (Aug 2011) which had beta IPv6 firmware (10.1.0.3), and this works.
+We've tested a TG789vn router (Aug 2011) which had beta [[IPv6]] firmware (10.1.0.3), and this works.
 A bit more info here:
 [http://revk.www.me.uk/2011/08/ipv6-routers-thomson-step-up-their-game.html]
@@ Line 40: / Line 40: @@
 ==Apple Airport Extreme==
-The Airport Extreme claims to support native IPv6 over PPPoE but we don't know of anyone who has it working. It still works via tunnels though (tunnel configuration explained on the [http://aa.net.uk/kb-broadband-ipv6-tech.html knowledge base]). You need to set the remote tunnel endpoint address to 81.187.81.6, and you need two /64 subnets off us that are statically routed to the Airport's IPv4 address. Assign an IP from one /64 as the WAN address and set the default route to our ping address "bottomless", which is 2001:8b0:0:81::51bb:51bb. Set the LAN address to the first usable IP on the second /64 and it should just work.
+The Airport Extreme claims to support native [[IPv6]] over PPPoE but we don't know of anyone who has it working. It still works via tunnels though (tunnel configuration explained on the [http://aa.net.uk/kb-broadband-ipv6-tech.html knowledge base]). You need to set the remote tunnel endpoint address to 81.187.81.6, and you need two /64 subnets off us that are statically routed to the Airport's IPv4 address. Assign an IP from one /64 as the WAN address and set the default route to our ping address "bottomless", which is 2001:8b0:0:81::51bb:51bb. Set the LAN address to the first usable IP on the second /64 and it should just work.
-Note that the firmware 7.6.3 breaks tunnels configured under earlier firmware but there is a simple fix.  Using the latest version of Airport Utility you need to add an IPv6 Delegated Prefix. The easy way seems to be to copy and paste the address from the IPv6 LAN address field and add /64 to the end - otherwise it assumes a /48.  Further details here: http://arstechnica.com/apple/2013/02/airport-extreme-update-breaks-ipv6-tunnels-but-heres-how-to-fix-it/
+Note that the firmware 7.6.3 breaks tunnels configured under earlier firmware but there is a simple fix.  Using the latest version of Airport Utility you need to add an [[IPv6]] Delegated Prefix. The easy way seems to be to copy and paste the address from the [[IPv6]] LAN address field and add /64 to the end - otherwise it assumes a /48.  Further details here: http://arstechnica.com/apple/2013/02/airport-extreme-update-breaks-ipv6-tunnels-but-heres-how-to-fix-it/
 ==ASUS RT-N66U==
-The RT-N66U does  pretty much "just work" with IPv6. Running the TomatoUSB firmware it was just a case of enabling  "Native IPv6" in the IPv6 options and giving the router's LAN interface an address from the allocated /64. The router appears to have enabled RA by default, so everything on the LAN side "just works"
+The RT-N66U does  pretty much "just work" with [[IPv6]]. Running the TomatoUSB firmware it was just a case of enabling  "Native [[IPv6]]" in the [[IPv6]] options and giving the router's LAN interface an address from the allocated /64. The router appears to have enabled RA by default, so everything on the LAN side "just works"
+==TP-Link TD-8817==
+From a customer:
+"The current v8 firmware does support [[IPv6]] properly, but for it to be distributed to connected devices, not only DHCPv6 needs to be enabled, but also RADVD (this setting is not currently described in the modem's user manual). Leaving the sub-settings for RADVD to their default seems fine."
 [[Category:IPv6]] [[Category:Router]]