I did so as above. configured it in port 53 an d dnsmasq moved to 54. thank you
it seems to be working okay but possibly there is a very minute delay (text seems to load first and then images in some pages)in comparison to when I was using smartdns ( that doesnt block ads).
I wonder whether very slight delay is expected?
In luci, the version ( v0.107.42) is one behind the latest ( v0.107.43). How to update it?
I am having issues with mine, I installed it today, and in the morning I could connect all my devices in the wifi but suddenly now no device can’t be connected to, I have reset the router to factory config but the problem persists, I find the Wifi in my list but all the time appears “couldn’t connect to network” or "couldn’t get the IP’, now I coonect my wifi mesh system to the lan to get wifi, how to solve it? or my device is broken?
What I mean is that you should check each firewall port forward to see if it contains “tcpudp” and if it does delete it and select the TCP and UDP checkboxes.
I think issues like this occur because GL.iNet’s UI was originally designed around an older version of OpenWrt and they’ve failed to updated it for newer versions. And that’s also why LuCi displays the “network ifname configuration migration” screen the first time you attempt to view the interfaces.
Since OpenWrt maintains their own fork you’ll probably receive an update next week.
Normally that line goes at the end of the file. But you’d need to reboot your router and then you can input cat /sys/module/mt7915e/parameters/wed_enable into PuTTY. If it returns Y then it’s enabled.
The latency at 2.4ghz is really unbearable. A workaround is not to use the “AX” mode but the “N” mode, the speed is lower on computers with a WiFi 6 card, but the latency on other devices is acceptable.
If the reset doesn’t work then you could try to flash the firmware via Uboot. But if that doesn’t fix it then one of the staff might ask you for log files next week.
I’m on 4.5.4 and once a day, the wi-fi ‘crashes.’ Both 5 and 2.4 Ghz devices say unable to authenticate. After rebooting the Flint 2, all connections are restored.