Forum - IPv6 stopped working after router reboot (OpenWRT) :: SixXS

IPv6 stopped working after router reboot (OpenWRT)

Shadow Hawkins on Wednesday, 27 July 2011 13:54:31

I rebootet my router because i had to disconnect the AC. After that IPv6 stopped working. Can't get any incoming traffic. This is strange, since i didn't change anything. sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2001:6f8:900:6ae::2/64 Scope:Global inet6 addr: fe80::5842:1c2e/64 Scope:Link inet6 addr: fe80::c0a8:101/64 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:1246 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:107434 (104.9 KiB) Is it normal, that i have two fe80:: adresses? Also my clients get two seperate 2001:: adresses.. root@OpenWrt:~# ip -6 route show 2001:6f8:900:6ae::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 2001:6f8:13a9::/64 dev br-lan metric 256 mtu 1500 advmss 1440 2001:6f8:13a9::/64 dev br-lan metric 1024 mtu 1500 advmss 1440 2000::/3 via 2001:6f8:900:6ae::1 dev sixxs metric 1024 mtu 1280 advmss 1220 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220 fe80::/64 dev br-lan metric 256 mtu 1500 advmss 1220 fe80::/64 dev eth0.0 metric 256 mtu 1500 advmss 1220 fe80::/64 dev eth0.1 metric 256 mtu 1500 advmss 1220 fe80::/64 dev wl0 metric 256 mtu 1500 advmss 1220 fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220 ff00::/8 dev br-lan metric 256 mtu 1500 advmss 1220 ff00::/8 dev eth0.0 metric 256 mtu 1500 advmss 1220 ff00::/8 dev eth0.1 metric 256 mtu 1500 advmss 1220 ff00::/8 dev wl0 metric 256 mtu 1500 advmss 1220 ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 default via 2001:6f8:900:6ae::1 dev sixxs metric 1024 mtu 1280 advmss 1220 Also, as i remember i only had one 2001:...... dev br-lan routing, but it also doesn't work if i delete one of them. Any ideas why it stopped working now? Thanks for your ideas.

IPv6 stopped working after router reboot (OpenWRT)

Jeroen Massar SixXS Staff

on Wednesday, 27 July 2011 15:10:19

sixxs Link encap:IPv6-in-IPv4

But what are the source/destination addresses?

Is it normal, that i have two fe80:: adresses?

On Ethernet interfaces no, but on a tunnel interface it sort-of makes sense as each is based on the two link-layer address that are below it: 88.66.28.46 and 192.168.1.1 Which at least shows that you most likely have a public IPv4 address which is a good thing.

Also my clients get two seperate 2001:: adresses..

Most likely they get a real address based on EUI-64 and a privacy address which is randomly calculated. The latter can be disabled, but depends on the OS how that is done. Showing the addresses would help....

Also, as i remember i only had one 2001:...... dev br-lan routing, but it also doesn't work if i delete one of them.

Maybe one is from adding an address to the interface and the other is from adding a route? You might want to check which addresses those are and if you maybe are running two radvds or so. The more details you provide the better, that is what that big yellow/orange box which is shown twice when posting is there. A traceroute to your unicast address ends up at your side: 13 2001:6f8:1:0:87:86:71:233 (2001:6f8:1:0:87:86:71:233) 35.032 ms 26.289 ms 25.277 ms 14 deham01.sixxs.net (2001:6f8:800:1003::2) 41.719 ms 40.691 ms 41.205 ms 15 2001:6f8:13a9:: (2001:6f8:13a9::) 90.782 ms 95.171 ms 95.118 ms Thus I don't think it is a problem on the PoP from that perspective at least.

Please note Posting is only allowed when you are logged in.