Project

General

Profile

Actions
Copy link

Bug #5786

open

Check WebConfigurator port for conflicts

Added by Renato Botelho over 9 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
Future
Start date:
01/20/2016
Due date:
% Done:

0%

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

Actions
Copy link
 #1

Updated by Chris Buechler over 9 years ago

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.

Actions
Copy link
 #2

Updated by Renato Botelho over 9 years ago

  • Target version changed from 2.3 to Future

Move it to future version then we have time to think about a way to check all possibilities

Actions
Copy link
 #3

Updated by Jim Pingle almost 6 years ago

  • Category set to Web Interface
Actions
Copy link
 #4

Updated by Renato Botelho about 3 years ago

  • Assignee deleted (Renato Botelho)
Actions
Copy link

Also available in: Atom PDF