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

    Simple Routing - Just can't get it right!

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 1.6k 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.
    • J
      jtcentral
      last edited by

      I have been beating this thing up with no luck.  Please help!

      I need pfsense to do a simple routing for me…I've got a /22 of public IP's and my Upstream provider has them routed to an IP on a different subnet.  I need to simply route between them...I don't need firewalling...but might use it in the future if I could get this darn thing to work!

      Upstream:
      100.100.100.1 Gateway
      100.100.100.2 IP where my public IP's are routed too.

      WAN
          pfsense
      LAN

      My Computers on my /22:
      200.200.200.0 /22

      I can ping the gateway and a public IP from the WAN, I can ping my computers through the LAN interface...so they are setup right...I just can't get them to route so I can see the internet from my computers.

      Any help would be GREATLY appreciated!!!

      Thanks,
      JT

      1 Reply Last reply Reply Quote 0
      • B
        blak111
        last edited by

        NAT > Outbound
            Check manual outbound > Click save
            Delete the rule > Click Save

        Verify the clients are using the pfSense LAN 200.200.200.x interface as their gateway.
        Create an allow rule on the WAN interface to allow unestablished traffic into the network for hosting.

        Verify route is being sent to you by sourcing a ping from your inside pfSense address.
          Get to a shell on the pfSense machine (ssh or console option 8).
          Issue ping command with -S source option. ( ping -S 200.200.200.x 100.100.100.1 )
          Success will verify that traffic directed to 200.200.200.x is being sent back to your firewall.

        1 Reply Last reply Reply Quote 0
        • J
          jtcentral
          last edited by

          Worked like a charm!!  Thanks so much!

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