[22.03] RA,DHCPv6,NDP relay mode makes it impossible to connect to the IPv6 Internet. #9881
Comments
|
The contents of /etc/config/network: /etc/config/dhcp: /etc/config/firewall: |
|
The router's route list looked like this. |
pepe2k
added
target/mediatek
WinLinux1028
changed the title
|
Few days ago I did a "because I just want to mess up a little" setup. I make my old router Archer C7 v2 to connect to my main router in the WAN zone. I setup it just as you have, but, I could only be able to get neighbours by setting up also Anyways, despite I then get the neighbours discovered in the Archer C7, ipv6 connectivity was not possible in the connected devices to that router, only ipv4, and the router itself could do ipv4 and ipv6 just as you say. If you want check if setting ndp also in the wan interface could work for you. Check before Status -> Routes and see if neighbours appear, if not do the wan thing, restart the network interfaces and wait a sometime to see if some neighbours start to appear (I assume there are more devices conected to the router present in the wan zone). |
|
Anything we (users) can do to run this to ground? Package bisects, different configs, etc? |
|
I seem to be facing the same issue. I simply followed the IPv6 relay example in the wiki, to the same behavior described in OP: router can do IPv6, clients get IPv6 addresses but no connection. However, I do have something to add: I'm facing this issue with my new Belkin RT3200, but I've been using IPv6 on the same network, with the same settings running in 22.03 on the Archer C7 that was replaced. The only difference I can think of is, the C7 grandfathered the IPv6 settings from the previously installed OW versions instead of being freshly flashed like OW in the RT3200. (I manually redid all the settings on the RT3200 instead of taking a backup of C7 and applying it to the new device). The C7 still retains the settings so I'll post it here later. |
|
I checked, and really, there's no difference to post about: Archer C7: Belkin RT3200: Which is all the more confusing to me. Are there any other relevant settings that might be worth looking at? I've downloaded backup configurations of both to easily compare. |
|
I forgot to mention, both devices described are running OW 22.03.2. Today I discovered that IPv6 works on some devices. It's working on an old HP laptop I have where I tried to verify IPv6 on a whim. I made sure to try on other devices, my newer ASUS laptop and couple 4 year old Android phones but IPv6 didn't work on them. The Android phones connected on the same 802.11n SSID as the old laptop, so the problem is not specific to a radio. |
|
Wild. I'm also seeing this — some devices can connect, some can't. I see the packets reaching and maybe even fully traversing the openwrt node, but not working past that. |
|
Confirm that this problem still exists on OpenWrt 22.03.3 (MT7621 Netgear R6220) |
|
Confirm that this problem still exists on OpenWrt 22.03.5(MT7621) |
|
Confirm that this problem still exists on OpenWrt 22.03.3 (Linksys WRT1200AC) |
|
Confirm that this problem still exists on OpenWrt 22.03.5 (Xiaomi Mi Router 4C) |
|
Confirm that this problem still exists on OpenWrt 22.03.5 (D-Link DIR-882) One more thing is that I found IPv6 works after the client ping the WAN IP(of course IPv6) of the router. after ping: A new NDP item with the client's IP is created at the |
|
what I found is openwrt is not trying to discover the neighbor on lan(br-lan). it only tries it on wan6(eth0). (I masked my actual ipv6 prefix) and trying to ping this global ip on lan it failed. and then I found in the routing table, there is no route on lan for make the router ever be able to connect to the devices if using devices global ip. so I did this. after that it worked that proxy is added for any new connected device. |
|
@WinLinux1028 @howl @MentalPower @oxwivi @aredridel @Headcrabed @FLIER001 @weyou @sianzhan @cmd2001 @smilekevin Neither of these options are supported at all. Am I misunderstanding something? |
|
@bluewavenet I think DHCP related to IPv6 (RA, DHCPv6, NDP etc.) are handled by odhcpc (WAN side, as client to ISP) and odhcpd (LAN side, as server). Dnsmasq is used only for IPv4 DHCP stuff. |
|
@KA2107 |
|
I have the same problem😫. |
|
@KA2107 |
|
@bluewavenet I think is possible but not by only setting it in configuration, I think is needed to replace the package with a more complete one with ipv6 support that is not installed by default because the use of odhcpd. |
|
A Possible Solution is: Delete IPv6 ULA-Prefix from Global network options. |
|
I have the same issue as this comment in that I need to ping the wan ipv6 address of the router to get my linux or windows computer working. My android phone works without any issue though and immediately gets working ipv6 internet without needing to do anything |
|
As stated in my previous comments, on my previous OpenWrt router Archer C7 v5, IPv6 used to work with It worked for me, I have IPv6 on all of the clients on my network. Keep in mind, with the previous DHCPv6 NB For context, ISP assigns |
For Android/ChromeOS, DHCPv6 NEVER WORKS because Google decides not to support it (you can search), when you mention "sometimes working" probably because some of your configuration might have passed down the stateless to downstream. Technically you don't have to disable DHCPv6 for Android to work (it will ignore the not usable one), but for sake of simplicity, in my guide I chose to disable DHCPv6 entirely so that I don't have to manage both (imagine you are looking at DHCPv6 lease however only a few entries there) |
Yes, I did see your referenced links about Google's response. But with my previous router, I'm pretty sure all of my machines had working IPv6, with all Anyhow, this neither on-topic nor fruitful to argue about what I may or may not remember; I'll refrain from commenting further. |
|
In my environment, even though some clients can obtain a public v6 address, they are unable to communicate via v6. The same happens when I ping outside the WAN, it becomes possible to communicate via IPv6. When I ping, the client gets added to the neighbor list. Entries for the client’s address are also added to the routing table. It seems that the management of entries is done by this: https://github.com/openwrt/odhcpd/tree/master It might be good to investigate what kind of communication the clients that don’t have an entry added are triggering. |
|
According to the information on https://openwrt.org/docs/techref/odhcpd, the updated version of https://datatracker.ietf.org/doc/html/rfc6204, which is https://tex2e.github.io/rfc-translater/html/rfc7084.html, states that
Following this, as mentioned in #9881 (comment), I found that removing the IPv6 ULA-Prefix allowed clients to communicate without needing to ping. However, it seems to take tens of seconds for communication to be established. Instead of 'This prefix is randomly generated at first install,' having a default empty field might be a better option. |
|
opkg install owipcalc ifdown_cb() { } case "$ACTION" in exit 0 ip6tables -I INPUT -p ipv6-nonxt -m length --length 40 -j ACCEPT ip6tables -I input_rule -i eth0 -p ipv6-icmp --icmpv6-type 1 -m limit --limit 100/s --limit-burst 10 -j ACCEPT ip6tables -I forwarding_rule -i br-lan -p ipv6-icmp --icmpv6-type 1 -m limit --limit 100/s --limit-burst 10 -j ACCEPT 网络--接口--全局网络选项，IPv6 ULA 前缀：空 /etc/config/dhcp 如下 config dhcp 'wan' config dhcp 'wan6' |
I'm using latest 22.03 snapshot on Linksys E8450.
Here is a list of what I know about this issue.
The text was updated successfully, but these errors were encountered: