Actions
Feature #814
closedGUI should allow to bind openvpn on different ip same port
Start date:
08/09/2010
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Actions
Added by Ermal Luçi about 14 years ago. Updated over 11 years ago.
100%
This is because the management interface relies on the same port as the server is listening on, which changing would have a number of complications. If someone wants to knock this out for 2.0 that's fine but it's not a critical issue for release given the complications it introduces.
This can be done now because Ermal converted the management interface over to UNIX sockets, so the port from the GUI should no longer matter to the management interface.
We just need to make sure the input validation is smart enough to reject only if there isn't an interface-specific conflict (or if one has chosen 'any' interface on a certain port)
The wizard also needs adjusted to accept this scenario (Reported in #1002, but that was closed in favor of using this ticket).
Hello, already is possible run 2 openvpn instances in same port using diferent Wan Interfaces?
This should be possible now but there is a new issue holding it back. Now that we can assign a gateway group as the "interface" for an OpenVPN instance, the IP would not only have to be checked against the other IPs used directly, but also against any potential IP/interface inside a gateway group.
Applied in changeset 49b76122af0846474f65eaf73e0e879e24fb554c.