Messages

Turns out it may have been a dodgy IPv6 device (an antique cctv camera). 

I restarted DHCPD6 and the problem stopped.  I suspect it would have restarted later anyway I identified the device  using the DUID in the log and searched the IPv6 leases. The device is now IPv4 only and scheduled for replacement.

So far the log file is behaving normally.

I don't think that the problem is the removal of circular logging.

In the first second of the new log today there were just under 2000 new entries. It's hard to see why dhcp would need to generate this level of logging on a domestic network with less than 40 active clients?

The message suggests that a lease has a very short life generating excess work for dhcpd?

Code Select Expand

<190>1 2022-03-03T00:00:00+13:00 OPNsense.xxxx.co.nz dhcpd 76891 - [meta sequenceId="1980"] Sending Reply to fe80::240:8cff:fe93:f120 port 546
<190>1 2022-03-03T00:00:01+13:00 OPNsense.xxxx.co.nz dhcpd 76891 - [meta sequenceId="1981"] Renew message from fe80::240:8cff:fe93:f120 port 546, transaction ID 0x7CE8EB00
<190>1 2022-03-03T00:00:01+13:00 OPNsense.xxxx.co.nz dhcpd 76891 - [meta sequenceId="1982"] Reply NA: address 2406:xxxx:x:xxxx::1234 to client with duid 00:03:00:01:00:40:8c:93:f1:20 iaid = 2 valid for 7200
seconds
<191>1 2022-03-03T00:00:01+13:00 OPNsense.xxxx.co.nz dhcpd 76891 - [meta sequenceId="1983"] Reusing lease for: 2406:xxxx:x:xxxx::1234, age 1404 secs < 25%, sending shortened lifetimes - preferred: 1, valid
5796

I have the same problem as OP with 12GB of file since last night. The system has crashed twice since the upgrade with no disk space left

While limiting the days to keep the log file as suggested is certainly helpful in keeping the system up I wonder what has changed as this seems a new problem since 22.1 and this amount of logging would appear to indicate an issue?