Bogey
Regular Contributor
@saison2023 and I have been running some tests as we have the same hardware and plugins installed.I had similar dnsmasq fatal errors with 388.2. With that release, dnsmasq is version 2.89. With the 388.1 release, it was 2.85.
I am now running 388.2 with the dnsmasq from 388.1. No more fatal errors.
If you still have 388.1 running, you can copy dnsmasq version 2.85 from that release (from /usr/sbin) to a usb stick, install 388.2 then copy the dnsmasq 2.85 binary to either /jffs or /opt (if Entware is installed). Then do what’s called a mount bind.
For example, I copied dnsmasq (v2.85) to /opt/tmp/sbin.
Then I ran this mount command:
mount -o bind,rw /opt/tmp/sbin/dnsmasq /usr/sbin/dnsmasq
Restert dnsmasq:
service restart_dnsmasq
Keep in mind, on a reboot, you will be back to dnsmasq 2.89 (unless you redo the mount and restart).
This is all temporary until the dnsmasq folks track down this issue.
In my case I was getting 2-3 dnsmasq Fatal 6 errors/day. Reverting to 2.85 a few days ago - none.
I too found that with dnsmasq logging disabled in Diversion fixes 'the problem'.
Your solution of using the old dnsmasq is a good find, thank you!
I do wonder if it's a bug in dnsmasq or that it could be fixed by
Last edited: