DHCP issues
-
OK and in which log should I look? General?
Can not find something special. -
Look for these :
@interessierter said in DHCP issues:Apr 12 15:17:13 dhcpleases Sending HUP signal to dns daemon(76835)
which should be in the DHCP log ^^
The dhcpleases process is the one that can restart unbound if a new DHCP lease are registered.It could also be an interface that goes up and down. See System log for that.
Can you list your services ?
Like :
Some of these could be candidates.
-
DHCP Log is pretty boring:
May 1 09:23:30 dhcpd DHCPACK on 192.168.1.51 to 00:0a:b3:03:0b:72 (gira) via re2
May 1 09:23:30 dhcpd DHCPREQUEST for 192.168.1.51 (192.168.1.1) from 00:0a:b3:03:0b:72 (gira) via re2
May 1 09:23:30 dhcpd reuse_lease: lease age 572 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.1.51
May 1 09:23:30 dhcpd DHCPOFFER on 192.168.1.51 to 00:0a:b3:03:0b:72 (gira) via re2
May 1 09:23:29 dhcpd DHCPDISCOVER from 00:0a:b3:03:0b:72 (gira) via re2
May 1 09:23:29 dhcpd reuse_lease: lease age 571 (secs) under 25% threshold, reply with unaltered, existing lease for 192.168.1.51
May 1 09:19:28 dhcpleases Sending HUP signal to dns daemon(86307)
May 1 09:19:28 dhcpd DHCPACK on 192.168.1.53 to 68:9a:87:9a:bb:5f (amazon-07146cf52) via re2
May 1 09:19:28 dhcpd DHCPREQUEST for 192.168.1.53 from 68:9a:87:9a:bb:5f (amazon-07146cf52) via re2
May 1 09:13:58 dhcpleases Sending HUP signal to dns daemon(86307)
May 1 09:13:58 dhcpd DHCPACK on 192.168.1.51 to 00:0a:b3:03:0b:72 (gira) via re2services:
-
This one restarts unbound :
@interessierter said in DHCP issues:
May 1 09:13:58 dhcpleases Sending HUP signal to dns daemon(86307)
are there more ? how often ?
Who is this :
The ancient one ?
These :
arpwatch - bandwithd - clamd - darkstat - radiusd - snort - squidvnstard : don't know.
iperf : idem.are, what I call, expert packages.
Solid knowledge of the (FreeBSD) file system and OS specific know hows. Otherwise, setting them up and be able to debug will be a huge no-go.
These are all packages that are designed to run without a GUI front end. The fact that pfSEnse offers a GUI front end does not mean they are easier to administer. On the contrary.I advise you to stabilize your system first. That means : use what you get when you installed pfSense. Nothing more.
-
Hi!
The system run now since years with this package and mostly the same configuration. Is use the DNSBL for getting IP lists and block if there is a request coming. When I disable the service, there is no change in the behavior, also when I disable pfBlocker
-
PS: On the gui I have no option anymore to uninstall this services, they are not listed andmore in the installed packages view. That is since there was a need to recover the firewall and restore from backup
-
@interessierter said in DHCP issues:
no option anymore to uninstall this services
So the settings are rather 'non-defined'.
A good reason the re set it up - clean. -
No the installed software is simply not in the section of installed addin.
I have reinstalled and restores with a backup 3 weeks ago
-
It seems like that every time the DHCP server is writing this one in the Log:
May 2 09:50:08 dhcpleases Sending HUP signal to dns daemon(86307)
The DNS Resolver restart
-
@interessierter said in DHCP issues:
It seems like that every time the DHCP server is writing this one in the Log:
May 2 09:50:08 dhcpleases Sending HUP signal to dns daemon(86307)
The DNS Resolver restartThat's normal.
THe question to be asked is : what is the reason that a device (more, devices ?) are asking every 3 seconds for a new lease ?
What is the lease time setup in pfSense => DHCP server ?
What is the lease time received by a (the) device(s) ? ( on a Windows PC, ise "ipconfig /all" and you see the lease start and end)Also,
If this option is set (checked) :
Then yeah, you're asking that unbound, the Resolver, gets restarted when a new DHCP gets registered.
For this and more reasons, it is very advisable to declare all your known devices with a DHCP-static -leases on pfSense.
This way unbound doesn't get hammered any more if some stupid device is re asking a new lease every XX seconds.Still, look for this device, and throw it out of the windows - out of the Wifi range if you have one.
-
DHCP registration is checked as this makes sense why not?
And you are right, it seems like my dhcp lease is only 3 secs valid. But where is the option to change this? I have never touched this
-
I have checked again the settings. The field was simply empty in the GUI, and the default is 7200 sec. I have no idea why he was refreshing it all 3 secs. I have added now 7200 sec in the field, now the lease time is at it should be.
I will follow up if the DNS server is still crashing however, it seems like the Backup/Restore is not really propery working right now
-
@interessierter said in DHCP issues:
The field was simply empty in the GUI, and the default is 7200 sec. I have no idea why he was refreshing it all 3 secs. I have added now 7200 sec in the field, now the lease time is at it should be.
If the 'device' wants a certain lease time, it can have it.
All devices are not equally 'designed' ;) Some exists to really do the max to break your network - a lease time of 3 seconds make no sense at all.
If a device doesn't specify a requested lease time, pfSEnse will offer it's default value, that is 7200 seconds. Still, keep in mind that the 'device' can override this, and re asks a new lease when ever it wants.
Best solution is : see if this behaviour can be changed for this device. You have to change it's settings.
If not => it belongs in the waste bin.@interessierter said in DHCP issues:
DHCP registration is checked as this makes sense why not?
Again : every new lease WILL restart the resolver, so that it includes the new IP and it's hostname.
That is, this functionality is logic, if you want to be able to resolve the hostname of your device. Very useful if you want to connect to it from another device.
But ask yourself : do you really want to connect to your phone ? The answer is probably : no.And again : in company networks, and well setup private home networks, all devices are staticliy mappedDHCP leases. Only unknown devices are left 'non configured', because you don't know their MAC address anyway.
That is : unknown devices (visitors to your network etc) belong on a dedicated - non private - network. -
I know that other devices can maybe overwrite the offer of the lease time. After I changed the value to 7200, the server no starts again all 7 minutes. Sure the situation is better, but not entirely done right now.
I have found out, that my sony beamer is asking all 5secs for a IP. And this device have already his static dhcp IP address, but not set directly on the device.
Yes I want to connect my device to wlan, but its a different network and so out of scope here anyway
-
@interessierter said in DHCP issues:
And this device have already his static dhcp IP address, but not set directly on the device.
Devices that have a static DHCP on pfSense are included in the DNS for live, so no DNS restarts will happens when these devices asking for a new lease.
@interessierter said in DHCP issues:
that my sony beamer is asking all 5secs for a IP.
Normally, devices start their DHCP-client that asks for a lease when it's interface goes up (which implies it was down just before). Check that device.
Or, by default :@Gertjan said in DHCP issues:
throw it out of the windows
