Navigation

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

    LAN not getting routed through default GW

    Installation and Upgrades
    3
    6
    869
    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.
    • A
      Andyrue last edited by

      I've been racking my head against this all day and can't seem to get anywhere.  I think I've covered all the basics but haven't gotten anywhere.

      I can't seem to access the internet from the LAN.  Trying to ping an IP or a name both fail.
      My WAN has a static IP and according to the Routing table in pfSense, the default GW is the proper GW for my WAN IP.
      From the pfSense box I can access the internet fine, one curious thing though…from pfSense, if I try to ping 8.8.8.8 using the LAN interface I get nothing.  I test this with another pfSense box I have and I could do it so I think that's supposed to work.

      The gateway on my laptop is set to the pfSense IP, so I know it should be getting that far anyway but seems to stop there.

      Thanks for any insight into this, I know it's a somewhat common question and generally is a simple solution.

      1 Reply Last reply Reply Quote 0
      • A
        Andyrue last edited by

        Ok, I don't know what it is but it seemed to be a bug.  I ran the General Setup wizard again per somebody's suggestion, didn't change anything and now it's working.  Seems changing some things manually doesn't take full effect somewhere.  I did originally have a different LAN subnet set and changed it later manually.  All is well now.

        1 Reply Last reply Reply Quote 0
        • jimp
          jimp Rebel Alliance Developer Netgate last edited by

          Sounds like maybe you didn't have the gateway selected on Interfaces > WAN which made automatic outbound NAT fail (similarly, adding a gateway on the LAN interface will break it)

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          • D
            Durrrr last edited by

            This sounds like my issue. Are you saying that we can't use a gateway on LAN at all? What do you do when pfSense is sitting in between a router and the WAN? If I don't have a gateway set on LAN then pfSense can't find nodes on LAN subnets routed by our L3 switches. But if I set the gateway on LAN all routing breaks. So what can I do besides stick to 2.0.3? (on which it works)

            1 Reply Last reply Reply Quote 0
            • jimp
              jimp Rebel Alliance Developer Netgate last edited by

              You can define a gateway for LAN on System > Routing for static routes

              You should not select a gateway on Interfaces > LAN

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • D
                Durrrr last edited by

                o_O

                Is it really that simple? I'm going to try this tonight when I can create some downtime. Thanks!

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post