I’m getting ready to open a ticket (have to wait for problem to reoccur, then collect techsupport, etc.), but while I work on this, want to know if anyone else is experiencing a problem similar to this & whether it might be a well-known issue with known workarounds…
Has anybody ever run into an issue with e-series cnPilots (in this case, e410, but I’m guessing it’s not limited to these) where, seemingly at random, a single SSID on a single radio (so, essentially, a particular VAP) will simply stop forwarding broadcast traffic (which in turn completely breaks essential things like DHCP & ARP)?
When it happens, other SSIDs on the same radio are unaffected (can ask the same computer to connect to different SSID that’s on the same VLAN, and it works perfectly), as is that same SSID on the other radio if that SSID is configured to exist on both bands (so if it happens on 2.4GHz, 5GHz will be okay, or vice-versa). Rebooting the Pilot will correct the problem…for a while (few hours, few days, etc.).
Particular customer of ours (coffee shop) started experiencing this problem a couple of weeks ago, and it’s driving both me and them mad. They’re also a particularly loud customer, so it’s been extremely frustrating. I’m this close to ripping the Pilots out and replacing with something non-Cambium at this point, frankly.
The fact that it’s happening in a well-trafficked location like a coffee shop makes me think that the trigger to the bug might have something to do with either the number of absolute associations/disassociations, or the frequency of assoc/disassoc (which would also explain why it’s only affecting the SSID that their customers / the public use). But it’s odd that they haven’t had problems up until very recently, which makes me wonder if something in “the environment” changed, like perhaps there’s some badly-behaving WiFi client that’s doing something non-kosher that the Pilot is responding poorly to.
Enabling Unicast DHCP option on the SSID does not work around the problem, and clients still cannot receive a DHCP lease while Pilot is in this funky state even with that option enabled. I have updated them to 18.104.22.168 with no change, but am hesitant to go beyond that to 6.x given some of the other known issues surrounding that branch that are being discussed in other threads.