Client conection lost after client reboot.
-
Hi everyone.
I have a very strange problem and im not sure if its a hardware or software issue.
I installed pfSense v2.5.2 on Protectli FW4B. I have my DSL modem connected to LAN0 (WAN) port, and my PC connected to LAN1. I run through standard pfSense installation wizard, it all configures automatically, firewall works, my PC gets IP address assigned via DHCP i have my internet up and running everything is working as it should.
However, as soon as i restart my PC, i can no longer connect to internet nor i can connect to pfSense box via web interface or SSH. I tried pinging the box, but there is no response from 192.168.1.17 which is the static IP address i assigned.
This is where it gets strange. My network adapter still gets IP address assigned after my PC was rebooted. How is it possible that IP address gets assigned, but there is no communication at all?
I tried playing with all DHCP settings in Services / DHCP Server none of them helped. Only when i manually reboot the firewall, connection gets restored and everything works fine until i reboot my PC again.
Im using Arch Linux on my primary machine, i tried different cables and different network adapters but nothing helped. Same thing happens on my Windows machine and my laptop. I reinstalled pfSense several times, no additional packages have been installed, im using default configuration that pfSense wizard is setting up and issue is still there.
Is there anything im missing here or this just might be a hardware issue?
Thank you all.
-
@alex303 said in Client connection lost after client reboot.:
response from 192.168.1.17
You diverted from the default installation.
What about an installation where you change nothing, except the password ?192.168.1.17 is strange.
192.168.1.1 would be good - that's why it's the default, 192.168.1.254 next best. Never understood why a IP of a gateway should be somewhere in the middle of the IP range. I known, technically, it isn't wrong. -
Believe me sir. I tried all defaults. Including 192.168.1.1. As i said, i did fresh reinstall several times, and went through wizard like an absolute beginner by just clicking next, next, finish. I only changed login password. But issue is still there. This is why i suspect that there is a hardware preoblem. Unless, of course, there is a some option somewhere in the settings that im not aware of.
-
After rebooting, when your PC comes online again, did you saw the DHCP negotiation on pfSense -> Status > System Logs> DHCP log.
The DHCP lease was visible here Status > DHCP Leases ?The IP/mask/gateway/DNS received on the PC were ok ?
-
This is the DHCP status after i reboot my Linux machine, and go to Windows. As you can see DHCP assigns everything as it should, but there is no connection to internet or pfSense box. These assigned parameters are 100% indentical to the parameters that get assigned after i reboot my pfSense box. The only difference is, i have internet connection and i can access my pfSense box via web gui.
For the sake of this thread, i have cleaned DHCP log and repeted the whole process of rebooting the PC and then pfSense box. This is the fresh DHCP log:
I have "masked" MAC address.
-
Issue resolved by replacing faulty adapter that only had 4V at the output.
-
At the client? That's a bizarre fault!
-
No. It was the power adapter on a DSL modem that was plugged into the Protectli box WAN port. What led me to believe it was the power issue, were the leds on DSL modem that used to shine much brighter. Also, if i plug my PC directly into the DSL modem, i have access to internet, but as soon as i reboot, or connect to its built in WiFi via phone, modem hangs and connection is lost.
I took my trusty multimeter and measured 4V instead of 9. I replaced the adapter with the brand new and beefier 9V adapter, and all issues are gone.
Why was the power adapter on my DSL modem causing Protectli box to be inaccessible after i reboot my PC is beyond me.
I have successfully configured pfSense, installed pdBlockerNG, and routed all traffic through NordVPN. Everything just works.
-
Ah, that sort of adapter. Nice catch. Yeah weird set of faults, glad you found it though.
