You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Static IPv6 routes configured in /etc/config/network that use a gateway within the ula address range are not properly restored on startup.
I managed to reproduce the issue in 19.07.7 and in the latest snapshot (17-04-2021). To reproduce the issue, do the following:
Setup a new OpenWRT system, for example in a VM. Uplink connectivity is not required, which makes it easy to reproduce the bug in a VM. Then edit /etc/config/network and add an IPv6 route using a gateway within the ula range. For example the entries may look like this:
Reboot the device and verify that the route is not present with ip -6 route show. Then modify the config a bit, for example replace the 43 in the gateway address with 42. Then execute reload_config and wait a few seconds. Then verify that the route is present with ip -6 route show. You may then reboot the device and the route will not be there anymore.
The text was updated successfully, but these errors were encountered:
I think after looking at the source code of netifd, I also know why this happens. First of all, the static IP addresses and routes for the interface are processed:
eriktews:
Static IPv6 routes configured in
/etc/config/network
that use a gateway within the ula address range are not properly restored on startup.I managed to reproduce the issue in 19.07.7 and in the latest snapshot (17-04-2021). To reproduce the issue, do the following:
Setup a new OpenWRT system, for example in a VM. Uplink connectivity is not required, which makes it easy to reproduce the bug in a VM. Then edit
/etc/config/network
and add an IPv6 route using a gateway within the ula range. For example the entries may look like this:Reboot the device and verify that the route is not present with
ip -6 route show
. Then modify the config a bit, for example replace the 43 in the gateway address with 42. Then executereload_config
and wait a few seconds. Then verify that the route is present withip -6 route show
. You may then reboot the device and the route will not be there anymore.The text was updated successfully, but these errors were encountered: