Got Tomato? Want IPv6? Read this.

[VirtualLarry]

I recently became interested in IPv6. I started reading DSLR's Comcast forums, and then LinksysInfo's forums. I found a nifty guide to enabling IPv6 with Tomato.

http://www.linksysinfo.org/index.php?threads/setting-up-ipv6-for-he-tunnelbroker.35297/

With this guide, I was able to get my wired HTPC to score 9/10 at test-ipv6.com , but my desktops connected via wireless ethernet bridge, aren't passing the test at all. I'm really confused why.

 

[theevilsharpie]

I recently became interested in IPv6. I started reading DSLR's Comcast forums, and then LinksysInfo's forums. I found a nifty guide to enabling IPv6 with Tomato.

http://www.linksysinfo.org/index.php?threads/setting-up-ipv6-for-he-tunnelbroker.35297/

With this guide, I was able to get my wired HTPC to score 9/10 at test-ipv6.com , but my desktops connected via wireless ethernet bridge, aren't passing the test at all. I'm really confused why.

Consumer routers have always sucked at IPv6 support (and that includes Tomato, DD-WRT, pfSense, etc.), so I've avoided using them in that role. It's good to hear that IPv6 is starting to be better supported, even if it's only at a basic level.

For the computer that is connecting to the IPv6 network, which test is it failing?

 

[VirtualLarry]

For the computer that is connecting to the IPv6 network, which test is it failing?

the test says I don't have an IPv6 address.

I also cannot ping my default IPv6 gateway.

 

[theevilsharpie]

the test says I don't have an IPv6 address.

I also cannot ping my default IPv6 gateway.

But you said you had one machine working

 

[VirtualLarry]

But you said you had one machine working

The wired PC is working. I can ping the default gateway, I can ping -6 www.google.com, etc.

Connecting my laptop (Win7 64-bit HP) to that router's 2.4Ghz AP also allows me IPv6 access.

But the PCs behind the 5Ghz wireless ethernet bridge are not passing any IPv6 that I can see.

Even though the IPv6 stack on my desktop PC behind the bridge appears to be picking up a proper IPv6 address (it has my tunnelbroker.net tunnel prefix in it).

 

[theevilsharpie]

The wired PC is working. I can ping the default gateway, I can ping -6 www.google.com, etc.

Connecting my laptop (Win7 64-bit HP) to that router's 2.4Ghz AP also allows me IPv6 access.

But the PCs behind the 5Ghz wireless ethernet bridge are not passing any IPv6 that I can see.

Even though the IPv6 stack on my desktop PC behind the bridge appears to be picking up a proper IPv6 address (it has my tunnelbroker.net tunnel prefix in it).

You want to try temporarily connecting your desktop PC straight to your router to see if your wireless bridge is screwing things up. Theoretically, there should be no problems since IPv6 operates at a higher layer, but with consumer networking gear, you can never really take any functionality for granted.

 

[VirtualLarry]

pretty sure it's something with the bridged router. I have an additional 2.4Ghz AP (DIR-655) plugged into the far bridged router (LAN to LAN), and when I connect to that AP using my laptop, I don't get an IPv6 connection either. But that same laptop, when connected to the 2.4Ghz AP on the main router (same firmware, same router model), I DO get IPv6 connectivity.

So for some reason, it seems like the bridge isn't passing IPv6. If this were IPv4, I would think that there is something wrong with ARP. But since IPv6 doesn't use ARP, I have no idea.

The far side of the bridge doesn't have an IPv6 address assigned to itself, either. That might be part of the problem, I don't know.

If I configure the far router/bridge, and enable IPv6 DHCPv6, I end up with two IPv6 default gateways on the desktop PC connected to the bridge, but IPv6 still doesn't work right.

Edit: Btw, still no IPv6 connectivity with the DIR-655 disconnected, I tried that too.

 

[pmarks]

The problem is that WiFi clients only have 1 MAC address, and can't function as a bridge without hacks in the IP layer:
http://wiki.openwrt.org/doc/howto/clientmode#bridged.client.mode.issues

The workaround is to implement RFC4389:
http://tools.ietf.org/html/rfc4389

