Actions
Bug #1637
closedcaptive portal web service port bind validation issue
Status:
Needs Patch
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/02/2011
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:
Description
captive portal uses port 8000 for the web interface but fails to report to the user if the port is already in useby another service on the pfsense box
example
if the ssh port is set to port 8000
ssh works correctly and on port 8000 via http a ssh protocol mismatch is reported which is correct behaviour
but if a user tries to enable the captive portal it should fail when pressing the save button and should report that the portal was not enabled/will not work due to another service using the captive portal web service port it should save all settings for the portal apart from the enable option
Actions