Skip to end of metadata
Go to start of metadata

Standards and Standard Organizations

While the IETF working groups have been working on IPv6 standards for many, many years, documents that describe what standards and features should be in broadband CPE devices have only started to materialize in 2010.

Broadband Forum

The Broadband Forum (formerly DSL Forum) has included IPv6 in its BroadbandSuite specification X.X which was intended to be released in 2009-2010.

CableLabs

IETF

RIPE

NIST

The New Hampshire's InterOperability Laboratory performed an IPv6 CE test, and as an exception to their general rule, published some test results. No vendors are named (to protect the guilty).

Other listings

Marco Hogewoning gave a presentation at RIPE 60 covering various vendors' support and progress with various DSL and router CPE. This has now been followed up with a page at the RIPE Labs to document IPv6 CPE. A complete listing of every survey can be found here.

Adapters

Adapter CPEs allow an ISP to offer subscribers immediate access to IPv6 over an existing IPv4 access network. Neither the existing IPv4 access CPE nor the ISPs IPv4 access network gear (DSLAM, etc.) need to be changed, nor have their firmware updated, if an Adapter CPE is used at the subscriber premise. As in Dual-Stack implementations, the ISP issues the subscriber a /48 prefix, or smaller space, using the ISPs own IPv6 allocation which the Adapter CPE advertises over the subscriber's home or office LAN.

The Adapter CPE practically works by plugging into any free ethernet port on an existing routers or modem at the subscribers premise. It encapsulates IPv6 traffic on the subscribers LAN in an IPv4 tunnel and sends it over an IPv4 network to the ISPs IPv6 enabled core. Regular IPv4 traffic at the subscriber premise follows its normal path on the existing CPE to the ISP core. Adapter CPEs can work behind nested NATs if the appropriate IPv6-in-IPv4 protocol is used. The ISP is expected to have a tunnel server to decapsulate the IPv6 traffic at their core network. One tunnel server should be able to handle thousands of Adapter CPEs, and such a server can be supplied by the Adapter CPE vendor.

Adapter CPEs can also reverse tunnel IPv4-in-IPv6 to serve subscribers operating an IPv6 modem but need a private IPv4 address tunneled within IPv6.

For users on a 3G, LTE or WiMax wireless connection via a USB style modem, a software version of the Adapter CPE can be used to connect the user to the same IPv6 tunnel server at the ISP core.

  • gogo6 Adapter CPE gogoCPE
    • Supports 6RD (RFC 5969), TSP (RFC 5572) and L2TP (RFC 2661) for IPv6-in-IPv4 tunneling
    • If implementing IPv6 tunneling behind NATs then TSP protocol is recommended for tunneling across all types of NATs
    • An Adapter CPE version that enables DS-Lite over IPv6 CPEs by using IPv4-in-IPv6 tunneling is available
    • Adapter CPE using DS-Lite helps conserve IPv4 by deploying v4 private addresses to subscribers over IPv6
  • gogo6 Adapter Software Client gogoCLIENT
    • Graphical interface works on Windows XP, Vista, 7, Server 2003/2008
    • Command line version for Mac OS X, Linux and BSD
    • Trial version of Adapter Software Client can be downloaded from the Freenet6 site
  • gogo6 Tunnel Server gogoSERVER
    • Server supports both Adapter CPE and Software Client users
    • One server can support different IPv6 migration protocols, including TSP, 6RD, DS-Lite and DSTM

Cable

For cable, this is simple because all gateway devices certified by Cablelabs at DOCSIS 3.0 CM or CMTS will have IPv6 support. An example such device is the Cisco Systems DPC3939 Of course, having a compliant cable modem or gateway only matters if the cable company's CMTS also supports IPv6.

