Latest revision as of 06:44, 29 February 2024

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

This page is out of date

ZyXEL VMG3925 and VMG1312

The VMG3925 B10B and VMG1312 B10D are currently AAISP's default routers, both with IPv6 support.

Technicolor TG582N

The TG582N was AAISP's default ADSL router prior to May 2015, it was chosen due to its IPv6 support. The Firmware versions that AAISP use which support IPv6 include 8.4.7.0 and 10.2.0.B.

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 an external FTTC Modem as it does not have a built-in VDSL modem. It has Wi-Fi 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]].
-=Technicolor TG582N=
+= ''' This page is out of date ''' =
-==Documents==
+=ZyXEL VMG3925 and VMG1312=
-*[[File:Technicolor_CPE_Firewall.pdf]]
-*[[TG582n_CLI_Guide_v1.0_public.pdf]]
-*[[IPv6_AppNote_v4.0_public.pdf‎]]
+The [[:Category:ZyXEL VMG3925 B10B|VMG3925 B10B]] and [[:Category:ZyXEL VMG1312 B10D|VMG1312 B10D]] are currently AAISP's default routers, both with [[IPv6]] support.
-==Firmware Versions==
+=Technicolor TG582N=
-Version 8.4.4.1 is the factory default (as of November 2011)
-Version 8.4.7.0 is IPv6 enabled, and is upgraded at AAISP when configured by AAISP.
+The [[TG582N]] was AAISP's default [[ADSL Router|ADSL router]] prior to May 2015, it was chosen due to its [[IPv6]] support. The Firmware versions that AAISP use which support [[IPv6]] include 8.4.7.0 and 10.2.0.B.
-Upgrading from 8.4.4.1 is arranged by AAISP via the TR-069 CPE WAN Management protocol.  This involves installing the "isp.def" as needed to persuade the router to connect to AAISP's TR-069 servers and asking AAISP to request the upgrade.
-===Admin Settings===
-When configured by A&A, the default username from the LAN side is: Administrator and from the WAN: aaisp.
-The password will be printed on the card on the base of the router, and also seen on the control pages.
-===Setting up Routed Config===
-Use the configuration-wizard (Firefox seems to work best) and choose ADSL(Expert).
-TODO: Describe where to find this.
-===Adding Static-routes===
-  ip rtlist
-  ip rtadd dst=network/mask gateway=gatewayip
-  ip saveall
-===Really disabling the firewall===
-From a customer: While going mad with a tg582n tonight.  I discovered they try to do stateful firewalling even when the firewall is disabled in the web interface.   This breaks where you want to failover to 3G.  I guess it would also break if you had 2 ADSL lines.
-Completely disabling the firewall seems to be necessary to allow IPv6 connections from WAN side to network, as even when IPv4 firewall is 'off', the IPv6 still seems to be firewalled.
-To fix, put in CLI:
- firewall config state disabled
- firewall config icmpchecks disabled
- firewall config udpchecks disabled
- firewall config tcpchecks none
-Disabling the firewall also allows access to the routers' internal services from the WAN-side, although there seems to be some default logic disallowing these to function e.g. "User 'Administrator' is disallowed to login from wan to telnet" etc.
-===Problems connection to PPTP Servers===
-One customer has reported problems connecting to PPTP VPN servers in either direction through a tg582n with the 8.4.7.0 firmware.
-Technicolor have stated that this may be due to the Application Layer Gateway system intercepting PPTP packets even when the firewall is disabled and is a deliberate feature, but that the feature can be disabled by entering the following commands in the CLI:
- connection applist
- connection unbind application PPTP port 1723
- saveall
-However the same customer has reported that this solution has not actually fixed the problem and that the PPTP entry is still visible when running the "connection applist" command even after the unbind command has been successfully run.
-(At present it appears no other customer has reported the problem so it may be an issue specific to this one user)
-===Adding a static route via telnet cli===
- ip rtadd dst=IP/MASK gateway=GATEWAYIP
+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 an external [[FTTC Modem]] as it does not have a built-in VDSL modem. It has Wi-Fi too.
+See the [[TG582N]] page for further information, and configuration notes (problems & fixes)
 ----
-=Other routers that we've used in the past:=
+=Other routers that we've used in the past=
@@ Line 77: / Line 30: @@
 We have a copy of 1.06d here:
-[[media:UKBillion7800NV6_106d.zip]]
+[[media:UKBillion7800NV6 106d.zip]]
@@ Line 87: / Line 40: @@
 ==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 93: / Line 46: @@
 ==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/
+==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."
+[[Category:IPv6]] [[Category:Router]]