OpenVPN bug(?) if there is more than one VPN-Server

  • I have three OpenVPN-Server in use. Of course this is for very different clients and there are totally differnet access-rules.
    The OpenVPN-Interface are

    VPN1 (This is for Laptops/Smartphones) -> via 10.10.90.x/30 -> Single IP per VPN-Client / no NAT
    VPN2 (This is Site2Site) -> NET
    VPN3 (several external stuff) -> via 10.10.92.x/30 -> Adresse 192.160.x.0/24 (every client with separate NAT-NET. / "x" = 1-20)

    If I configure Outbound-NAT for VPN3
    OpenVPN  any * * interfaceAdresse
    than pfSense actually uses RoundRobin for this rule.

    The first packet is NATed to
    The second to
    The third to (this is the right one)
    The fourth to again.

    This way only one out of three packets finds the right path.
    As the NET is ONLY routed behind VPN3 the pfSense should know that it is not valid to NAT it to another Interface that

    I have to use that rule instead:
    OpenVPN  any * * (or use an Alias for that)

    Is that "normal" or a bug?

  • That's the expected behavior. OpenVPN is a group, using its "interface address" will be a round-robin through that group. Assign the individual ovpnsX interfaces if you want to do that without round robin and specifying "interface address".

  • Thanks for the answer.
    I found several users with the very same problem of understanding. As everywhere the IF-adresses (WAN/LAN/…) automatically are available in drop-down-menues. There is no hint, that in this case "Interface Adress" is a group.  It would be great if this is more clear that "InterfaceAdress" is ment as a group of all VPN-interfaces here.

    Also I don't understand in what case this behavior may be intended by user. Only with exact one VPN the result is what someone needs.

    And at last, why is there no dropdown-entry for each of the several Interfaces of a multi-VPN-setup?


  • It's not "interface address" that's a group, "OpenVPN" is a group. That's widely documented. The individual connections show up if you assign their interfaces.

  • Probably you're right with "That's widely documented", as you are in that theme and an admin here.
    I did'nt find anything about that anyway. Maybe you can point me to a good place to start reading about?

    Even if pfSense is not for beginners, there are lot's of things where I feel the documentation is not comprehensive enough.
    To have that "InterfaceAdress" at that dropdown at least is missleading.

    As I can't imagine where someone can use that intentional than.
    If I have one VPN it will do, but adding a second VPN will break the outbound-NAT for the first one. So it should recommended that you better not use "InterfaceAdress" there, because this can cause Problems later, when you allready forgot the Outbound-NAT-Rules depending to the first VPN are affected than.

Log in to reply