I've got 3 - E410 APs mounted and configured on my network both with a Secure and Guest WLAN. I created a DHCP pool that works great and clients are able to connect however, there are a few clients (at the moment some tablets and mobile phones) that get assigned a 0.0.0.0 address thus not able to get to the internet. It makes no difference whether the client is connected to the secure network or guest network they still get a 0.0.0.0 address. I've tried forgetting the network on the phone and reconnecting and no dice.Â
DHCP Pool range is 192.168.16.13 - 99 so its not that its exhausting IPs.Â
If someone can point me in the right direction that would be great. I've seen other threads about possibly the device not obtaining the default gateway information but see as 25 other devices connect with no issues I don't know how that would be the case.
does the issue happens only to Apple devices or issue is also seen with other devices like Android / Windows devices. If not tried to make this observation can we try it.
We created a VLAN on the firewall and have that VLAN tagged for Guest WiFi. We are able to have users log in. Its a very strange setup to say the least, as the client has Ubiquiti equipment to other buildings that go off the Guest network for the residents to have WiFi access. All in all, we couldn't identify if the ACLs were truly working or not as the environment wasn't healthy enough to make that assumption. But things are good to go now.
I've had other cambium guest WLANs with ACL control that has worked in the past but this one just went haywire. I appreciate everyone who helped.Â
Maybe a future feature for guest access to be a toggled bridged mode that other carriers have, sometimes selling the Cambium product it can be a little intimidating to the customer so they default to something else. OpenMesh has this for Guest Access that is very easy and quick to set up, however, OpenMesh doesn't have the hardware or software features that we like/require for our clients. Just a thought, I know I'm not alone in thinking this.
I marked it as resolved because the Cambiums looked to be functioning properly it was the network infrastructure that was the issue and was resolved. I had some great help from Ashok for tech items on this.
The 0.0.0.0 was strange as it took clients a bit to get an IP hence why they showed having a 0.0.0.0 but then around 4-5 minutes later they got an IP.
However, this thread was created 2 years ago, and whatever the problem was that the original person who started the thread had, it sounds like it might have had a completely different & unrelated root cause, at least vs. what I’m experiencing.
But the uptick in recent responses to this thread with people experiencing “I can’t get an IP” makes me wonder if those in fact might be running into the same (alleged) bug that I am.
@Benjamin_Cordoba and @Adam_Jones1 if you reboot your Pilot when you see this happening, does the problem resolve itself for a little while?
We are also having the same problem, which does not appear to be exclusive to an iPhone or other Apple product but rather to a wide range of devices. Rebooting the ap, though, does temporarily fix the problem.
As 2.4 has not yet displayed 0.0.0.0, it does appear to be concentrated around the 5 GHz channel.
@Network_Support_Spec Thanks for adding to the sample size here. This sounds very very similar to what we are experiencing, & correct it’s not limited to any particular make/model of device or software platform. And though I can’t yet say for certain that it never happens on 2.4GHz, every time I have observed it so far, it has been on 5GHz. So that’s fascinating.
Hopping to the same SSID on the opposite band, or hopping onto a different SSID on the same band, will work. I have only ever observed it affecting one SSID on one band at any given time. And in an installation with multiple Pilots, it only tends to affect one particular Pilot at any given time (can connect to same SSID on the same band on a different Pilot & that works).
@Network_Support_Spec@Adam_Jones1
I have received techsupport files will go through the logs and get back to you.
and can you please confirm how frequent you are observing this issue ?
