Client can not renew IP address.
-
Randomly when I wake up in the morning my clients can not get a IP address. I can also not access the WebUI or SSH after assigning manual IP on same subnet to troubleshoot.
If I assign a IP address manually on the computer internet works fine on the device so routing is working.
This is on a SG-1100 only non-default packages installed are pfblocker-ng, ntopng, and Telegraf
-
@anzenketh said in Client can not renew IP address.:
my clients can not get a IP address.
Hi,
you might want to look at the DHCP log when the client is not receiving an IP
Btw, you use long lease times or the default?
+++edit:
@anzenketh "I can also not access the WebUI or SSH after assigning manual IP"- in this case, how do you get access to the box? (restart?)
- does the box respond to PING?
-
- I am using default lease times.
- Regarding responding to a ping I can not recall.
- To regain access. I unpluged the box and plugged it back in. Did not have a console terminal I could use.
At Sep 12 23:25:26 I see the DHCP server starting but not shutdown command. This is around the time I had the issue. I do not show any log lines after the following log line:
Sep 12 23:25:26 dhcpd Server starting service.
Until Sep 13 10:11:52 when I started troubleshooting the system.
All Devices did not work until after Sep 13 10:12:32 when I rebooted the pfsence box by unplugging it then plugging it back in. (I did not have working console).
-
@anzenketh said in Client can not renew IP address.:
pfsence box by unplugging it then plugging it back in.
This is not a good solution...
- be sure to gain proper console access to analyze the error / issue
- be sure to do this because of violent shutdowns
https://docs.netgate.com/pfsense/en/latest/hardware/forcing-a-filesystem-check.html
btw:
in the case of this error, we can only proceed using the console -
@DaddyGo Agreed it is not a good solution. I did not have any other viable ones at the time as I did not have a system that I could use to get console access. I lacked a portable device that had the appropriate drivers for USB to serial. I have rectified the situation so I will not run into that problem in the future. I am now able to get console access to the system in the case it is needed in the future.
Thank you for letting me know what needs to be done in the future.