Hi there,
My tunnel worked over months flawlessly but now no traffic gets to the server tunnel endpoint dns queries work though
PING www.google.com(2a00:1450:4008:c01::68) 56 data bytes
--- www.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016ms
I tried to ping the endpoint server but I don't get any results either.
I'm using a linksys wrt54gs with dd-wrt, I reset the device just to check if it's not router related, I used the config from the dd-wrt config thread http://www.dd-wrt.com/phpBB2/viewtopic.php?p=669563 (http://www.dd-wrt.com/phpBB2/viewtopic.php?p=669563), still nothing works
startup script
ip tunnel add he-ipv6 mode sit remote 216.66.84.46 ttl 64
ip link set he-ipv6 up
ip addr add 2001:470:1f14:1b1b::2/64 dev he-ipv6
ip route add ::/0 dev he-ipv6
ip addr add 2001:470:1f15:1b1b::/64 dev br0
sleep 5
radvd -C /tmp/radvd.conf
radvd config
interface br0 {
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
AdvLinkMTU 1480;
AdvSendAdvert on;
prefix 2001:470:1f15:1b1b::/64 {
AdvOnLink on;
AdvAutonomous on;
AdvValidLifetime 86400;
AdvPreferredLifetime 86400;
};
RDNSS 2001:470:20::2 {};
};
routing table
2001:470:1f14:1b1b::/64 via :: dev he-ipv6 metric 256 mtu 1472 advmss 1412
2001:470:1f15:1b1b::/64 dev br0 metric 256 mtu 1500 advmss 1440
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440
fe80::/64 dev vlan0 metric 256 mtu 1500 advmss 1440
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440
fe80::/64 dev br0 metric 256 mtu 1500 advmss 1440
fe80::/64 dev vlan1 metric 256 mtu 1500 advmss 1440
fe80::/64 via :: dev he-ipv6 metric 256 mtu 1472 advmss 1412
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440
ff00::/8 dev vlan0 metric 256 mtu 1500 advmss 1440
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440
ff00::/8 dev br0 metric 256 mtu 1500 advmss 1440
ff00::/8 dev vlan1 metric 256 mtu 1500 advmss 1440
ff00::/8 dev he-ipv6 metric 256 mtu 1472 advmss 1412
default dev he-ipv6 metric 1024 mtu 1472 advmss 1412
If someone could help me bringing back ipv6 to my router...
EDIT:
hi there,
The Problem is solved now, tunnel wasn't configured right on the HE side, but they corrected it really fast
thanks broquea for pointing to the problem.
greetings
RJ
Assuming that is actually your tunnel's /64, I don't think your tunnel interface on HE's side is configured anymore. Try making sure your IPv4 endpoint is up-to-date, and that you see the tunnel in the broker's webUI. Also try emailing ipv6@he.net and see if they can push out your tunnel config on their side.
--- 2001:470:1f14:1b1b::1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3024ms
I don't see any rDNS on that IP or the ::2, so if you are obfuscating your tunnel IP, don't. Makes it hard to troubleshoot. If it is your allocation, bug them to push out rDNS as well :)