We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
odhcp6c - 2023-05-12-bcd28363-20 odhcpd-ipv6only - 2023-10-24-d8118f6e-1
Log shows this:
Thu Sep 26 16:59:12 2024 daemon.info odhcpd[7832]: Address 2607:fa18:9ffe::1 (dprefix 0, valid 8617466) not suitable as RA route on lan
root@gw-xm-wr1200:~# ip a sh br-lan 15: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000 link/ether 00:01:9f:0a:1a:ec brd ff:ff:ff:ff:ff:ff inet 192.168.12.1/24 brd 192.168.12.255 scope global br-lan valid_lft forever preferred_lft forever inet 166.70.97.193/29 brd 166.70.97.199 scope global br-lan valid_lft forever preferred_lft forever inet6 2607:fa18:9ffe::1/56 scope global dynamic noprefixroute valid_lft 2578115sec preferred_lft 590915sec inet6 fe80::201:9fff:fe0a:1aec/64 scope link valid_lft forever preferred_lft forever config dhcp 'lan' option interface 'lan' option start '100' option limit '150' option dhcpv4 'server' option leasetime '12h' option ra 'server' option dhcpv6 'server' option ra_default '2'
Why does it think that 2607:fa18:9ffe::1 is not suitable?
It looks like SLAAC and/or "auto" systems do get a route, but dhcpv6 systems do not. Perhaps the error log is not stopping RA packets?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
odhcp6c - 2023-05-12-bcd28363-20
odhcpd-ipv6only - 2023-10-24-d8118f6e-1
Log shows this:
Thu Sep 26 16:59:12 2024 daemon.info odhcpd[7832]: Address 2607:fa18:9ffe::1 (dprefix 0, valid 8617466) not suitable as RA route on lan
Why does it think that 2607:fa18:9ffe::1 is not suitable?
It looks like SLAAC and/or "auto" systems do get a route, but dhcpv6 systems do not. Perhaps the error log is not stopping RA packets?
The text was updated successfully, but these errors were encountered: