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

    No internet on LAN

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    24 Posts 8 Posters 5.8k 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.
    • R
      Ramy
      last edited by

      @stephenw10:

      How does the ping fail? No route to host? No dns resolution? No reply?

      Do you have the gateway and dns servers set on the client?

      Steve

      I get "Destination Host Unreachable". The gateway and DNS servers are set on the client.
      Client settings are:
      IP: 192.168.1.2
      Netmask: 255.255.255.0
      Gateway: 192.168.1.1
      DNS: I tried 192.168.1.1, 8.8.8.8 and the DNS of my provider

      @Klaws:

      Just out of curiosity…which ISP is using PPPoE over VLAN6?

      Not the German Telecom, they use PPPoE over VLAN7.

      Chello?

      The ISP is XS4ALL (Dutch)

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        I assume your WAN address is a public IP?

        Do you have a default gateway set? System: Routing: Gateways:
        Do you have a default route set? Diagnostics: Routes:

        So you can still ping from the webgui but there is no route from the client? But DNS is working.

        Steve

        1 Reply Last reply Reply Quote 0
        • R
          Ramy
          last edited by

          @stephenw10:

          Do you have a default gateway set? System: Routing: Gateways:

          That was the problem! The default gateway was 192.168.1.1, I've changed the default gateway to the gateway of my provider and it worked!

          Thanks a lot for the help!

          1 Reply Last reply Reply Quote 0
          • Z
            zenny
            last edited by

            I had the same problem after an upgrade (both on nanobsd and hdd installation).

            I solved by going to 'Interfaces >> LAN' and change the gateway to 'none' and LAN can access internet. I do not know whether this is the way to do or not?

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              @zenny:

              I solved by going to 'Interfaces >> LAN' and change the gateway to 'none' and LAN can access internet. I do not know whether this is the way to do or not?

              There should NOT be any GW for non-WAN interfaces.

              1 Reply Last reply Reply Quote 0
              • Z
                zenny
                last edited by

                @doktornotor:

                @zenny:

                I solved by going to 'Interfaces >> LAN' and change the gateway to 'none' and LAN can access internet. I do not know whether this is the way to do or not?

                There should NOT be any GW for non-WAN interfaces.

                Thanks for confirming. :-)

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Indeed. We don't know Ramy's exact setup but since his default gateway was set to 192.168.1.1 it seems likely that he set a gateway on LAN which is incorrect. However his screen shot shows no gateway set on LAN so perhaps his more complex WAN setup caused problems. It would be interesting to know how the default gateway ended up set like that if no gateway was ever set on LAN.

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • K
                    Klaws
                    last edited by

                    @Ramy:

                    @stephenw10:

                    Do you have a default gateway set? System: Routing: Gateways:

                    That was the problem! The default gateway was 192.168.1.1, I've changed the default gateway to the gateway of my provider and it worked!

                    Shouldn't the gateway there be "dynamic", as WAN goes over PPPoE? In theory, the ISP could change the default gateway….

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Exactly, it should. However since the WAN is PPPoE over VLAN in this case perhaps he needed to manually configure some things that ended up overriding the ISP supplied details.

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • R
                        Ramy
                        last edited by

                        I've attached a screenshot of "Routing > Gateways". Somehow GW_LAN was set as default, I've set WAN_PPOE default and the problem was gone. The WAN gateway is dynamic.

                        ![Schermafbeelding 2013-07-06 om 13.42.45.png](/public/imported_attachments/1/Schermafbeelding 2013-07-06 om 13.42.45.png)
                        ![Schermafbeelding 2013-07-06 om 13.42.45.png_thumb](/public/imported_attachments/1/Schermafbeelding 2013-07-06 om 13.42.45.png_thumb)

                        1 Reply Last reply Reply Quote 0
                        • D
                          doktornotor Banned
                          last edited by

                          @Ramy:

                          Somehow GW_LAN was set as default, I've set WAN_PPOE default and the problem was gone. The WAN gateway is dynamic.

                          I've noticed when you edit the LAN GW (e.g., change the monitoring IP), it somehow makes itself default. I deleted the LAN GW altogether and have had zero issues since then.

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            As mentioned above you should not have a gateway on LAN.

                            The only time you would ever want that is if you have some downstream router with another subnet behind it such that pfSense needs to know where to route traffic to get to it.

                            Usually you only see a LAN gateway in the gateway table like that if you have set one on the LAN config page. Your screenshot in the first post shows no gateway set but perhaps you set one subsequently? Either way make sure it is not set now and remove it from the gateway table.

                            Steve

                            1 Reply Last reply Reply Quote 0
                            • R
                              Ramy
                              last edited by

                              @stephenw10:

                              As mentioned above you should not have a gateway on LAN.

                              The only time you would ever want that is if you have some downstream router with another subnet behind it such that pfSense needs to know where to route traffic to get to it.

                              Usually you only see a LAN gateway in the gateway table like that if you have set one on the LAN config page. Your screenshot in the first post shows no gateway set but perhaps you set one subsequently? Either way make sure it is not set now and remove it from the gateway table.

                              Steve

                              I haven't set a gateway on LAN after I created this thread. I don't know why it was there.

                              I've removed the gateway.

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