pfSense

Overview
Activity
Roadmap
Issues

Custom queries

2.8.1 - Resolved/Closed
2.9.0 - Resolved/Closed
26.03 Plus - All Closed Issues
26.03 Target - All Closed Issues
26.03.1 Plus - All Closed Issues
26.03.1 Target - All Closed Issues
26.07 Plus - All Closed Issues
26.07 Target - All Closed Issues
26.10 Plus - All Closed Issues
26.10 Plus - All Open Issues
26.10 Plus - Feedback Issues
26.10 Plus - Needs Attention/Work
26.10 Plus - New/Confirmed/In Progress Issues
26.10 Plus - Pull Request Review
26.10 Plus - Waiting on Merge
26.10 Target - All Closed Issues
26.10 Target - All Open Issues
All Open Issues assigned to Me
All Open Pull Requests
Any Target - All Open Regressions
Any Target - Feedback Issues
CE-Next - All Closed Issues (Move to specific target)
CE-Next - All Open Issues
CE-Next - Feedback (Likely needs target changed)
New Issues by Category - Future Target
New Issues by Category - No Target
New Issues by Category - No Target+Future
No Target - All Open Issues (Base Only)
No Target - New Issues (Base Only)
No Target - New Issues (Base and Packages)
Plus-next Feedback/Closed (likely needs target changed)
Release Notes - CE Target Version (DO NOT EDIT)
Release Notes - Plus Target Version (DO NOT EDIT)
Release Notes - Target Version (DO NOT EDIT)

Actions

Copy link

Bug #5786

open

Check WebConfigurator port for conflicts

Bug #5786: Check WebConfigurator port for conflicts

Added by Renato Botelho over 10 years ago. Updated over 4 years ago.

Status:

New

Priority:

Normal

Assignee:

Category:

Web Interface

Target version:

Future

Start date:

01/20/2016

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

All

Affected Architecture:

Description

There is no check today to make sure WebConfigurator TCP port is being used by OpenVPN and it can end up losing web access to the box

History
Notes
Property changes

CB Updated by Chris Buechler over 10 years ago Actions
Copy link
#1

there are a lot of other possibilities for port conflicts too. HTTPS on port 80 with HTTP->HTTPS redirect enabled (though that's a pretty crazy dumb one). 80xx ports for captive portal. DNS Forwarder/Resolver. Proxy mode NAT reflection. Lot of possibilities with packages though that's a tough one to build in checks to the base system, the packages themselves should check that.