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

    Multi WAN/LAN - how to separate ISP connections?

    Routing and Multi WAN
    4
    6
    1.3k
    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
      apiskala
      last edited by

      Hi,

      I have problem with multiwan setup. My current config:

      ISP1 –-------------                    IF1 (ETHERNET)  --------------------LAN 1
                                    PFSENSE
      ISP2 ---------------                    IF2 (WIFI AP)  -----------------------LAN 2

      Clients on LAN1 can use both ISP with failover feature and this is working OK pfsense swith traffic if one of members is down (LAN1 use gateway group as default gateway). Clients on LAN2 are supposed to use only ISP2 so in advanced settings of default pass firewall rule for LAN2 I have set ISP2 gateway. Here everythig works great till ISP2 goes down. In this kond of situation pfsense swith LAN 2 to ISP2 ant this is not what  I expected  :( I tried to set up second gateway group with ISP2 -> Tier1 and ISP1 -> Never and assign it to LAN2 but this behaves the same way. My version of pfsense is 2.1.5

      1 Reply Last reply Reply Quote 0
      • ?
        Guest
        last edited by

        version of pfsense is 2.1.5

        Please upgrade to 2.2.1 please.

        I would decide to go by load balancing, and this is why.

        • The entire traffic will be using all two ISP lines
        • If on ISP is failing the entire traffic runs over the last ISP line
        • So both lines will be used and a fail over is also automatic on top

        By using the policy based routing method it should matching best at your situation.

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          I'm not clear on what you want to have happen when ISP2 goes down?  LAN 2 should just be down and not use ISP 1?

          If you want them both to use different circuits but both fail over, do this:

          Make a gateway group with ISP 1 as Tier 1 and ISP 2 as Tier 2.  Make another gateway group with ISP 1 as Tier 2 and ISP 2 as Tier 1.

          On your LAN 1 rules policy route out the first group.  On your LAN 2 rules, policy route out the second.

          If you want to have the LAN 2 traffic go nowhere, look in System > Advanced, Miscellaneous for the Skip rules when gateway is down option and check it.

          There are more elegant ways of dealing with this on a per-interface/rule basis but I think that checkbox will suffice in your situation.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

            @Derelict:

            I'm not clear on what you want to have happen when ISP2 goes down?  LAN 2 should just be down and not use ISP 1?

            Thats right. When ISP2 goes down LAN2 should not have access to internet. When "Skip rules when gateway is down" is enabled almost everything works ok. Internet is disabled but LAN2 can not access LAN1 (most likely  all interface  rules are skipped)

            1 Reply Last reply Reply Quote 0
            • P
              phil.davis
              last edited by

              "Skip rules when gateway is down" only skips any rule that specifies a gateway that is down. Other rules should be working fine. Post your rules and a description of what you want to happen and what does not happen.

              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                Yeah something's not adding up.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

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