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
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.
The text was updated successfully, but these errors were encountered:
acu:
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.
The text was updated successfully, but these errors were encountered: