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
Flashed 19.07.06 via the sysupgrade process, keeping the existing configuration. After installation, the dnsmasq Resolve file setting was left with the following invalid path:
/tmp/resolv.conf.d/resolv.conf.auto
This path does not exist, resulting in dnsmasq failing to load. To fix and restore DNS forwarding, I changed the Resolve file setting to:
/tmp/resolv.conf.auto
which restored full functionality.
The text was updated successfully, but these errors were encountered:
Flashed 19.07.06 via the sysupgrade process, keeping the existing configuration. After installation, the dnsmasq Resolve file setting was left with the following invalid path:
/tmp/resolv.conf.d/resolv.conf.auto
Sounds like you have downgraded from a master snapshot to 19.07.6.
That downgrade path is not supported for dnsmasq.
The resolv directory in dnsmasq config was changed a year ago in January 2020 by dangowrt with commit cd48d8d:
Those commits effectively block downgrading from master to 19.07 unless you adjust the dnsmasq config to the dnsmasq 19.07 expectations.
I guess that this bug will end up with WONTFIX, as downgrading from a year 2020 or 2021 master build to a 19.07.x build (mainly with year 2019 code) is not really in focus.
Ps.
I include a config migration script in my own 19.07 builds, so that 6a28552 gets applied reverted when you move from master to 19.07.
ajleary19:
Netgear Nighthawk X4S R7800
Flashed 19.07.06 via the sysupgrade process, keeping the existing configuration. After installation, the dnsmasq Resolve file setting was left with the following invalid path:
/tmp/resolv.conf.d/resolv.conf.auto
This path does not exist, resulting in dnsmasq failing to load. To fix and restore DNS forwarding, I changed the Resolve file setting to:
/tmp/resolv.conf.auto
which restored full functionality.
The text was updated successfully, but these errors were encountered: