amph

Hmm, not sure if it counts as proprietary but I imagine any firewall/router/modem device that is capable of DDWRT/OpenWRT would be capable of this. It is interesting though to see which are capable of it out of the box.

Works on Nokia IP boxen running CheckPoint. Tested with IPSO 4.1-build045 and CheckPoint VPN-1 NGX R65 HFA02 + ipv6 hotfix. The documentation leaves something to be desired, and tunnels cannot be terminated on the VRRP (virtual) address of a pair. On a single machine, it works fine.

We are looking to compile a list of firewall/CPE devices that by default (With no major changes except maybe a firmware update) support IPv6 over IPv4 tunnels. (Protocol 41 tunneling).

I use D-Link Gaming Router DGL-4300 fw 1.7. I have NAT enabled. The router works with HE's IPv6 Tunnel Broker out-of-the-box.This is a regular IPv4-only router.

Direct IPv6 Support with D-Link RoutersAlso, D-Link is supposed to support IPv6 directly in some of their (newer?) routers. They are: D-Link IPv6 support: DI-784 abg, DI-524 bg, DI-624 bg, WBR-1310 g, WBR-2310 g rangebooster, DIR-615 n. SeeRef: http://www.ipv6.org.tw/summit2008/doc/1-4-4.pdfIt would be nice if HE can provide configuration instructions for these routers (although I could probably figure it out myself eventually once I get one).

D-Link DIR-615, not 100% confirmed yet, but after reviewing a user's screen shots of the device's web interface out of the box, it appears to let you configure a 6in4 tunnel on it, and plug in the routed /64 to hand out to your LAN.

I'm going to run out to a store and see if I can get one. Mostly for personal use at home, aside from testing it for this HCL. I'll post some screen shots if I can get one and confirm.

I'll have screen shots that hopefully I can sort into example configurations.

I think Hurricane electric uses IPv6 in IPv4 Tunneling, as 6 in 4 Tunneling is for isolated networks.

For Stateful or Stateless I think that's just a local (site) choice whether the D-Link router assigns an address with it's own Router Advertisement Network Discovery Protocol daemon (Stateless) or each host sets it's IPv6 address (Stateful). I could be wrong.

I'm using an old Secure Computing SG570 with firmware Version 3.1.4u5 and it allows tunnels with zero configuration.

It has built in IPv6 support that can be enabled if your ISP supports IPv6, Comcast does not at this time so I cannot test that side of things. I turned the IPv6 support off because of this.

I did ssh into the router and setup my HE tunnel through the CLI at one point, but it doesn't save the changes upon reboot so I opted not to use this method. I setup a VMware CentOS to handle IPv6 and DNS locally, it also worked fine when I used a Windows 7 machine to connect directly to the tunnel as well.