Captive Portal MACs not working as of 1/1/2017
-
To whomever is tracking this issue, we upgraded to 2.3.3-RELEASE (amd64) and we continue to operate without problems. Just because I was curious, however, I reinstalled the older 2.3.2 version on the backup router and restored the configuration that was attached in this forum and it does revert to ignoring the MAC bypass list, but then I upgrade it to 2.3.3 and once again the problem went away. So congratulations on the new version, and thank you very much for your excellent work.
-
This morning at 4:00am sharp the router rebooted for no apparent reason (no error in the logs) and it is back to ignoring the MAC address bypass list in the Captive Portal settings just like it did back on January 1 of this year (hence the bump of this topic, because all of the conditions are the same).
I've had to turn off Captive Portal to prevent denying access to the Internet for all of the workstations on the network. Current version 2.3.4-RELEASE-p1. Rebooting the router again didn't solve the problem. No configuration changes have been made this week. The router has been rebooted a number of times without this problem. Etc etc.
System configuration AMD FX-8370 Eight-Core 4.2 GHz with Intel Quad Gigabit Ethernet card, dual HGST hard drives, 8G RAM (barely used), etc etc about 300 workstations to dual upstream gigabit Ethernet WAN. All overkill.
I was already planning to upgrade to 2.4 this weekend, so we'll see if that fixes the problem.
-
Upgrading to 2.4.0.RC solved the problem. Captive portal now recognizing the MAC bypass list.