I get a X:Y:Z:C900::/64 IP assigned to vlan2 and a X:Y:Z:C9f1::/60 IP assigned to br0. Linux boxes connected to br0 also get X:Y:Z:C9f1:: addresses.
dd-wrt routes:
Code:
X:Y:Z:c900:cf21:d288:3c14:9e96 dev vlan2 proto kernel metric 256
X:Y:Z:c900::/64 dev vlan2 proto kernel metric 256 expires 534122sec
X:Y:Z:c9f1::/64 dev br0 proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
fe80::/64 dev vlan1 proto kernel metric 256
fe80::/64 dev eth1 proto kernel metric 256
fe80::/64 dev eth2 proto kernel metric 256
fe80::/64 dev br0 proto kernel metric 256
fe80::/64 dev vlan2 proto kernel metric 256
default via fe80::ae22:5ff:fe1d:4a78 dev vlan2 proto ra metric 1024 expires 1798sec hoplimit 64
unreachable default dev lo proto kernel metric -1 error -101
ff00::/8 dev eth0 metric 256
ff00::/8 dev vlan1 metric 256
ff00::/8 dev eth1 metric 256
ff00::/8 dev eth2 metric 256
ff00::/8 dev br0 metric 256
ff00::/8 dev vlan2 metric 256
unreachable default dev lo proto kernel metric -1 error -101
Node routes:
Code:
X:Y:Z:c9f1::/64 dev enp0s31f6 proto kernel metric 256 expires 3575sec pref medium
fe80::/64 dev enp0s31f6 proto kernel metric 256 pref medium
default via fe80::526a:3ff:fec0:168c dev enp0s31f6 proto ra metric 1024 expires 1775sec hoplimit 64 pref medium
All internal nodes are able to communicate with no problem. Internal nodes are able to ping the global ipv6 address of both br0 and vlan2. The router is able to ping all internal nodes AND ipv6.google.com.
The problem: internal nodes are not able to ping externally. The built in ping tool on the Unity Media modem is also not able to ping the br0 IP (the vlan2 IP is OK). So it appears there are still some routing issues on one or both of the router and modem. Any ideas? Note, there is no ability to set static routes on the Unity Media modem.
I tried that because I was seeing "update_ia: status code for PD-1: no prefixes" in the log. It didn't help but I never changed back to sla-id 0.
An update -- after about 3 days all of a sudden everything started working. But as soon as I rebooted the router it was back to the same problem. I played around with doing factory resets on both the modem and the router in various orders and was able to get it to work once more, but never consistently. Right now it is back in the original state (LAN nodes can not reach internet). I see no difference between the NIC configurations and ip -6 routes on either the LAN nodes or the routers between when it is working and when it is not. radvd output seems identical as well. At a loss.
I had actually tried adding "prefix ::/60 infinity" but it didn't change anything.
I switched to the Advanced Tomato build (1.28.0000 -3.4-140 K26ARM USB AIO-128K) and everything just works -- been running for almost 48 hours with multiple reboots and zero issues. So there appears to be some issue between dd-wrt (dhcp6c?) and UnityMedia's Connect Box.
I have an old Linksys WRT400N I may try dd-wrt on when I get a little time. Now that I have a working config to test against.
Now, I have only started investigating the issue, which I have experienced that vanished after a reboot of my router.
For me the problem was that the default ipv6 route vanished in Ubuntu. If I requested to get the network connection setup again for my Ubuntu-computer, then it worked, but only for some time (minutes) and the route was gone again.
I poked around a lot but according to my initial search it 'seems' that the first 'Router Advertisement' first came after 400 seconds into my wireshark session - but I had started to poke to the router so I am not completely sure of all my steps before it started to work again besides rebooting the router.
Should it happen for me again I will continue from there. But it is actually a good situation that your experience is that the problem keeps showing up as it might be easier then to pinpoint where the problem is.
If you use Linux on your computer or maybe Mac you might want to run a:
Code:
netstat -nr -6
On Linux you would need to have a route that looks like:
Code:
::/0 fe80::2332:0101:abcd:ef12 UG 100 3 3 eth0
If that route is gone, then you will no access outside of your LAN via ipv6.
