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

    Automatic Mirror Nat/Rules across multiple WANs

    Scheduled Pinned Locked Moved NAT
    3 Posts 2 Posters 1.8k 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
      AkkerKid
      last edited by

      I'd like to be have most/all of the rules I create for one WAN connection to sync to my other WAN connection. Or just set each rule during creation to apply to both WANs instead of just one.  Is this possible?

      Example: Two internet connections (1 cable and 1 DSL)  In oder to connect to the computers/servers inside the router from the internet I must create identical NAT port forwarding rules for each connection so that in case one connection goes down, I can still access everything through the other.  Also Failover and DDNS is set up so that if either go down, my DDNS provider will be updated to use the working connection. Is there an easier way to sync the rules between WANs?
      Thanks all!

      1 Reply Last reply Reply Quote 0
      • A
        AkkerKid
        last edited by

        Anyone?

        1 Reply Last reply Reply Quote 0
        • GruensFroeschliG
          GruensFroeschli
          last edited by

          Use aliases.
          Create an alias containing all the ports you want to forward.

          Then create an NAT rule with as inbound/destination port this alias.
          Create a rule for each WAN.
          The autocreated rule for the WAN uses this alias as well.

          Now if you ever want to change anything, you just have to change the alias.

          The DNS failoverpart is not possible with the pfSense itself.
          However what you can do:
          Install the client to update the dynDNS entry on the server itself.
          Let the server check every minute or something if it's IP changed.
          Have the outbound traffic of the server in a separate failover-pool.
          Now if the primary WAN fails, the server will notice within one minute that it's IP changed and update that with dynDNS.

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

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