After updating my Mudi 7 to firmware 4.10.0, my WireGuard client connection to my FritzBox (single-device VPN) stopped working correctly. The router reported:
Primary Tunnel IP Address (192.168.0.102/24) is in conflict with wlan4.
My main LAN is 192.168.8.x and my guest network is 192.168.9.x, so this wasn't a config I set myself — it looks like an interface (wlan4) came up with a 192.168.0.0/24 subnet after the update, which collided with the WireGuard tunnel address assigned by my FritzBox.
I did a full factory reset, and the exact same conflict reappeared — so this seems to be a default introduced by the update itself, not a leftover config issue.
Looking at the 4.10.0 release notes, I suspect this is related to the "Subnet: Refines subnet management to streamline the centralized configuration of main and guest network parameters" change, combined with the new "proactive IP and DNS conflict detection" for VPN — possibly the underlying overlap existed before too, but wasn't actively flagged/blocked until this release.
Fix: I downgraded back to firmware V4.8.5, and the WireGuard connection works again without any changes on my end.
Posting this in case others hit the same issue after updating to 4.10.0 — and so GL.iNet support can take a look at the wlan4 subnet default.
Device: GL-E5800 (Mudi 7)
Firmware: 4.10.0 → downgraded to V4.8.5
I’m sorry but this firmware seems to be broken. The screen wouldn’t light up after resetting the device. I couldn't turn the screen on at all. I didn’t observe the pattern but it was alarming when i saw the wifi on (on my phone) and no screen to disable it. This is a huge security issue with regards to close quarters threats, when one is expecting the screen to function predictably. I promptly reverted to previous firmware.
We tested a similar WireGuard configuration on a Mudi 7 running firmware 4.10.0, using 192.168.0.102/24 as the WireGuard interface address, but we have not been able to reproduce the conflict with wlan4 warning.
Could you please let us know how the Mudi 7 was connected to the Internet when the issue occurred — Cellular, Ethernet, or Repeater?
If Ethernet was using DHCP, could you please also let us know the IP address/subnet and gateway assigned to the Mudi 7 by the upstream router.
If convenient, when the issue occurs again on firmware 4.10.0, could you please run the following commands and share the output with us?
Thanks for looking into this. To answer your questions:
Connection type: The Mudi 7 was connected as a repeater within my home network (connecting to my FritzBox's Wi-Fi as the upstream).
VPN setup: The WireGuard server was the FritzBox itself, using its "connect single device" feature — so the VPN client (Mudi 7) and the VPN server (FritzBox) were in the same home network, not connecting from an external network.
I'm currently on vacation, but I could update back to 4.10.0 afterwards to reproduce the issue and provide the ip -4 addr, iw dev, and bridge link show output then.
We checked the GL.iNet Download Center and were able to download the Mudi 7 firmware normally, and the firmware upgrade also completed successfully on our test device.
I am running into a similar issues as this, but on wan3. I am using the Mudi 7 as a repeater on a hotel guest network and am unable to connect to my VPN. Both my wireguard home vpn and protonvpn. I used the admin page to upgrade to the latest firmware and just now also installed the latest firmware from the linked above page. Both ways I get this error message:
Primary Tunnel IP Address (10.2.0.2/32) conflicts with the wlan3
