Mudi V2 Cannot reach any device in LAN on Windows

Technical Support for Routers
1

Hello.

This is a really weird issue I have. On my laptop I have Windows 11 and I can connect to Mudi but I can't reach/ping the gateway (192.168.8.1) nor a second connected device (a phone) from Windows 11. I always get a timeout. However I can reach the internet fine (using the port on the extender bundled with Mudi as a WAN port)...

When using the phone, I can normally reach the gateway via web or the app as well as ping the laptop and then it does respond back (ping phone -> laptop works, ping laptop -> phone/gateway doesn't).

I dual booted Linux on the laptop and everything worked normally, so it is an issue in Windows I guess..?

I guess something is up with my network config/driver in Windows? Can anybody help please? I have not experienced this with any other WiFi router.

2

Please check your Windows network settings. Are they DHCP? What about the DNS servers?

3

ipconfig:

Wireless LAN adapter WiFi 2:

   Connection-specific DNS Suffix  . : lan
   Description . . . . . . . . . . . : Intel(R) Wi-Fi 6E AX210 160MHz
   Physical Address. . . . . . . . . : <MAC address>
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::937:d22a:6c7f:a344%20(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.8.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : pondelok 19. augusta 2024 12:35:56
   Lease Expires . . . . . . . . . . : utorok 20. augusta 2024 0:35:55
   Default Gateway . . . . . . . . . : 192.168.8.1
   DHCP Server . . . . . . . . . . . : 192.168.8.1
   DHCPv6 IAID . . . . . . . . . . . : 350414656
   DHCPv6 Client DUID. . . . . . . . : 00-03-00-01-E2-E7-40-38-7B-7C
   DNS Servers . . . . . . . . . . . : 8.8.8.8
   NetBIOS over Tcpip. . . . . . . . : Enabled

As I said, connection to WAN/Internet works, only to LAN doesn't. My normal home WiFi works fine when connected to it.

4

Wait wait wait.

What are you trying to reach? Some devices outside of the current subnet 192.168.8.x?

5

I am trying to reach gateway or anything really in 192.168.8.x subnet, which doesn't work on the Windows laptop and that's my problem.

I was just trying to open router settings (on 192.168.8.1) on the laptop with Win11. I can open the web UI via phone, but it doesn't work on the laptop. Then I tried to ping other devices on 192.168.8.x subnet, I cannot reach any. For some reason it looks like the Windows laptop is "isolated" from the other devices, even from gateway, even though Internet somehow works.

arp -a output:

Interface: 192.168.8.125 --- 0x14
  Internet Address      Physical Address      Type
  192.168.8.1           94-83-c4-47-d5-c6     dynamic
  192.168.8.255         ff-ff-ff-ff-ff-ff     static
  224.0.0.22            01-00-5e-00-00-16     static
  224.0.0.251           01-00-5e-00-00-fb     static
  224.0.0.252           01-00-5e-00-00-fc     static
  239.255.255.250       01-00-5e-7f-ff-fa     static
  255.255.255.255       ff-ff-ff-ff-ff-ff     static

This is how it's connected:
home router (192.168.1.1) <-- eth cable --> (192.168.1.xxx) Mudi (192.168.8.1) <-- WiFi --> laptop (192.168.8.xxx)

So I can connect to WiFi network produced by Mudi, I get IP assigned by it's DHCP, I can reach e.g. my home router or the Internet, I just cannot reach Mudi gateway itself nor any other device also connected to Mudi.

6

Ok so I figured it out. It seems like it was the same problem as in here: https://www.reddit.com/r/GlInet/s/0H5mAfGUen

It also seems like there is a bug in the firmware. I too was setting up VPN yesterday (Wireguard/Mullvad) but I then removed it. I guess there was a conflict between subnets, which was weirding out the Windows?

However I didn't create a static route, I just factory reset the Mudi and now it works perfect even on Windows...

2 Likes