Actions
Bug #12532
closed
Virtual IP problem with OpenVPN
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
Hi, I wasn't sure if this should be tracked separately, but I've seen similar behavior to this issue: https://redmine.pfsense.org/issues/11545 (which includes IPSec language).
With OpenVPN server, if I have the Interface set to "WAN" it actually binds to my VIP.
In Status > Interfaces, WAN also shows my VIP.
If I go to Interfaces > WAN, I see the proper static IP address I set, not the VIP.
I saw an earlier report about order of IP's, but my WAN IP is first numerically (x.x.x.138 for WAN and x.x.x.139 for my VIP).
My workaround for OpenVPN is to have it bind to "all" interfaces, not WAN. Then clients can connect.
Related issues
Updated by Jim Pingle over 2 years ago
- Status changed from New to Duplicate
It's the same as the other issue, no need for a separate entry.
Updated by Jim Pingle over 2 years ago
- Is duplicate of Regression #11545: Primary interface address is not always used when VIPs are present added
Actions