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

    MultiWAN failover - config is not saved properly??

    Scheduled Pinned Locked Moved Routing and Multi WAN
    5 Posts 2 Posters 1.9k 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.
    • F
      fribert
      last edited by

      Hmm, I read the MultiWANVersion1.2 guide (http://doc.pfsense.org/index.php/MultiWanVersion1.2) and tried to set up our pfsense test server here the same way.

      I'm a bit unsure of the requirements of the setup.
      I have a primary fiber connection, and a secondary shdsl. I would prefer to have only a failover setup, not a loadbalanced.

      From the primary line we have a lot of PAT/NAT's to services on the inside.

      So, do I need to setup a DMZ the way it's explained in the doc above, or can I do the PAT/NAT's directly on the failover pfSense?

      Furthermore, I tried setting up pools, and have them check on 'other' IP's than DNS's, but if I opened the pool again, no IP was shown in the 'other' field, it was just blank.
      If I chose to test the DNS, it seemed to be doing it right, but again, on reopening the pool, it showed 'other' with an empty field.

      Nothing else, except upnp has been activated on the pfSense.

      internet_failover.gif
      internet_failover.gif_thumb

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

        Hmm, I read the MultiWANVersion1.2 guide (http://doc.pfsense.org/index.php/MultiWanVersion1.2) and tried to set up our pfsense test server here the same way.

        I'm a bit unsure of the requirements of the setup.
        I have a primary fiber connection, and a secondary shdsl. I would prefer to have only a failover setup, not a loadbalanced.

        I understand the doc as it's the dsl modem / routers DMZ and not a DMZ interface on pfSense itself.
        So yes to port forward and failover

        Furthermore, I tried setting up pools, and have them check on 'other' IP's than DNS's, but if I opened the pool again, no IP was shown in the 'other' field, it was just blank.
        If I chose to test the DNS, it seemed to be doing it right, but again, on reopening the pool, it showed 'other' with an empty field.

        As it should be… look at List as that is where you should see the ip's in your failover pool.

        /Perry
        doc.pfsense.org

        1 Reply Last reply Reply Quote 0
        • F
          fribert
          last edited by

          Hmmm, I'm getting confused here :-)

          I was thinking that I could skip most of the config, and just have one pool that said WAN1FailsToWAN2, and use the rule from that one.
          As I understand the pool, it will take the interfaces in prioritized order?

          So I then created one pool as below (as gateway)

          Then I created three rules

          But if I then go a ask for status on the pool, it says offline to both of them???

          Btw. the IP is ntp2.tele.dk, which does reply to ping.

          pool.jpg
          pool.jpg_thumb
          rules.jpg
          rules.jpg_thumb
          status.jpg
          status.jpg_thumb

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

            You can not have the same monitor ip for both gateways
            Delete your first lan rule

            /Perry
            doc.pfsense.org

            1 Reply Last reply Reply Quote 0
            • F
              fribert
              last edited by

              Hi Perry

              Wow, fast answer  :D

              Ok, so you say I've made two errors. First of, correct the monitor IP, ok did that (and it helped).

              Secondly, you say I should delete the WAN2 subnet firewall rule???

              Oh, and the interface for setting up pools is NOT logical, I didn't see the connection between adding the port, and selecting a monitor IP until you mentioned my error.

              As the Secondary line is down at the moment (no cable in it ;) ), I'm going to test that the primary cable works.

              Thankyou for your insights.

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