No internet on LAN
-
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 think this is the same issue I am having since upgrading the the latest version of 2.1.
The Post I have is http://forum.pfsense.org/index.php/topic,63557.0.html
-
I think this is the same issue I am having since upgrading the the latest version of 2.1.
The Post I have is http://forum.pfsense.org/index.php/topic,63557.0.htmlWould be more useful to answer the previous post…
-
It's not the same problem since Ramy is able to ping external sites from the pfSense box. His WAN connection, PPPoE over VLAN, is working fine. Impossible to say further until he reports back but at this point my money would be on misconfigured client since it's not using DHCP.
Steve
-
Just out of curiosity…which ISP is using PPPoE over VLAN6?
Not the German Telecom, they use PPPoE over VLAN7.
Chello?
-
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 providerJust 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)
-
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
-
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!
-
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?
-
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.
-
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. :-)
-
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
-
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….
-
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
-
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) -
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.
-
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
-
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.