I also have it set to dynamically update the HE ip through DNS-o-matic, this is working perfectly.
However, when I did `ping -6 ipv6.google.com` or run any other IPV6 test, it times out. What am I doing wrong?
Edit: Well IPv6 works fine when I am physically behind my network now but for some reason it does not work across the VPN I have setup through DD-WRT (IPv6 is enabled in Windows)
What build are you using ? Not all builds have working IPv6... _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
Posted: Fri May 15, 2015 12:43 Post subject: Static IPV6 address
Hi
I have a WNDR 3700v4 running v24-sp2 (05/09/15) std - build 26866. I've got an IPV6 6in4 tunnel configured via SIXXs, which is working fine. Now i want to configure it to issue static IPv6 addresses to the devices on my LAN. I'm trying to set up a web and email server up.
I've tried activating DHCP6s on the IPv6 page with the following custom entry:
At the moment I have this working on my WNDR3700v2 with dd-wrt build 27456 using a tunnelbroker.net 6in4 tunnel.
I get the impression that QoS isn't working for IPv6 connections, but it's difficult to tell for sure. But it seems that running several IPv6 downloads can almost completely block everything else and seem to exceed the download limit I entered on the QoS page.
Is there an equivalent guide for SixXS? It seems to use some extra software for it, but the software seems to provide DDNS by itself, and the service seems to have more tunnel endpoints to choose from.
Is there an equivalent guide for SixXS? It seems to use some extra software for it, but the software seems to provide DDNS by itself, and the service seems to have more tunnel endpoints to choose from.
It should be the same unless you need to deal with your IPv4 address changing (i.e. you have a dynamic IP on your IPv4 connection).
For dynamic IP SixXS make you use their "heartbeat" protocol and a program called aiccu to tell them when your IP changes.
You can run aiccu in your dd-wrt router. I did it (don't remeber exactly how). But what I didn't realize was that although it's called "heartbeat" they do not expect regular packets from aiccu to them unless your IP address changes.
Just me rebooting my router as I experimented with the settings, thus restarting the aiccu program each time, was enough to make them send an email accusing me of "hammering" their server.
I just gave up with them. I haven't got the time for dealing with idiots that design things to make it hard to use them and name things so as to mislead you about the way they work.
I didn't like their attitude anyway. To get started you have to email them setting out why you think you deserve to be allowed access to their service.
It should be the same unless you need to deal with your IPv4 address changing (i.e. you have a dynamic IP on your IPv4 connection).
For dynamic IP SixXS make you use their "heartbeat" protocol and a program called aiccu to tell them when your IP changes.
You can run aiccu in your dd-wrt router. I did it (don't remeber exactly how). But what I didn't realize was that although it's called "heartbeat" they do not expect regular packets from aiccu to them unless your IP address changes.
Just me rebooting my router as I experimented with the settings, thus restarting the aiccu program each time, was enough to make them send an email accusing me of "hammering" their server.
Yeap, I do need to deal with dynamic IPv4. I assume you ran aiccu through optware? In which case for most people that's probably much harder to set up than DNS-o-matic like in the OP.
The fact that they can accuse you of using heartbeats too often sounds strange; aiccu is their software, so why wouldn't they design it to not call back too often or make the heartbeats themselves trivial...
Yeap, I do need to deal with dynamic IPv4. I assume you ran aiccu through optware? In which case for most people that's probably much harder to set up than DNS-o-matic like in the OP.
The fact that they can accuse you of using heartbeats too often sounds strange; aiccu is their software, so why wouldn't they design it to not call back too often or make the heartbeats themselves trivial...
I just checked and the aiccu binary seems to be included in dd-wrt. I think I had to enable jffs2 to create a non volatile place to store a configuration file for aiccu.
I think I started aiccu from one of the scripts you can create from the web interface.
I can't try again, I think I'm now banned for life from SixXS because I didn't immediately write a grovelling apologetic email to them.
I'm having some trouble getting a HE tunnel working.
I followed all the instructions in the first post, but the router is unable to ping any ipv6 address not on the LAN.
I'm using DD-WRT v3.0-r27506 on a WZR-HP-AG300H. I'm wondering is I have a build with broken ipv6, but I'l like to rule out any misconfigurations first.
Does anyone know what might be wrong with this configuration?
Thanks.
Code:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 75.101.54.1 0.0.0.0 UG 0 0 0 eth1
75.101.54.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br0
Code:
# route -n -A inet6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
2001:470:20::2/128 :: UC 0 1 0 ip6tun
2001:470:66:796::/64 :: U 256 0 0 ip6tun
2001:470:67:796::/64 :: U 256 0 0 br0
2607:f8b0:4005:803::200e/128 :: UC 0 4 1 ip6tun
2000::/3 :: U 1024 0 2 ip6tun
fe80::/64 :: U 256 0 0 br0
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 ath0
fe80::/64 :: U 256 0 0 ath1
fe80::/64 :: U 256 0 0 eth1
::1/128 :: U 0 1 1 lo
2001:470:66:796::/128 :: U 0 0 1 lo
2001:470:66:796::2/128 :: U 0 0 1 lo
2001:470:67:796::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::4b65:361a/128 :: U 0 0 1 lo
fe80::b2c7:45ff:fe76:2ff6/128 :: U 0 4 1 lo
fe80::b2c7:45ff:fe76:2ff6/128 :: U 0 0 1 lo
fe80::b2c7:45ff:fe76:2ff6/128 :: U 0 0 1 lo
fe80::b2c7:45ff:fe76:2ff7/128 :: U 0 0 1 lo
fe80::b2c7:45ff:fe76:2ff7/128 :: U 0 0 1 lo
ff02::1/128 :: UC 0 23 0 br0
ff00::/8 :: U 256 0 1 br0
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 ath0
ff00::/8 :: U 256 0 0 ath1
ff00::/8 :: U 256 0 0 eth1
ff00::/8 :: U 256 0 0 ip6tun
I'm having some trouble getting a HE tunnel working.
...
I don't understand much of that but I found I needed the tunnel MTU to be 40 bytes less than the MTU of my IPv4 connection. Your's seems to me 1480 which, I think, is too high.