Cannot connect to the Guest Network Wifi, Will not Connect to the Guest Network Wifi

[jksmurf]

This is not a request for help, just some feedback related to GNP and an issue I had trying to connect to the Guest Wifi.

Thought I would just put out a wee heads up if anyone has a problem not being able to connect to the Guest Network, when using Guest Network Pro and the dnsmasq-x.conf.add approach to manually assigning IPs; here is my breakdown and implementation of that, as an aside. I used dnsmasq-1.conf.add, dnsmasq-2.conf.add etc.

I spent a good part of the afternoon scratching my head as to why I could not connect.

The reason was that I had 1 (one) leftover manually assigned IP which I did in the GNP Gui (GNP, Advanced Settings, Manually Assigned IP around the DHCP List) earlier, before I started using dnsmasq-x.conf.add referred to above.

However I forgot about the addition of a Manual IP assignment done via the GUI and went ahead and added a manual assignment to dnsmasq-1.conf.add (being the first VLAN, VLAN52). I cannot recall if it was the same MAC or IP or not.

Anyway the upshot was it caused me not to be able to connect to the Guest Wifi - it just kept twirling the connecting icon thing forever .. note: this issue is not about Internet Access nor Intranet Access nor AP isolation.

I did see when I looked on (i) info on Wifi in the iPhone (even when it was not showing connected) that it had connected (how?) to some crazy IPv4 address 254.169.xx.xx or something I had never heard of.

Anyway, the lesson is to not put assignments in both!

HTH someone one day.

 

[dave14305]

If you still have the syslogs from that time, there should be a “duplicate dhcp-host IP address 192.168.52.10” in the logs to show that the SDN dnsmasq instance failed to start up. Therefore, DHCP wouldn’t work, and you’d end up with an APIPA address 169.254.x.x.

 

[jksmurf]

If you still have the syslogs from that time, there should be a “duplicate dhcp-host IP address 192.168.52.10” in the logs to show that the SDN dnsmasq instance failed to start up. Therefore, DHCP wouldn’t work, and you’d end up with an APIPA address 169.254.x.x.

How do you even know this … I completely forgot to check the logs but even if I had I’d have no idea what I was looking for.

My troubleshooting seems to involve 1000 hrs of trial and error and you clocked it in about 2 seconds flat. So annoying. I’m going to have to put freddyjuarez on to you just to keep you occupied.

 

[dave14305]

How do you even know this

The benefits of being a loser spending all day reading home networking forums.

So annoying.

Another benefit.