Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    After an update runs openvpn only on the main ip not on vrtual ip addresses

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 2 Posters 1.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      ahuser
      last edited by

      i have make an update from pfsense 2.1 beta.x  to the newest.

      I have an public ip range
      x.x.x.34 to x.x.x.44

      the ip x.x.x.34 is the main ip-address of the wan inferface. The rest is configured as virtual ip-addresses.

      i use the x.x.x.35 virtual ip for openvpn. Ago the update works all fine.
      After the update clients can not connect to the openvpn server which have a virtual (alias) ip-address.

      i have change the interface in openvpn server to "WAN" interface.
      same result no connection possible .

      tcpdump shows a attempting incomming connection from the client
      but no response vom openvpn server.

      only when ich change the openvpn server to the WAN IP-Address x.x.x.34 and to  second the client config "server host address" also to den WAN IP-Address x.x.x.35 then the connection is possible and work.

      for testing the firewall rules are at first position all open (any to any)

      anybody have an idea?

      many thanks!

      1 Reply Last reply Reply Quote 0
      • P
        pkwong
        last edited by

        Create an interface and route it out that interface.  Or you can modify the routing tables manually (not suggested).

        When all else fails, don't blame the machine.  Blame your architecture.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.