Can't login to web configurator or ping the LAN ip
-
I am new to pfsense. I am running v2.2.p2 on a gigabyte motherboard. The WAN is set to DHCP and the LAN is statically set to 192.168.1.15. I saw the web configurator long enough to set up the initial settings, then was not able to ping the LAN or log into the web configurator. I tried to ping my ip address to my laptop from the console and get a message saying that the host it down. I'm hoping that I can get some help with this issue.
-
I'm assuming you mean 2.4.4p2? Because 2.2 is years old.
Is your laptop getting an IP from the pfSense DHCP server?
Host is down implies it's not responding to ARP even so make sure it's connected to correct NIC and shows link. Make sure the laptop and LAN interface both show as in the3 same subnet.
Steve
-
Also make sure your WAN interface is not using 192.168.1.x for its subnet, otherwise you've made a conflict which would also explain your symptoms.
-
There wasn't a 2.2p2, atleast not in the release history. So having a hard time working out what sort of typo he could had to come up with 2.2.p2 to be honest? ;) There wasn't a 2.4.2p2 only p1, etc.
The default rules on lan are any any.. Are you saying your client gets dhcp from pfsense but can not ping pfsense IP on its lan this 192.168.1.15 you set it to be?
I would suggest you rest the IPs from console and validate your setting the correct interface, etc..
-
@stephenw10
Hey Steve,You are correct. When I first started my pfSense firewall, I used the image for 2.4.4p1 and upgraded through the console. I do have the WAN side as DHCP. I am connected to correct NIC's. I am getting the WAN feed from a wireless router instead of the modem itself. Could that be the issue? When I look at the network settings, I'm connected to the WiFi and connected to the LAN without Internet which is all on the same network.
Thanks,
Jon
-
@jimp
I set up the WAN port to be DHCP, and it chose an ip address in the 192.168.1.x range. Should I change it to static? -
@johnpoz
When I initially set up my firewall, I used the 4.2.2p1 image and upgraded to 4.2.2p2 from the console. I have the WAN side set up as DHCP and the LAN set statically as 192.168.1.15. When I ping from the laptop, it times out with 100% loss, and when I ping from the console, I get Host is down. -
I think someone is dyslexic? Or drunk?
4.2.2p1? ;)
Its 2.4.4p1
So you you have pfsense getting its wan via wireless?? Yeah that not any sort of optimal sort of configuration that is for sure.. Unless your talking some sort of wisp with say a 4G/LTE modem that hands that off to ethernet?
-
@sugaredaxe said in Can't login to web configurator or ping the LAN ip:
I set up the WAN port to be DHCP, and it chose an ip address in the 192.168.1.x range.
The WAN and LAN cannot be in the same subnet. Since changing the WAN side usually means changing everything else that might be using that subnet too it's probably easier to change the pfSense LAN subnet to something else. 192.168.100.1/24 for example.
Steve
-
@stephenw10
I change the LAN to 192.168.2.1 subnet and restarted my pfSense box. Connected my laptop to the firewall and ran an ipconfig. I received an IP address and a subnet mask, but not a gateway address. I then went into the internet properties on the laptop and set a static address for the LAN network. I can now ping from the laptop to the LAN port with no loss, but when I ping from the console to the laptop I get 100% loss and the web configurator cannot be reached. I seem to make some progress, but I can't seem to get this figured out.Thanks,
Jon
-
@sugaredaxe said in Can't login to web configurator or ping the LAN ip:
I received an IP address and a subnet mask, but not a gateway address.
Then something is wrong - out of the box the dhcpd in pfsense would hand its own IP for the gateway.
So unless you on purpose went into the dhcp server settings and set NONE for the gateway it would hand out its own IP address.
-
@johnpoz
I have the LAN port set to be static. Should I have set it to be DHCP instead? -
Huh? No you can not run a dhcp server (dhcpd) on a dhcp client interface..
What I am saying is if you got dhcp from pfsense dhcp server (dhcpd) then what you saying not getting an IP for the gateway is broken... And not really possible without something major being wrong - unless you went into the dhcp server setting on pfsense and set NONE for the gateway.
-
@johnpoz
How would I check if the dhcp server is correct in the console? -
it would be correct unless you ON Purpose went in there and changed it to NONE.
You can reset the IP of your interface at the console and it will ask you to turn on or off the dhcp server..
-
@johnpoz
This will be on the LAN side, correct? -
yes this is on the LAN side.. Normally your WAN would be dhcp..
-
@johnpoz
I entered the LAN address that I wanted along with the subnet mask. It is asking me 'For WAN, enter the new LAN IPv4 upstream gateway address. For a LAN, press <ENTER> for none:' Can I enter the same address the I just entered, or does it have to be different? -
Dude I have no idea what your doing... Resetting your lan address would have NOTHING to do with your wan IP..
You used the #2 on console to set your LAN IP.. on LAN no there would be NO gateway.. Its not a WAN is it, so no there would be NO gateway...
Click the ENTER button.. Just as it says!! This is your LAN... If you were setting gateway on your lan then yeah no wonder you prob have it all F'd up!!
-
Yes, you should not have a gateway configured on the pfSense LAN interface.
The interface IP itself should be handed to clients via DHCP if the setup is default.
Check in Services > DHCP Server > LAN tab.
The gateway field there should either be empty or set to the LAN IP address which looks to be 192.168.2.1.
Steve
