Hi,
I think I have spotted a bug on GL-X2000 (Spitz Plus)
It happens both on 4.8.2beta and snapshot
It seems that wireguard breaks DNS. This is the log:
Sun Mar 29 12:24:08 2026 daemon.notice netifd: Interface 'wgclient1' is now up
Sun Mar 29 12:24:08 2026 daemon.notice netifd: Network device 'wgclient1' link is up
Sun Mar 29 12:24:08 2026 user.notice firewall: Reloading firewall due to ifup of wgclient1 (wgclient1)
Sun Mar 29 12:24:10 2026 daemon.crit dnsmasq[25415]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Sun Mar 29 12:24:15 2026 daemon.crit dnsmasq[25570]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Sun Mar 29 12:24:20 2026 daemon.crit dnsmasq[25643]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Sun Mar 29 12:24:25 2026 daemon.crit dnsmasq[25784]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Sun Mar 29 12:24:30 2026 daemon.crit dnsmasq[25857]: bad option at line 1 of /tmp/dnsmasq.d.wgclient1/mark
Sun Mar 29 12:24:30 2026 daemon.info procd: Instance dnsmasq::wgclient1 s in a crash loop 6 crashes, 0 seconds since last crash
This is the content of the file that seems to be corrupt:
root@GL-X2000:~# cat /tmp/dnsmasq.d.wgclient1/mark
mark=0x1000
I know this issue has already been reported on 4.8beta in other models (e.g. Beta 4.8.0 op24 issues) but what seems really strange is that this was fixed in other models but not in Spitz Plus (neither in 4.8.2beta or snapshot)
Could someone of the staff take a look on it? Does anyone know a workaround?
Thanks a lot!