OpenWRT includes a "6relayd" package which partially solves this problem, but it only works for LAN<->Internet and not LAN<->LAN connectivity. I filed a bug about this recently:
https://dev.openwrt.org/ticket/13275

 

[VirtualLarry]

The problem is that WiFi clients only have 1 MAC address, and can't function as a bridge without hacks in the IP layer:
http://wiki.openwrt.org/doc/howto/clientmode#bridged.client.mode.issues

The workaround is to implement RFC4389:
http://tools.ietf.org/html/rfc4389

OpenWRT includes a "6relayd" package which partially solves this problem, but it only works for LAN<->Internet and not LAN<->LAN connectivity. I filed a bug about this recently:
https://dev.openwrt.org/ticket/13275

Very interesting, thank you! Looks like that's what needs to be done, an implementation of that RFC.

 

[RossMAN]

For a basic wired/wireless house like ours using Linksys E3000 running Tomato with:

2 desktops, 1 laptop, iPad, Roku, HTPC

What are the benefits of ipv6?

 

[pmarks]

What are the benefits of ipv6?

IPv4 connects you to all the IPv4 devices in the world, and IPv6 connects you to all the IPv6 devices. The benefits are essentially the same, except that IPv6 isn't running out of addresses.

 

[VirtualLarry]

For a basic wired/wireless house like ours using Linksys E3000 running Tomato with:

2 desktops, 1 laptop, iPad, Roku, HTPC

What are the benefits of ipv6?

All the cool kids are doing IPv6.

 

[RadiclDreamer]

All the cool kids are doing IPv6.

all 8 of you

 

[ViRGE]

Thanks for throwing this up, Larry. Comcast finally turned on IPv6 around here, so I bit the bullet, installed Tomato-Toastman, and now I'm fully dual stack.

 

[k96nb01]

Hi, I know this is an old thread, but I'm hoping someone will see this and be able to help me. I have an Asus RT-N16 flashed with Toastman's Tomato build. I have Comcast with my own modem, which I know properly does IPv6, since if I plug my modem directly to my computer, everything works fine. However, I can't get my router to work properly. I've tried following the directions I've found online, about enabling "DHCPv6 with Prefix Delegation," and then inserting the following script:

#
# Workaround for TomatoUSB bug where a spurious default IPv6 route is
# added for no justified reason, resulting in packets getting forwarded
# effectively to /dev/null.
#
# 1. Temporarily disable accepting IPv6 RAs on the WAN interface. This
# will stop the kernel from automatically adding a default IPv6 route
# when such an RA is received via the WAN.
# 2. Delete ALL default IPv6 routes. In effect this deletes the spurious
# IPv6 default route, as well as any default IPv6 routes received via RA.
# Sadly the "ip" command does not give you a way to differentiate between
# the two, since the one we truly want to delete lacks "proto kernel".
# 3. Restore honouring IPv6 RAs via the WAN. Within 60-120 seconds (often
# within seconds on Comcast) a default IPv6 route should be added by the
# kernel. You can use "ip -6 route show default dev `nvram get wan_iface`"
# to verify; you should have only one route ("default via fe80::xxx ...").
#
# http://www.dslreports.com/forum/r27234575-TomatoUSB-and-Comcast-IPv6-bugs-found
#
echo 0 > /proc/sys/net/ipv6/conf/`nvram get wan_iface`/accept_ra
ip -6 route flush default dev `nvram get wan_iface`
echo 2 > /proc/sys/net/ipv6/conf/`nvram get wan_iface`/accept_ra

However, it does not work. No IPv6 address is listed under the WAN section of my status screen.

What am I doing wrong?

 

[ViRGE]

Personally I just used one of ToastMAN's builds and never needed to make any other changes to get IPv6 working.

 

[Engineer]

Personally I just used one of ToastMAN's builds and never needed to make any other changes to get IPv6 working.

The ARM versions, at least with Shibby, don't seem to work unless scripts are added to the WAN-UP and Firewall sections of Tomato. I've added the scripts and pull an IPv6 IP (Time Warner) but can't connect via IP6. Not sure what the issue is here.