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

    No internet on the LAN

    Scheduled Pinned Locked Moved General pfSense Questions
    11 Posts 3 Posters 2.0k 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.
    • H
      heper
      last edited by

      can you get to the webgui from behind the switch?
      are you sure that none of the AP's have taken control of 192.168.1.1 ?

      can you ping 8.8.8.8 ? if yes ==> dns issue

      1 Reply Last reply Reply Quote 0
      • G
        gvintila
        last edited by

        Hello,

        Yes, I can access the web gui, as I said I can ping the LAN IP from the access points or any device connected to the switch. And no, the AP's don't have DHCP, I am getting an IP from the DHCP on the pfsense machine, 192.168.1.x. Also yes, I can ping either the name or the IP of any external host.

        1 Reply Last reply Reply Quote 0
        • H
          heper
          last edited by

          Also yes, I can ping either the name or the IP of any external host.

          from the clients? then what is the problem?

          1 Reply Last reply Reply Quote 0
          • G
            gvintila
            last edited by

            Sorry if I misunderstood, I can ping either name or IP on external from the PFSENSE machine, not from the clients. From the clients I can only ping the LAN interface (192.168.1.1).

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

              What are your firewall rules on LAN?

              Are the clients receiving pfSense as their default gateway?

              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
              • G
                gvintila
                last edited by

                Hello and thank you,

                Yes, please see attached screenshots for the firewall rules and the ipconfig output.

                fwrules.jpg
                fwrules.jpg_thumb
                dhcp.jpg
                dhcp.jpg_thumb

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

                  What are your outbound NAT rules?

                  It should be working. Have to figure out what's hosed somewhere.

                  If it's a simple setup it might be easier just to reset to factory and reconfigure.

                  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
                  • G
                    gvintila
                    last edited by

                    These are the outbound rules. I ran the setup again half an hour ago, it's not working. I did not reset to factory defaults as I am not in that location and don't have anyone to create a basic setup.
                    In your expert opinion , it should work with the existing setup? Could it be a restriction on any of the core switches or vlans? I have no access to those in the network.

                    fw2.jpg
                    fw2.jpg_thumb

                    1 Reply Last reply Reply Quote 0
                    • G
                      gvintila
                      last edited by

                      Also an extra element (if it matters), I can't ping anything on the other VLANs from the client connected on the LAN, it's as if everything is blocked on the Pfsense interface 192.168.1.x.

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

                        Looks like it should be working.  Put something else on the WAN side instead of whatever network you're plugging into and see if it works. Or start doing packet captures. Or reset and start over like I suggested before.

                        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
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.