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

    5 Wan links, Only 3 working (Policy Based)

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 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.
    • A
      Alchamy
      last edited by

      I am really hopeful that somebody can assist me with a small problem I have encountered.

      I have been using pfSense since 0.6* or somewhere around there. I have always had 3 wan links and used policy based routing. No failover or load balancing.

      I simply create firewall rules in the Lan section and point to the gateway I wish to use.

      Recently I have added 2 links; however if I select the new gateways no traffic moves across them and I cannot find any errors in the logs.

      My setup looks like this

      rl0:192.168.0.125/16 (LAN)
      ste0: 209.212.119./29 (WAN - Cable Link)
      ste1: 196.211.142.
      /29 (OPT1 - DSL Link)
      ste2: 209.212.121./29 (OPT2 - Cable Link)
      ste3: 196.211.127.
      /29 (OPT4 - DSL Link)
      ste4: 172.16.5.**/24 (OPT5 - 3G Link)

      Each ste* interface is a seperate physical link (just incase the ip ranges make you think they are the same links)

      What I normally do is create rules like  "TCP  192.168.0.3  443 (HTTPS)  169.202.9.74  443 (HTTPS)  209.212.121.** Banking"

      This works perfectly for me unless I select the gateways for the 2 new links. Then it is dead. Nothing in the firewall logs, no traffic. Just dead. The links are working 100% I can see the gateways from the firewall and I can ping the gateways from outside.

      I am currently using 1.2-BETA-1-PRERELEASE-SNAPSHOT-04-23-07

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

        Okay, Well….

        I figured it out. I just had to add an outbound NAT rule and it is working 100%

        Not sure if its working as intended but my problem is solved so I am happy.

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