Can't access internet fresh install
-
I have almost the same at home - rooftop device that the ISP manages. They set its LAN side to 192.168.100.1
Cable comes down from the roof, I plug it into pfSense WAN. pfSense WAN gets an IP address from the rooftop device. All is well.
In this configuration the factory default config "just works" .Check that your pfSense WAN is getting an IP address by DHCP from the rooftop device, and that the gateway it is given is the IP address of the rooftop device. From pfSense confirm that you can ping the rooftop device.
If you are not already starting from the factory default config, then you could reset to factory defaults - because that should get you internet in your case.
-
So I'm pulling an ip from my ISP 172.16.x.x and I can ping it from both the pfsense box and a computer on the lan side of the pfsense box.
Here is the funny part my installation media has 2.2.3 on it, after another fresh install I access the web gui with my laptop and while on the dashboard it told me that an update was available, i was able to update to 2.2.4 however I can't access any website or access the internet with any of the computers just the pfsense box, I'm also able to install packages with the gui on my laptop.
So the pfsense box is able to download updates and packages but computers on the lan side can't access the Internet just the pfsense gui.
Suggestions??
Thanks -
As a guess since it's common, did you make the mistake of specifying a gateway for your LAN? Only WAN needs a gateway. Setting one for LAN will kill the connection.
-
I double checked there is no gateway on the lan interface
-
Post screenscaps of your WAN settings, LAN settings and LAN firewall rules. It should just work if you haven't monkeyed with any LAN rules, which by default allow everything outgoing.
-
here are the screencaps
-
So I'm pulling an ip from my ISP 172.16.x.x
Dude, stop blocking RFC1918 on WAN if your WAN is 172.16.x.x
-
So I'm pulling an ip from my ISP 172.16.x.x
Dude, stop blocking RFC1918 on WAN if your WAN is 172.16.x.x
that's fine as long as you don't need to allow private sourced ingress traffic on WAN (which is usually true in double NAT scenarios).
-
I've tried with that box checked and unchecked still the same,
Not sure why i can install packages thru the web gui and check for updates without any issues, and ping external sites from within the pfsense box shell.
This is all on a fresh install without any additional configuration it should work out of the box.
I been using pfsense for years never really had any issues i could not figure out by just doing some research but this one got me stomp
-
Have you messed with Firewall > NAT?? Outbound should be automatic. Post a screenshot of that while you're there.
Are you testing by pinging IP addresses or hostnames?
-
Have you messed with Firewall > NAT?? Outbound should be automatic. Post a screenshot of that while you're there.
Are you testing by pinging IP addresses or hostnames?
No I have not, just double checked to be sure, it is just a fresh install of 2.2.3 and upgraded to 2.2.4 either one could not access any website, no other tweaks have been done.
Forgive me, just out of curiosity I installed another utm on the same box and everything works, also using my netgear router by itself everything works fine.
I really need to make pfsense works as it is what I'm familiar with and love to use, at a lost not sure what is going on.
note that this is a fresh install with not other settings alter, please advise!!
thanks
-
Dunno what else you want to advise. Start from scratch. This works out of the box.
-
The 2 things I can think of that could be done to break this are:
a) Mess with outbound NAT - it needs just Automatic Outbound NAT.
b) DHCP Server on LAN - check that there are no special things specified in any of the advanced bits (like maybe a different gateway being given to the LAN clients)Check the LAN clients network settings and make sure they are getting pfSense LAN IP as their gateway and DNS.
traceroute from a LAN client to 8.8.8.8 and see how far it gets and what path it takes.
-
You could also switch wan and lan around… That breaks things
Rather than trying to figure out what you did wrong, I'd do a reinstall.
-
Done reinstalling several times, no further tweaking or setting changes is always the same.
I can via web gui install updates and packages, via pfsense box shell ping to the outside via ip or hostname, i can't however access the Internet from any box connected to the lan side.
It is not my first time installing/using pfsense i usually solve any issues by just searching the forums but this time i can't find the answer.I know pfsense works out of the box, but not sure what's going on this time.
-
What's up with your IPv6 definition on LAN? Are you even running IPv6 on your network? You have the IPv6 Configuration Type set to Track Interface, and then below you have the Track IPv6 Interface set to WAN. This isn't default behaviour on a fresh install. Change IPv6 Configuration Type back to None and see if that helps.
-
Im done a fresh install of pfsense 2.2.3 the issue I'm having is that while I'm pulling and ip from my ISP on the WAN side and i can access the pfsense web interface I can't access any website, connection is listed as limited on windows machine, also my ununtu box is the same.
If I use just my wireless router without pfsense everything works fine, note that the I have tried just the pfsense box with wan to isp and lan directly to my computer bypassing the wireles router and switch and still the same, also when i use the wireless router has dhcp disabled an just act as AP.
The same box used to worked flawlessly in the same house and same provider a year ago, then I went to Korea for a year and just got back and having this issue.
Any suggestions would be appreciated.
Thanks
I have same problem like you. Here how I fixed it.
Go to Interface - WAN - Uncheck Block private networks.
Go to Services - DNS Resolver - Check Enable Forwarding Mode.Make sure everything else is default.
-