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

    Passthrough public IP traffic

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 1.8k 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.
    • M Offline
      mmulqu
      last edited by

      Good morning,

      I'm trying to put two PFSense devices (primary and failover) at the head of my existing network.  Currently, my setup is as follows:

      Cable internet&2 bonded T1s (these have a block of public IPs, xxx.xxx.xxx.161 - xxx.xxx.xxx.190) -> Fatpipe WARP 3.0 (Primary and Failover) -> Sonicwall Pro 4060 (Primary and Failover) -> LAN

      Public IP addresses are assigned as follows:

      Cisco IAD = xxx.xxx.xxx.161
      Fatpipe WAN 1 = xxx.xxx.xxx.162
      Fatpipe LAN = 172.16.1.25 with a public IP of xxx.xxx.xxx.164 as an alias
      Sonicwall WAN = xxx.xxx.xxx.180 and this device handles the NATing of public to private IPs for servers on the LAN
      Sonicwall LAN = 172.16.1.75

      I'm planning to use the PFSense device to replace the Fatpipe and have it almost working except that I don't know how to pass incoming traffic destined for the public IPs to the Sonicwall.  How can I accomplish this?  Also, I had trouble figuring out how to mimic the alias setting that I found in the Fatpipe device and we were offline when I had the LAN port's IP in PFSense set to 172.16.1.25.  I just set it to xxx.xxx.xxx.164 to get our internet connections working.  Could this be an issue?

      Thanks much,

      Matt

      1 Reply Last reply Reply Quote 0
      • M Offline
        mmulqu
        last edited by

        Bump.  Anyone?  I'm going out to pickup a hub today.  I'm going to try to figure out which is the last device to pass the packets by running a packet capture through the hub at different points in the network.  Also, this network is a bit new to me and I've realized that I left one switch out of the equation.  There is a switch between the Fatpipes and the Sonicwalls.

        Cable internet&2 bonded T1s (these have a block of public IPs, xxx.xxx.xxx.161 - xxx.xxx.xxx.190) -> Fatpipe WARP 3.0 (Primary and Failover) -> Cisco 2950 Switch -> Sonicwall Pro 4060 (Primary and Failover) -> LAN

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