Actions
Bug #12355
closedCaptive Portal database and ``ipfw`` rules are out of sync after unclean shutdown
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
22.01
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
If a Captive Portal zone does not have the "Preserve connected users across reboot" option set and the firewall encounters an unclean shutdown, users are listed in the captive portal database and status as being online but their entries are not present in the correct IPFW tables. This can happen, for example, due to sudden power loss, crash/panic, or CLI reboot
not using the expected scripts.
Currently at startup the Captive Portal code only checks if the preserve option is set and restores the IPFW entries if so. That check should have an else
clause which resets the database if the user chose not to preserve the data.
Actions