[Solved] I can't get Internet access on the LAN side…
-
ALright, I think I figured out the problem. It was my LAN network card. I started thinking it was that because I had been seeing this error message on the Pfsense console: "dc_setcfg failed to force tx to idle state".
I tried using a USB to RJ45 instead and I am able to get out on the Internet. And it's running very fast. Before, everything was fairly slow. That's what I get for grabbing one of my many old network cards that have been floating around my stuff for years. Something was probably damaged on the card.
Thanks Steve.
-
Don't use the installer interface to configure your firewall. I did this for a day. If you set the ip address to something rather than 192.168.1.1 you'll never get to the internet. Don't turn on DHCP from the installer either.
Do your change in the web interface.
I re-installed several times, and until I stopped making changes in the installer and used the Web Interface I could not get to the internet.
-
That certainly shouldn't be the case. I have set a different LAN subnet at the initial console interface setup a number of times with no issues.
If you have found a bug in 2.1 and can pin down the exact circumstances that trigger it I'm sure the devs would love to hear about it in a redmine report. https://redmine.pfsense.org/Steve
-
Don't use the installer interface to configure your firewall. I did this for a day. If you set the ip address to something rather than 192.168.1.1 you'll never get to the internet.
Thank you for this four year old posting. I built a new 2.3.3-RELEASE-p1 pfSense server today and set the IP address to a different address at the console. Spent HOURS trying to get any routing from the LAN <> WAN while I could see the WAN was running fine, even with IPv6. I did a factory reload and set the LAN IP using the web config and this time all is well. There might be a four year old+ lurking bug in there somewhere!
There were three gateways, one for the IPv4 and one for the IPv6 of my Comcast connection, but there was also a third one marked "Default" which I could never delete. After the factory clear and functioning routing I only had the two normal gateways. I'm sure that odd third one was causing the problems.
-
Hello all and sorry for bumping an old thread.
The reason for doing this is the exact problem that @DKirk had. I changed the LAN IP from console ==> no access to WAN. When I changed the LAN IP via the WebGUI. It worked straight away. I'm on pfSense 2.3.4-RELEASE.
I have pfSense installed on ESXI 6.5 and I'm using 2 NIC's. If I can do anything to provide more info to eliminate this bug I'd be happy to :)
-
If you can replicate this reliably then please detail the steps taken and result and add it to a redmine ticket: https://redmine.pfsense.org/
Thanks,
Steve -
Now I know that pfsense initially blocks all traffic by default
And just to correct this sentence from the first post..
pfSense does not block all traffic by default. It blocks all unsolicted inbound traffic and allows all outgoing traffic by default. For those that might come along, read that and become confused.
;)
-
And just to correct this sentence from the first post..
pfSense does not block all traffic by default. It blocks all unsolicted inbound traffic and allows all outgoing traffic by default. For those that might come along, read that and become confused.
;)
My LAN cannot access the internet until I add a firewall rule for LAN to access any outside.
-
The default rule on LAN is ANY ANY… So whatever you think your lan is, its not the actual lan interface.. Yes if you add an opt interface there will be no rules on it and you will have to create them.
BTW this thread is from 2013, and then someone neco'd it back in 2017..
-
Hey Guys,
I am new to pfsense and it is quite the journey.
as for my issue
when i first installed pfsense
I had internet working fine but was not able to connect via openvpn so then i decided to reboot and was able to connect to openvpn then another issue was created i can no longer connect to the internet via the LAN or OpenVPN connect but able to access all resources on the lan
LAN is 10.X.X.X/8
VPN is 192.X.X.X/24
DMZ is 172.16.X.X/12
WAN
WAN1
WAN2I have surricata and squid on board but i have not blocking anything just alerting
I am also get an error see image
i am able to ping using the pfsense web interface ping tool using wan
and able to connect to vpn
also another question for you guys how can i use the same gateway for all the wan interfaces.
-
Hi,
Your question is not related to the original one (from 2013 !! ).
For your firewall wall rule error : See https://forum.pfsense.org/index.php?topic=147333.0
Btw : new to pfSennse and installing right away surricata, squid and OpenVPN …. :o
What about step-by-step approach ? ;) -
Locking this thread. Waaaaay too old! ;)
