[chappel]

I didn't have any luck with the script, but I was able to get ipv6 running by typing the key bits directly through a telnet console - when I'm connected to a wired port. However, I'm not connecting to the router (ping6s fail) when I'm connected via wireless. I'm trying to decide if I have something configured incorrectly, or if it's a bug in the firmware.

My client is Mac OSX snowleopard.
The router is a WRT-160NL running dd-wrt v24-(pre)sp2 build 14896 standard (latest as far as I can tell)

I'm using a hurricane electric tunnel from a static IPv4 address (which as I said, works on the wired side)

The client is detecting a link-local ipv6 default gateway of the router's eth0 interface (which I understand is the 'inside' interface off the cpu), but I can't ping it, nor the link-local address of the wifi or bridge interface (or anything else). The client auto-generated address correctly matches the routed inside subnet from HE; there must be some level of communication back and forth.

When I do a tcpdump from the client I'm seeing packets going out, and ndp 'who-has' queries coming back, but the devices seem to be talking 'past' each other.

On the router I enable the 'IPv6' and 'dadvd' checkboxes, and entered the following via telnet:

ip tunnel add he-ipv6 mode sit remote 209.51.181.2 local 208.x.x.229 ttl 255
ip link set he-ipv6 up
ip addr add 2001:x:x:x::2/64 dev he-ipv6
ip route add ::/0 dev he-ipv6
ip -f inet6 addr

ip -6 addr add 2001:x:y:x::1/64 dev br0
ip route add 2000::/3 dev he-ipv6

(the client auto-address matches the br0 subnet)

I haven't installed any of the ip6tables kernel mods; I'm not filtering any inbound v6 traffic on the wired side - is that somehow required to get wireless working? I plan on adding that sometime (along with a working version of the script), but thought I'd get the basics working first. At one point I added iptables rules to pass protocol 41 (?) for the tunnel traffic to work; do I need an equivalent rule for the wireless interface?

My dadvd.conf (generated by one of the scripts I've tried; I don't recall which) is:

interface br0 {
AdvSendAdvert on;
prefix 2001:x:y:x::/64 {
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};

My ipv6 addresses on the router are:

4: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500
inet6 fe80::x:x:x:304/64 scope link
valid_lft forever preferred_lft forever
5: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500
inet6 fe80::x:x:x:305/64 scope link
valid_lft forever preferred_lft forever
9: wifi0: <BROADCAST,MULTICAST,UP,10000> mtu 1500
inet6 fe80::x:x:x:306/64 scope link
valid_lft forever preferred_lft forever
10: br0: <BROADCAST,MULTICAST,PROMISC,UP,10000> mtu 1500
inet6 2001:x:y:x::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::x:x:x:304/64 scope link
valid_lft forever preferred_lft forever
13: ath0: <BROADCAST,MULTICAST,UP,10000> mtu 1500
inet6 fe80::x:x:x:306/64 scope link
valid_lft forever preferred_lft forever
16: he-ipv6@NONE: <POINTOPOINT,NOARP,UP,10000> mtu 1480
inet6 2001:x:x:x::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::d07b:7e5/128 scope link
valid_lft forever preferred_lft forever

On the client a 'ndp -n -cPR' initially showed a record for the link-local default gateway with a status of 'deleted', then when I restarted IPv6 services in didn't show anything, although I'm still getting the link-local default gateway and correct subnet for the auto assigned address.

I'm unable to ping6 any of the link-local (or the global) addresses shown on the router from the client.

I understand the WRT160NL has a rather odd wireless hardware system (and only recently supported); is this a matter of a bug in the firmware, or do I have a configuration error? Tips and suggestions?

thanks,

ch

[Twirrim]

Just been through this process myself.

I didn't have the ipv6 module in either pre-SP2 build of firmware for my WRT54GL. Not sure what was going on there, but got it to work with SP1.

The modprobe command in the section headed '# The following commands are straight from HE's website' is extraneous (and doesn't work anyway).

whatismyip.com doesn't seem to work any more, so I wasn't getting a public IP address which stopped the tunnels being created. I substituted it with icanhazip.com instead, however I can't help but think there should surely be a system variable or some way of getting that IP address from the router?

[Xenophore]

The new URL for automatically getting one's IP address is now http://automation.whatismyip.com/n09230945.asp.

[e1000v21]

*Edit: Problem solved by myself!!


Router Model Linksys E1000 v2.1
Firmware Version DD-WRT v24-sp2 (05/17/11) std-nokaid-small - build 17084M NEWD-2 K2.6 Eko

DD-WRT v24-sp2 std (c) 2011 NewMedia-NET GmbH
Release: 05/17/11 (SVN revision: 17084)

[ac1115]

I made a few changes to the script.

1- Optional NVRAM WAN IP Source)
External by default

You can now either use an external site for Wan IP or use the NVRAM. You can switch this easily by changing the setting.

I changed the whatismyip url to the new one. thanks xeno

The external wan ip site is also easily changed now. in case user wants to user another service or if the url changes again.

2- Optional Fetching IPv6 only DNS results
on by default

OpenDNS has a pubilicaly avilble ipv6 dns recursive server. The option in the script adds the dns server entries into /tmp/resolv.dnsmasq

You will need to be running dnsmasq (DHCP Server) for this to work.

This script will APPEND the OpenDNS dns server, not replace your existing settings.

[Kalkoen]

Very nice script, I've already used it for a few months and it always worked great! Thanks for the IPv6 DNS update

[xaero]

I'm unable to get this working, set up my tunnelbroker acct and copied the necessary info into a script, enabled the required ipv6 and radvd options and copied the script to the router and marked it as a startup script. I get the he-ipv6 interface on my router but I don't have any address assigned to it.

[ac1115]

Your routed 64 is incorrect. It should be an ipv6 addy

Also tunnel id cannot be 1. It's a 5 or 6 digit number.

[xaero]

[ac1115]

Look for the entry named routed 64. Tunnel Id is near top.

[xaero]

OK, cool, now that is working, when I try to ping 2001:470:1f06:d30::2 from another (gentoo) box on my lan, I get

[xaero]

Oh and modprobe doesn't exist in my router's firmware, insmod does though, which makes me think, if ipv6 is enabled by the web config, that loads the ipv6.o module, so why are you loading it again from the script? That's only going to produce more errors.

*EDIT*: Currently, I removed it from the startup script and am running the script manually via a CIFS mountpoint, so I can see exactly what the script does (besides hang for ~10sec). Which is where I saw the modprobe error and the last thing I see is RTNETLINK answers: File exists, not sure if this is important or not (prolly not since the interface already exists I would presume.)

[ac1115]

Insmod has no negative effect if run repeatedly

[VanillaXtract]

I owe you many thanks. I tried with no avail to get ipv6 working via the wiki. I found this post and followed it, rebooted, and bam! It works! Many thanks. I only wish I had tried this first. But if I did, I would not be as grateful since there would have been little reason to be .

[ac1115]