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

    Dual wan with mobile ipsec fail

    Scheduled Pinned Locked Moved IPsec
    4 Posts 3 Posters 949 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.
    • K
      kapara
      last edited by

      I added a second WAN (ATT) and changed the default gateway to the new ISP (ATT) and modified the rule for ipsec to use the SONIC gateway.  Both wan connections are up and active.

      When the default is set to ATT mobile IPSEC fails.
      When the default is set to SONIC it has no issues.

      The mobile client is set to use the SONIC connection.
      IPSEC is set to use SONIC as gateway instead of default.
      No rules on LAN have been set to use anything other than default.

      Skype ID:  Marinhd

      1 Reply Last reply Reply Quote 0
      • K
        kapara
        last edited by

        Really????

        Skype ID:  Marinhd

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

          At the risk of necro'ing this, I wanted to mention I'm having the same issue on 2.2.2 with dual-WAN, cable and DSL.

          If I manually add the temporary IP I have from my 4G provider to pfSense to a route pointing to the non-default gateway, I can connect the client successfully. Without that route, the client gets no response from the server.

          It looks like requests are coming in on the secondary WAN connection, then attempting to return via the primary WAN connection that I have set up as default on pfSense.

          I don't know where to set up the routing to tell pfSense that I want to route all mobile IPSec traffic regardless of origin back out through the secondary WAN connection. The initial connection can't be made, so I don't think any routing behind that is worth fiddling with yet.

          Any ideas?

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            Mobile IPsec rules don't get added with reply-to, so it only works by default on the WAN where your default route resides. If you manually add UDP ports 500 and 4500 rule(s) on the other WAN, it'll add the reply-to, which will do the return routing correctly.

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