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

    Not able to route traffic through pfSense

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 5 Posters 1.1k 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.
    • X
      xk0nsid
      last edited by

      I'm having trouble routing from LAN interface to WAN interface. I have one WAN interface connected to a leased line with 5 public IPs available. I've chosen one IP for WAN interface of pfSense. I've also added LAN interface with IP 172.16.1.1/16 and a dhcp server. I've attached a brief map of the network.

      I've tried everything. I am able to ping my router gateway from LAN systems but not able to talk to WAN. I have default Firewall LAN rules. I've allowed a couple of IPs from WAN so as to provide access to our remote office.

      ![Screen Shot 2015-02-03 at 11.50.45 AM.png](/public/imported_attachments/1/Screen Shot 2015-02-03 at 11.50.45 AM.png)

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        No idea how you could make that not work.  Making it fail is harder than making it work.

        You'll need to post more specifics about your WAN and the rest of your config.

        Did you start with a clean install?  Follow along with the installer script?

        Can you ping the WAN default gateway from pfSense?

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • M
          muswellhillbilly
          last edited by

          Might be worth checking the masking you have on the WAN address. Is it correct? If so, you should be able to ping the default gateway (router) from the WAN side of the firewall. SSH onto the pfsense and see if that works. If you can get that far the next thing would be to see if you can ping any external address (eg:8.8.4.4). Assuming you can do that, then about the only thing left which might be causing an issue would probably be DNS. Assuming you've just set up the firewall in an 'out-of-the-box' fashion, then these are about the only things I can imagine which might be wrong.

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by

            did you set the pfsense lan interface gw to itself? 172.16.1.1??

            You would be amazed at how often this is seen - for the life of my I don't understand it.. But see it all the time..

            Also just for curiosity why would you use a /16???  Come on.. so you might need 65K IPs on the same segment??

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.7.2, 24.11

            1 Reply Last reply Reply Quote 0
            • W
              wifiuk
              last edited by

              what does your tracert / traceroute show ?

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