Navigation

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

    Dual WAN with DUAL LAN (no failover)

    Routing and Multi WAN
    2
    3
    864
    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.
    • E
      elias28 last edited by

      Hi there,

      I have setup the firewall with two independent WAN and two independent LAN interfaces.
      Goal is to NAT traffic from LAN01 via WAN01 and LAN02 via WAN02.
      Therefore I have created the following AON NAT rules:

      LAN01 = 192.168.8.0/24 with GW 192.168.8.1 (firewall)
      LAN02 = 192.168.81.0/24 with GW 192.168.81.1 (firewall)

      The Gateways are as well created, with no default gateway set and are also reachable:

      When I connect now on LAN01, I am going via the correct LAN01 route and gateway to the internet.
      When I do the same on LAN02, DNS is resolving, but there is no connection to the www. Looks to me like a missing route.

      Finally I figured out, that when I select WAN02 as the default Gateway under System/Routing/Gateways, then I can also reach the internet via LAN02,
      but then LAN01 is of course off.
      So how can I fix this issue, as there is only one Default Gateway available - either for LAN01 or LAN02.
      Looks like the gateway rules are not working properly.

      I do not want any failover or load balancing between the WAN's,. Both networks must remain independent from each other, even if one WAN fails.
      For this scenario I know, there are a lot of topics.

      Many thanks in advance!

      1 Reply Last reply Reply Quote 0
      • E
        elias28 last edited by

        I figured it out finally by myself.

        There is an option called "Policy Based Routing" under Firewall/Rules/LAN
        You need to force the LAN net to use a dedicated GW, which is configured under System/Routing/Gateways.

        Like this you can get around the default GW problem (pfsense will always choose one and add it to its routing table regardless if you chose one or not)
        The one which is chosen by the system (normally the top one in the list) is then also used by the NAT rules.
        A little confusing, because you expect the NAT rules to do this for you.

        Anyway, thanks for reading  8)

        1 Reply Last reply Reply Quote 0
        • M
          Markee last edited by

          Can u post screenshots on your configuration?

          I want to do the same but something is not working.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          Products

          • Platform Overview
          • TNSR
          • pfSense Plus
          • Appliances

          Services

          • Training
          • Professional Services

          Support

          • Subscription Plans
          • Contact Support
          • Product Lifecycle
          • Documentation

          News

          • Media Coverage
          • Press
          • Events

          Resources

          • Blog
          • FAQ
          • Find a Partner
          • Resource Library
          • Security Information

          Company

          • About Us
          • Careers
          • Partners
          • Contact Us
          • Legal
          Our Mission

          We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

          Subscribe to our Newsletter

          Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

          © 2021 Rubicon Communications, LLC | Privacy Policy