Hi,
I have a couple of Max2Play devices on my network, both wirelessly linked to my 192.168.1.x network. Recently I have had some issues where a PC rebooted and could not get external access. Upon further investigation it appeared to have picked up a 192.168.189.x IP address.
It seems the Max2Play hosting my Logitech server was on the wireless at a 192.168.1.180 address, but was giving out DHCP addresses!
Is their any way to stop this, as I already have a DHCP server and really don’t want or need this extra service on my network. I have disabled the „access point on startup mode“ in both these units.
But even then should it not disable the services this creates once its correct wireless setup is active and it has become a client on another wireless network ?
I came to the forum this evening for a similar issue. I don’t know that the Max2Play pi is handing out ip addresses, but it suddenly has 2 – 192.168.0.12 (expected) and 192.168.189.1. I would like to understand this behaviour for sure.
We now added a fix in our most current beta. If you have an active DHCP server before the update, the beta update’s yellow text should include a notification „Disabled DHCP Server DNSMASQ“ in the details.