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

    [resolved] Multi-WAN: best way to…

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

      Hello all,

      I've been going over some of the docs looking for examples and best practices, but I don't think my situation falls under what most are trying to do with Multi-WAN. Some backgound on the situation:

      -Currently have an ISP set up as primary WAN. The connection has 5 IPs. 3 of these IPs are configured in a 1:1 NAT to internal servers, another is NAT'ed based on firewall rules for services to another internal server.
      -I would like to add a redunandant inbound connection for one of these servers only, as this additional WAN link only has 1 IP address. I have configured this as WAN2. In my pfSense dashboard, it shows the IP as online, gateway good to go, etc.
      -After adding the exact same NAT and firewall rules for the internal server that I have for the original WAN connection, I can't access any services externally (all are "connection refused" as if nothing allowed through WAN2 regardless of my config).
      -After enabling ICMP on the WAN2 IP, I can ping it externally.

      From the reading I've done, I don't think I should set up a typical multi-wan setup here, as I don't want any load balancing and I won't have equivalent IPs and services to associate if I were to group the two WAN connections as the documentation suggests. Ideally, there would just be an additional inbound connection that would access the internal server via the same NAT and firewall rules for WAN2 as there are for the initial WAN.

      I feel like I'm missing something obvious here: any suggestions? I should also mention I'm running pfSense 2.1.5-RELEASE (amd64).

      Thanks,
      Greg

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

        Just wanted to update this thread, there was nothing wrong with my pfSense config, this was an ISP port blocking issue.

        Thanks to all that took the time to review the thread.

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