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

    Multi WAN routing not working, one PPPoE one DHCP behind ISP NAT router

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

      Hi all,

      I'm struggling to get load balancing working across two WAN interfaces.

      The first interface is PPPoE. The second is using a cable router which I've been unable to get to work in modem mode (I might post about that separately!), so is therefore acting as a NAT router with IP 192.168.0.1, giving PFSense an IP of 192.168.0.14.

      I've set monitor IPs on the first interface as 8.8.8.8 and on the second 1.1.1.1. Both show as online:

      bc60068c-d2e1-4df9-bcee-3eec78be4f0a-image.png

      I've also configured gateway groups as shown:

      d9ae17d6-33cf-4a50-939f-99833db76a54-image.png

      I've tried trigger level on both member down and packet loss or high latency.

      In firewall rules, I set the gateway accordingly:

      bf2d32bb-2637-4465-87b5-6ac687016b98-image.png

      No matter what I try, traffic always goes out via the first WAN interface. Interestingly changing the gateway in the firewall rule to the second WAN interface also sees traffic continue to go out via the first:

      f1521caa-50a5-4d33-a512-89ff2a39b559-image.png

      I've tried both with and without sticky connections.

      If I yank the cable out of the first WAN connection, it fails over just fine and starts to use WAN2, but that's the only scenario where it does.

      Tracert 1.1.1.1 goes out via WAN2, anything else via WAN1.

      Anything I've missed?

      Thanks,
      Paul

      I 1 Reply Last reply Reply Quote 0
      • I
        identitypaul @identitypaul
        last edited by

        @identitypaul Answering my own question, after many days of battling with this...

        Resetting the state table fixed it instantly.

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