Bug #5786
open
Check WebConfigurator port for conflicts
Added by Renato Botelho almost 9 years ago.
Updated over 2 years ago.
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
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.
- 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
- Category set to Web Interface
- Assignee deleted (
Renato Botelho)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by