New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#3657 - dnsmasq listen on the wrong address after the PPP update #8692
Comments
jow-: Can you provide the output of Would also be interesting to modify package/network/services/ppp/files/lib/netifd/ppp6-up in order to dump the $LLLOCAL value passed by pppd to the up script. |
castiel652: I can do that when I get home. Where and what should I modify in the script? |
jow-: Something like "logger -t debug "LLLOCAL=$LLLOCAL" near the top should suffice. You should see a corresponding line in |
castiel652: This is one is the output of "ifstatus wan" before reverting the commit and I attached the output of LLLOCAL at the top |
castiel652: After reverting the commit |
castiel652: LLLOCAL is the same as the ipv6-address in the output for both |
jow-: And in the broken case, LLLOCAL contains the remote LL address and not the local one? |
castiel652: LLLOCAL contains the local one in the broken case |
slh:
Edit: While it took considerably longer to trigger, this didn't actually avoid the issue in the end: |
castiel652: I did the same and still having the same problem |
castiel652:
dnsmasq starting to listen on it because it's now correctly set. EDIT: that's not the problem |
castiel652:
Sun Mar 21 14:47:21 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
Sun Mar 21 14:47:21 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
Sun Mar 21 14:52:03 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
Sun Mar 21 14:52:03 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
Sun Mar 21 14:56:31 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
Sun Mar 21 14:56:31 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
Sun Mar 21 15:01:06 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
Sun Mar 21 15:01:06 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
Sun Mar 21 15:06:00 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
Sun Mar 21 15:06:00 2021 daemon.warn dnsmasq[9758]: failed to create listening socket for RRLOCAL%pppoe-wan: Address not available
|
castiel652:
root@openwrt:~# cat /etc/config/network
root@openwrt:~# cat /etc/config/dhcp
|
castiel652: I did something wrong when testing the PPP commit. The problem really is this commit [[https://github.com/ppp-project/ppp/commit/c3af52231184ade3cf728ec60c9de9e87c2622ad]] |
val-kulkov: I am observing the same problem. In my case, the error message is: dnsmasq[24965]: failed to create listening socket for fe80::200:ff:fe00:0%pppoe-wan: Address not available Here is my configuration (the public IPv6 address has been obfuscated): root@openwrt:~# ip -6 address show dev pppoe-wan root@openwrt:~# ip -6 route show dev pppoe-wan Note that LLLOCAL is fe80::1d8:5efd:9947:1f55 and RLLOCAL is fe80::200:ff:fe00:0. "ip -6 addr" shows only LLLOCAL, which is correct. I do not understand why "ip -6 route" lists a routing destination for RLLOCAL at all (fe80::200:ff:fe00:0 dev pppoe-wan metric 256), but as long as RLLOCAL is routed to "dev pppoe-wan" it does not create a problem I think. For some reason, dnsmasq thinks RLLOCAL is a local address and attempts to listen on that address, which apparently cannot succeed. As a workaround, I added "list notinterface 'pppoe-wan'" to the "config dnsmasq" section in /etc/config/dhcp to prevent dnsmasq from listening on pppoe-wan interface. But why RLLOCAL appears as a local address for dnsmasq in the first place? |
oliver44: Hello all, I have the following log in system log and I have seen that for some time it persists in the latest version of OpenWrt protocol PPPoE ipv6 on, does anyone know where the problem is ? Hostname OpenWrt Firmware Version OpenWrt SNAPSHOT r18437-92820cc5b9 / LuCI Master git-21.357.58153-63d9bcb Tue Dec 28 20:17:04 2021 daemon.warn dnsmasq[14805]: failed to create listening socket for fe80::1%pppoe-wan: Address not available |
oliver44: config interface 'loopback' config globals 'globals' config device config interface 'lan' config device config interface 'wan' config interface 'wan6' root@OpenWrt:~# cat /etc/config/dhcp config dnsmasq config dhcp 'lan' config dhcp 'wan' |
oliver44: root@OpenWrt: |
castiel652:
With PPP version 2.4.9 dnsmasq would try to listen on remote LL address instead of local LL address which spams the log with
daemon.warn dnsmasq[4528]: failed to create listening socket for xxx::xx:xx:xxx:xxx%pppoe-wan: Address not available
That doesn't happen anymore after I revert the commit 030bc39
The text was updated successfully, but these errors were encountered: