Getting KEA-DHCP mass entried in the log.
-
Gettting this smap in the DHCP log and its every 3 minutes
Nov 8 08:08:25 kea-dhcp4 17140 INFO [kea-dhcp4.leases.0x30e715d09000] DHCP4_LEASE_ALLOC [hwtype=1 a8:a1:59:9d:cf:c8], cid=[01:a8:a1:59:9d:cf:c8], tid=0xf3d46482: lease 192.168.1.3 has been allocated for 7200 seconds Nov 8 08:08:25 kea-dhcp4 17140 INFO [kea-dhcp4.dhcpsrv.0x30e715d09000] EVAL_RESULT Expression pool_lan_0 evaluated to 1 Nov 8 08:05:13 kea-dhcp4 17140 INFO [kea-dhcp4.commands.0x30e715c12000] COMMAND_RECEIVED Received command 'lease4-get-all' Nov 8 07:56:05 kea-dhcp4 17140 INFO [kea-dhcp4.leases.0x30e715d09000] DHCP4_LEASE_ALLOC [hwtype=1 52:fd:97:ac:47:88], cid=[01:52:fd:97:ac:47:88], tid=0xf081982e: lease 192.168.1.103 has been allocated for 7200 seconds Nov 8 07:56:05 kea-dhcp4 17140 INFO [kea-dhcp4.leases.0x30e715d09000] DHCP4_INIT_REBOOT [hwtype=1 52:fd:97:ac:47:88], cid=[01:52:fd:97:ac:47:88], tid=0xf081982e: client is in INIT-REBOOT state and requests address 192.168.1.103 Nov 8 07:56:05 kea-dhcp4 17140 INFO [kea-dhcp4.dhcpsrv.0x30e715d09000] EVAL_RESULT Expression pool_lan_0 evaluated to 1 Nov 8 07:55:33 kea-dhcp4 17140 INFO [kea-dhcp4.leases.0x30e715d09000] DHCP4_LEASE_ALLOC [hwtype=1 b0:f7:c4:45:49:7a], cid=[01:b0:f7:c4:45:49:7a], tid=0xe8998d2d: lease 192.168.1.100 has been allocated for 7200 seconds Nov 8 07:55:33 kea-dhcp4 17140 INFO [kea-dhcp4.dhcpsrv.0x30e715d09000] EVAL_RESULT Expression pool_lan_0 evaluated to 1 Nov 8 07:33:07 kea-dhcp4 17140 INFO [kea-dhcp4.leases.0x30e715d09000] DHCP4_LEASE_ALLOC [hwtype=1 da:d8:cb:59:a8:9f], cid=[01:da:d8:cb:59:a8:9f], tid=0xca6defa6: lease 192.168.1.101 has been allocated for 7200 seconds Nov 8 07:33:07 kea-dhcp4 17140 INFO [kea-dhcp4.dhcpsrv.0x30e715d09000] EVAL_RESULT Expression pool_lan_0 evaluated to 1 Nov 8 07:30:58 kea-dhcp4 17140 INFO [kea-dhcp4.leases.0x30e715d09000] DHCP4_LEASE_ALLOC [hwtype=1 46:af:0f:a9:30:46], cid=[01:46:af:0f:a9:30:46], tid=0x43db326b: lease 192.168.1.108 has been allocated for 7200 seconds Nov 8 07:30:58 kea-dhcp4 17140 INFO [kea-dhcp4.dhcpsrv.0x30e715d09000] EVAL_RESULT Expression pool_lan_0 evaluated to 1 Nov 8 07:26:36 kea-dhcp4 17140 INFO [kea-dhcp4.leases.0x30e715d09000] DHCP4_LEASE_ALLOC [hwtype=1 c6:c8:05:a8:26:45], cid=[01:c6:c8:05:a8:26:45], tid=0x52835bb3: lease 192.168.1.227 has been allocated for 7200 seconds Nov 8 07:26:36 kea-dhcp4 17140 INFO [kea-dhcp4.dhcpsrv.0x30e715d09000] EVAL_RESULT Expression pool_lan_0 evaluated to 1 Nov 8 07:23:42 kea-dhcp4 17140 INFO [kea-dhcp4.dhcpsrv.0x30e715c12000] DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: /usr/local/sbin/kea-lfc -4 -x /var/lib/kea/dhcp4.leases.2 -i /var/lib/kea/dhcp4.leases.1 -o /var/lib/kea/dhcp4.leases.output -f /var/lib/kea/dhcp4.leases.completed -p /var/lib/kea/dhcp4.leases.pid -c ignored-path Nov 8 07:23:42 kea-dhcp4 17140 INFO [kea-dhcp4.dhcpsrv.0x30e715c12000] DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup Nov 8 07:22:51 kea-dhcp4 17140 INFO [kea-dhcp4.leases.0x30e715c18900] DHCP4_LEASE_ALLOC [hwtype=1 7c:d5:66:d4:f7:24], cid=[no info], tid=0x8d546fac: lease 192.168.1.105 has been allocated for 7200 seconds Nov 8 07:22:51 kea-dhcp4 17140 INFO [kea-dhcp4.dhcpsrv.0x30e715c18900] EVAL_RESULT Expression pool_lan_0 evaluated to 1 Nov 8 07:19:37 kea-dhcp4 17140 INFO [kea-dhcp4.leases.0x30e715d09000] DHCP4_LEASE_ALLOC [hwtype=1 1c:93:c4:54:de:39], cid=[01:1c:93:c4:54:de:39], tid=0x2352ea41: lease 192.168.1.102 has been allocated for 7200 seconds
-
@troysjanda I an on the 2.7.1RC and switched to the kea-dhcp backend.
-
@troysjanda Am similarly seeing the same noise in my logs - Production version of pfsense 23.09
hcp4.leases.0x2dd460018900] DHCP4_LEASE_ALLOC [hwtype=1 54:6c:eb:2d:47:7c], cid=[01:54:6c:eb:2d:47:7c], tid=0x88e85be4: lease 192.168.10.53 has been allocated for 7200 seconds Nov 8 16:18:04 kea-dhcp4 84135 INFO [kea-dhcp4.dhcpsrv.0x2dd460018900] EVAL_RESULT Expression pool_opt8_0 evaluated to 1 Nov 8 16:18:04 kea-dhcp4 84135 INFO [kea-dhcp4.dhcpsrv.0x2dd460018900] EVAL_RESULT Expression pool_opt7_0 evaluated to 1 Nov 8 16:18:04 kea-dhcp4 84135 INFO [kea-dhcp4.dhcpsrv.0x2dd460018900] EVAL_RESULT Expression pool_opt3_0 evaluated to 1 Nov 8 16:18:04 kea-dhcp4 84135 INFO [kea-dhcp4.dhcpsrv.0x2dd460018900] EVAL_RESULT Expression pool_opt6_0 evaluated to 1 Nov 8 16:18:04 kea-dhcp4 84135 INFO [kea-dhcp4.dhcpsrv.0x2dd460018900] EVAL_RESULT Expression pool_opt2_0 evaluated to 1 Nov 8 16:18:04 kea-dhcp4 84135 INFO [kea-dhcp4.dhcpsrv.0x2dd460018900] EVAL_RESULT Expression pool_opt5_0 evaluated to 1 Nov 8 16:18:04 kea-dhcp4 84135 INFO [kea-dhcp4.dhcpsrv.0x2dd460018900] EVAL_RESULT Expression pool_opt4_0 evaluated to 1 Nov 8 16:18:04 kea-dhcp4 84135 INFO [kea-dhcp4.dhcpsrv.0x2dd460018900] EVAL_RESULT Expression pool_opt1_0 evaluated to 1 Nov 8 16:18:04 kea-dhcp4 84135 INFO [kea-dhcp4.dhcpsrv.0x2dd460018900] EVAL_RESULT Expression pool_lan_0 evaluated to 1 Nov 8 16:17:44 kea-dhcp6 84874 INFO [kea-dhcp6.leases.0x237606018900] DHCP6_LEASE_RENEW duid=[00:01:00:01:25:75:5b:28:00:5b:94:d5:68:17], tid=0xc348b9: lease for address 2001:4d48:ad5c:fe10:0:f:10:42 and iaid=0 has been allocated Nov 8 16:17:44 kea-dhcp6 84874 INFO [kea-dhcp6.dhcpsrv.0x237606018900] EVAL_RESULT Expression pool_opt6_0 evaluated to 1
-
@Thondwe ok so its just not me. hope that i get a reply from netgate to say this is normal or how to fix if not.
-
It look like this for me, maybe because of the 7 VLANs on LAGG. It's too much useless information to me ... Nothing else to report I've a very basic config BTW :
2023-11-08 13:20:20.476501-05:00 kea-dhcp4 30424 INFO [kea-dhcp4.leases.0x31f54015f00] DHCP4_LEASE_ALLOC [hwtype=1 38:18:4c:13:47:cf], cid=[01:38:18:4c:13:47:cf], tid=0xfce4731b: lease 192.168.60.12 has been allocated for 7200 seconds 2023-11-08 13:20:20.476095-05:00 kea-dhcp4 30424 INFO [kea-dhcp4.dhcpsrv.0x31f54015f00] EVAL_RESULT Expression pool_opt11_0 evaluated to 1 2023-11-08 13:20:20.476063-05:00 kea-dhcp4 30424 INFO [kea-dhcp4.dhcpsrv.0x31f54015f00] EVAL_RESULT Expression pool_opt10_0 evaluated to 1 2023-11-08 13:20:20.476031-05:00 kea-dhcp4 30424 INFO [kea-dhcp4.dhcpsrv.0x31f54015f00] EVAL_RESULT Expression pool_opt6_0 evaluated to 1 2023-11-08 13:20:20.475999-05:00 kea-dhcp4 30424 INFO [kea-dhcp4.dhcpsrv.0x31f54015f00] EVAL_RESULT Expression pool_opt8_0 evaluated to 1 2023-11-08 13:20:20.475966-05:00 kea-dhcp4 30424 INFO [kea-dhcp4.dhcpsrv.0x31f54015f00] EVAL_RESULT Expression pool_opt7_0 evaluated to 1 2023-11-08 13:20:20.475934-05:00 kea-dhcp4 30424 INFO [kea-dhcp4.dhcpsrv.0x31f54015f00] EVAL_RESULT Expression pool_opt5_0 evaluated to 1 2023-11-08 13:20:20.475899-05:00 kea-dhcp4 30424 INFO [kea-dhcp4.dhcpsrv.0x31f54015f00] EVAL_RESULT Expression pool_opt4_0 evaluated to 1 2023-11-08 13:20:20.475841-05:00 kea-dhcp4 30424 INFO [kea-dhcp4.dhcpsrv.0x31f54015f00] EVAL_RESULT Expression pool_lan_0 evaluated to 1
-
@mr_nets dont have any vlans, I just have a very basic setup. Basiclly just stock setup.
-
That is the expected default logging in Kea. There is a scope for improvement!
-
@stephenw10 maybe better in the next rc or final release, or more likely in the 2.8.0 version?
-
Yes, more likely in the next version.
-
I'm on the 24.03-RELEASE and the Issue still persist:
A lot of those log entries:
INFO [kea-dhcp4.commands.0x281e4e812000] COMMAND_RECEIVED Received command 'lease4-get-all'`
-
Whole bunch of exciting work happening for Kea right now. Should be in 24.08-dev snap real-soon-now. (but really, actually, soon!)