OpenWrt/LEDE Project

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Base system
  • Assigned To No-one
  • Operating System All
  • Severity Medium
  • Priority Very Low
  • Reported Version openwrt-18.06
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Daniel - 14.10.2019

FS#2553 - dns name resolution with dnsmasq does not work after reboot

I’ve got a bunch of GL-MT300A devices suffering from this issue. They are configured as simple openvpn gateway behind a DSL router. There is no WIFI active, no WAN port, just a LAN interface and openvpn. Dnsmasq is used only for name resolution, and not for DHCP.

After upgrading the device from LEDE 17.01 to OpenWrt 18.06.4 r7808-ef686b7292 (latest stable version according to the website) DNS resolution failes after a reboot of the system.

Even though dnsmasq is up and running (ps shows the deamon, and netstat -tulpen shows the deamon listing to port 53 as it should be) name resolution is not working, preventing openvpn to find its servers.

After restarting dnsmasq (/etc/init.d/dnsmasq restart) name resolution starts to work as expected.

I noticed that /tmp/etc/dnsmasq.conf differes between the reboot of the router and the restart of dnsmasq.
The following line appears in the config file after restarting dnsmasq manually:

no-dhcp-interface=br-lan

Adding /etc/init.d/dnsmasq restart to /etc/rc.local seems to be a workaround for the moment.


Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing