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

      Hello everyone,

      I know this has probably been asked before, I have made sure to check everything before posting here, but it's still not working. This setup was installed into another location, and it was working, now after only changing the IP of the WAN, it does not work anymore (now and before the IP of the WAN is/was private, before was 172.27.x.x and now the WAN is 10.140.x.x)

      I have the following setup:

      WAN interface with the private IP of 10.140.33.200, gateway 10.140.33.1, I can successfully ping the gateway and everything on the web (google, yahoo, etc)
      LAN interface with the private IP of 192.168.1.1, no gateway. If I run the Diagnostics/Ping with source address being LAN, I can also successfully ping anything external.

      I have a dumb switch connected to the LAN interface, and into that switch there are a few wireless access points. If I connect a client to the AP, I am getting an IP address from the 192.168.1.x range, I can successfully ping 192.168.1.1, but nothing else.

      If I connect a laptop directly to the switch, I am also getting an IP from the 192.168.1.x range, I can ping the gateway (192.168.1.1), but nothing beyond that.

      I have attached also screenshots with the System/Routing, Interfaces/LAN/WAN, Firewall/NAT/Outbound and routing tables, maybe I am missing something. Thank you in advance for your help.

      ping.jpg
      ping.jpg_thumb
      gw.jpg
      gw.jpg_thumb
      fw.jpg
      fw.jpg_thumb
      gw0.jpg
      gw0.jpg_thumb
      lan.jpg
      lan.jpg_thumb
      routing.jpg
      routing.jpg_thumb
      wan.jpg
      wan.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • 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.