I thought I had put it in the Request section (section below) - dhcp DHCP-Request { update control { &DHCP-DHCP-Server-Identifier = 192.168.1.1 } if (&request:DHCP-DHCP-Server-Identifier && \ &request:DHCP-DHCP-Server-Identifier != &control:DHCP-DHCP-Server-Identifier) { do_not_respond } update reply { &DHCP-Message-Type = DHCP-Ack Packet-Dst-Port = 68 } dhcp_network dhcp_sqlippool_request linelog_dhcp } From: Freeradius-Users <freeradius-users-bounces+d.lake=surrey.ac.uk@lists.freeradius.org> on behalf of Matthew Newton via Freeradius-Users <freeradius-users@lists.freeradius.org> Date: Thursday, 31 July 2025 at 12:19 To: freeradius-users@lists.freeradius.org <freeradius-users@lists.freeradius.org> Cc: Matthew Newton <mcn@freeradius.org> Subject: Re: Unsure of linelog configuration On 31/07/2025 12:14, David Lake via Freeradius-Users wrote:
But my line log is only showing the first successful allocate. I have obviously mis-understood the syntax and positioning of linelog because it is basically working but not as I expected. Would welcome a pointer or two?
A renewing DHCP client will send a direct request, so won't hit the discover section. Put the logging in the request section instead. -- Matthew - List info/subscribe/unsubscribe? See https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.freeradius.org%2Flist%2Fusers.html&data=05%7C02%7Cd.lake%40surrey.ac.uk%7C7b56928dd16845eb247f08ddd024216a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C638895575794961415%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=DhPAlyDzFCni2e2O5Jv1A1U%2BwiP5g7SYS9YHMofsqSk%3D&reserved=0<http://www.freeradius.org/list/users.html>