The new 'DOCSIS 2.0 + IPv6' standard also supports IPv6, which may on the cable modem side only require a firmware upgrade [http://www.rmv6tf.org/2008-IPv6-Summit-Presentations/Dan%20Torbet%20-%20IPv6andCablev2.pdf].

DSL

Most of the newest models released since Q3 2010 either have some level of IPv6 support, especially those models that support VDSL2. Many of the vendors with IPv6 implementations use Broadcom's chipset, and it's code has been lacking. That code has improved over the last few months to the point that in Q2 2011 that it's almost feature complete.

  • AVM Fritz!Box WLAN 3270 and 3370, FRITZ!Box Fon WLAN 7240, 7270 (only v2, v3 and international, no IPv6 on 7270 v1), 7320, 7340, 7390 and 7570 (upgrade to latest firmware might be required):
    • IPv6 now supported by most (if not all) current AVM modem routers
    • Support for native IPv6 as well as SixXS heartbeat, 6RD, 6in4 and 6to4 tunnels
    • MTU can be set manually
    • Support for ULA
    • IPv6 firewall
    • DHCPv6 support
  • BEC 7800TN R2
    • Has the Billion 7800NL code on the bottom of the box
    • When PPPoEv6 configured on WAN
      • DHCPv6-PD works
      • Stateful DHCP works and retrieves DNS servers
      • SLAAC with stateless DHCP works and retrieves DNS servers
      • handles non /64 prefix delegations
      • verifying if it has stateful packet inspection firewall support
    • IPoE requires manually entering default WAN gateway
  • BEC 8800N (IPv6 implementation not fully complete, i.e. requires entering default gateway on WAN interface)
  • Billion BiPAC 7402R2 ADSL2+ VPN Firewall Router (seems to be vanished from the face off the earth or at least is not supported)
  • Billion 7800NL
  • Cisco 87x and 88x SOHO routers, so not residential consumer-grade
  • Comtrend CT-5374
    • When PPPoEv6 configured on WAN
      • DHCPv6-PD works
      • SLAAC with stateless DHCP works
      • handles non /64 prefix delegations
      • stateful packet inspection firewall support
    • GUI doesn't expose much of the IPv6 addresses
    • GUI uses confusing terminology to describe IPv6 features
  • Comtrend AR-5384u
    • When PPPoEv6 configured on WAN
      • DHCPv6-PD works
      • SLAAC with stateless DHCP works
      • handles non /64 prefix delegations
      • stateful packet inspection firewall support
    • GUI doesn't expose much of the IPv6 addresses
    • GUI uses confusing terminology to describe IPv6 features
  • Draytek Vigor 120, 2130 and 2750
  • Funkwerk Enterprise Communications
  • NetComm NB6Plus4
  • NetComm NB6Plus4W
  • NetComm 3G16WV
  • Technicolor TG582n and also the TG789vn, TG789vn v3, TG788vn, TG787, TG784n v3, TG784n, TG784, TG712, TG670, TG589vn v2, and TG587n v3
    • Firmware r10.2 should be ready by the end of January, 2012.
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6
      • SLAAC
      • Stateful DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
      • 6rd
      • DSLite
      • stateful firewall for IPv6
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful DHCPv6 server
      • SLAAC
      • Prefix delegation
      • DNSv6 server
      • DNSv4/v6 proxy
  • Technicolor TG789vn
    • When PPPoEv6 configured on WAN
      • DHCPv6-PD works
      • SLAAC with stateless DHCP works
      • handles non /64 prefix delegations
      • GUI for IPv6 configuration is incomplete
  • VisionNet 505N (IPv6 implementation not fully complete)
  • ZyXEL VSG1432 is in a testing phase with their IPv6 code (may be available from your ZyXEL SE)
    • When PPPoEv6 configured on WAN
      • DHCPv6-PD works
      • Stateful DHCP works
      • SLAAC with stateless DHCP works
      • handles non /64 prefix delegations
      • stateful packet inspection firewall not currently supported, vendors says it will soon
  • Zoom X7N
  • via OpenWRT
  • via DD-WRT
  • via TomatoUSB

Routers/Wireless Access Points

  • D-Link's presentation (http://www.ipv6.org.tw/docu/summit2009/1028 Sesson 4/01.2009%20Summit D-Link's%20View%20on%20IPv6.pdf) on their commitment to IPv6 and blog entry listing some IPv6 ready products. D-Link is currently working on adding Dual-Stack Lite (DS-Lite) support.
  • Airport Extreme (later model) details here
    **WARNING: Apple will NOT suppport IPv6, if it works it works, if it doesn't, their support will not talk to you
    • IPv6 on the WAN side
      • Static IPv6
      • DHCPv6 (stateful) with PD
      • DHCPv6 (stateless) with PD
      • 6to4 tunneling
    • IPv6 on the LAN side
      • stateless DHCPv6
      • no stateful DHCPv6
  • Buffalo WZR-AG300NH
    • Implementation details unknown
  • D-Link DIR-601 (Hardware Revision A1, look //ftp.dlink.com/Gateway/dir601/Firmware/ here for updates)
    • supports DHCP-PD
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6
      • SLAAC
      • Stateful DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful DHCPv6
      • SLAAC
  • D-Link DIR-615 (Hardware Revision C)
  • D-Link DIR-615 (Hardware Revision E1-E4, all new IPv6 features will be developed on this hardware revision, look //ftp.dlink.com/Gateway/dir615 revE/Firmware/ here for updates; some features listed may be only available in private beta)
    • supports DHCP-PD
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6
      • SLAAC
      • Stateful DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
      • 6rd
      • Stateless DHCP to retrieve options
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful DHCPv6
      • Stateless DHCPv6/SLAAC
      • RFC 6106 (previously RFC 5006)/SLAAC
  • D-Link DIR-632 (Hardware Revision A1; some features listed may be only available in private beta)
    • supports DHCP-PD
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6
      • SLAAC
      • Stateful DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
      • 6rd
      • Stateless DHCP to retrieve options
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful DHCPv6
      • Stateless DHCPv6/SLAAC
      • RFC 6106 (previously RFC 5006)/SLAAC
  • D-Link DIR-655 (Hardware Revision B1, look //ftp.dlink.com/Gateway/dir655 revB/Firmware/ here for updates; some features listed may be only available in private beta)
    • supports DHCP-PD
    • stateful packet inspection firewall on WAN
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6
      • SLAAC
      • Stateful DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
      • 6rd
      • DS-Lite (in development)
      • Stateless DHCP to retrieve options
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful DHCPv6
      • Stateless DHCPv6/SLAAC
      • RFC 6106 (previously RFC 5006)/SLAAC
      • DNS Search List support
  • D-Link DIR-815 (Hardware Revision A1)
    • supports DHCP-PD
    • stateful packet inspection firewall on WAN
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6
      • SLAAC
      • Stateful DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
      • 6rd
      • DS-Lite (in development)
      • Stateless DHCP to retrieve options
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful DHCPv6
      • Stateless DHCPv6/SLAAC
      • RFC 6106 (previously RFC 5006)/SLAAC
  • D-Link DIR-825 (Hardware Revision B and //ftp.dlink.com/Gateway/dir825 revB/Firmware/dir825 revB FW 205NA.zip latest firmware; some features listed may be only available in private beta)
    • supports DHCP-PD
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6
      • SLAAC
      • Stateful DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
      • 6rd
      • Stateless DHCP to retrieve options
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful DHCPv6
      • Stateless DHCPv6/SLAAC
      • RFC 6106 (previously RFC 5006)/SLAAC
  • D-Link DIR-825 (Hardware Revision C1)
    • supports DHCP-PD
    • stateful packet inspection firewall on WAN (in development)
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6
      • SLAAC
      • Stateful DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
      • 6rd
      • DS-Lite (in development)
      • Stateless DHCP to retrieve options
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful DHCPv6
      • Stateless DHCPv6/SLAAC
      • RFC 6106 (previously RFC 5006)/SLAAC
  • D-Link DHP-1320 (Hardware Revision A1)
    • supports DHCP-PD
    • IPv6 on the WAN side
      • Link-Local only
      • Static IPv6
      • SLAAC
      • Stateful DHCPv6
      • IPv6 over PPPoE
      • 6to4 tunneling
      • IPv6 in IPv4 tunneling
      • 6rd
      • Stateless DHCP to retrieve options
    • IPv6 on the LAN side
      • Link-Local only
      • Stateful DHCPv6
      • Stateless DHCPv6/SLAAC
      • RFC 6106 (previously RFC 5006)/SLAAC
  • FireBrick Ltd A range of SOHO/Office routers built with IPv6 from the start.
  • Funkwerk Enterprise Communications
  • Linksys E4200 (needs 1.0.02 (Build 13) or later)
    • supports DHCP-PD
    • IPv6 on the WAN side
      • SLAAC (likely, but not verified)
      • Stateful DHCPv6
      • manual or automatic 6rd
    • IPv6 on the LAN side
      • Stateless DHCPv6/SLAAC
    • supports IPv6 on guest network if there are more than two available IPv6 subnets
  • Linksys RVS4000 has a NAT-PT bug
    • IPv6 on the WAN side
      • 6to4 tunneling
    • IPv6 on the LAN side
      • Stateless
      • Stateful (DHCPv6)
  • Linksys WRVS4400N is the wireless version of the above
    • IPv6 on the WAN side
      • 6to4 tunneling
    • IPv6 on the LAN side
      • Stateless
      • Stateful (DHCPv6)
  • NetComm NP805N
  • Netgear WNR1000v2 Latest firmware explicitly supports IPv6
  • Netgear WNR3500v2 Latest firmware explicitly supports IPv6
  • Netgear WNR3500L Latest firmware explicitly supports IPv6
  • Netgear WNDR3700v1 Latest firmware explicitly supports IPv6
  • Netgear WNDR3700v2 Latest firmware explicitly supports IPv6
    • supports DHCP-PD
    • IPv6 on the WAN side
      • Static IPv6
      • Stateful DHCPv6
      • IPv6 over PPPoE (creates a separate session for IPv6. Issue has been reported to Netgear)
      • 6to4 tunneling
      • Stateless DHCP to retrieve options
      • Pass Through
    • IPv6 on the LAN side
      • Stateful DHCPv6 (whether WAN was PPPoE or DHCP, the LAN-attached Windows 7 machine did obtain an IP, but unable to ping past WAN interface; could be the fact that the delegated prefix was a /56. Bug has been reported to Netgear.)
      • Stateless DHCPv6/SLAAC (the full /56 delegated prefix is used, rather than a /64, which results in a Windows 7 machine not obtaining IP information, consistent with RFC2462. Bug has been reported to Netgear.)

Trial and Test devices

In addition to the commercial products, some people are rolling their own using Linux/BSD servers or upgrading the firmware of existing devices. The typical broadband gateway currently on the market is a standard computer design loaded with custom firmware according to the spec of the company whose plastic case and logo are used. But in actual fact, all devices whatever the brand, are manufactured by factories in the Far East using a small set of standard hardware designs. Virtually all of these designs can be adapted to use IPv6 by simply changing the software, i.e. uploading a different set of firmware. The brand name sellers are using this fact to have very short product cycles to adjust to market demand. This means that as soon as there is any significant demand for IPv6 support, they could update their software and have new products on the market in two to three months.

The Far East

The Japanese market has many more IPv6 devices and services than most other countries. A good way to track what is going on there is to read through the announcements at IPv6Style in Japan. Don't click on the English version of the site since that is outdated and doesn't contain the product announcements. Instead, use a web translator to read the site. You can use Babelfish to produce an adequate Japanese-to-English translation for learning about new products. While many articles will still be almost incomprehensible, new product announcements are so formulaic that you can usually understand what the product will do, and the product name and model for further inquiries.

If you want to deploy IPv6 and cannot find CPE on the market to support your needs, it is worthwhile to send a detailled RFQ to the major brand name sellers like Linksys, Netgear, etc. Japanese or Korean brand name sellers are more likely to have already done the IPv6 development so make sure that companies like Billion and Buffalo get your RFQ.

  • No labels