Re: dhcpd syslog message no longer shows client Hostname?

[christos%astron.com@localhost (Christos Zoulas)]

In article <E03A1421-E2B2-4472-BD53-154F5EE6ED96%distal.com@localhost>,
Chris Ross  <cross+netbsd%distal.com@localhost> wrote:
>
>  Apologies to the list for asking about an issue with a very old
>system.  But, I have a router that I've failed to plan an upgrade for
>for quite some time, running dhcpd 3.0.3 on NetBSD 5.2.x.
>
>  I reconfigured an internal network last night, and noticed that where
>in /var/log/messages I used to see the client "Hostname" value, I am no
>longer.  I'm seeing the local address of the server/router (Server-ID),
>where I was before, but note a lack of client identifier in the log
>where I used to see it.  An example of an attach this morning:
>
>Dec 30 06:35:47 server dhcpd: DHCPOFFER on 172.16.12.28 to
>aa:bb:cc:dd:ee:ff (RossFamilyiPad) via vlan2
>Dec 30 06:35:48 server dhcpd: DHCPREQUEST for 172.16.12.28
>(172.16.12.30) from aa:bb:cc:dd:ee:ff (RossFamilyiPad) via vlan2
>Dec 30 06:35:48 server dhcpd: DHCPACK on 172.16.12.28 to
>aa:bb:cc:dd:ee:ff (RossFamilyiPad) via vlan2
>
> I'm now seeing:
>
>Dec 30 23:33:09 server dhcpd: DHCPOFFER on 172.16.8.61 to
>aa:bb:cc:dd:ee:ff via vlan2
>Dec 30 23:33:10 server dhcpd: DHCPREQUEST for 172.16.8.61 (172.16.8.63)
>from aa:bb:cc:dd:ee:ff via vlan2
>Dec 30 23:33:10 server dhcpd: DHCPACK on 172.16.8.61 to
>aa:bb:cc:dd:ee:ff via vlan2
>
>  I assigned fixed-addresses to a number of devices, by hardware
>ethernet address, including the aa:bb:cc:dd:ee:ff device shown here.  Is
>that the reason I'm not longer seeing the client identifier/Hostname
>parameter in the logs?  Is there any way I can turn that back on?  I
>don't see in the man pages a way to control/influence what is logged.

Try looking at the traffic:

tcpdump -vv -s 1500 -i vlan2 port bootpc or port bootps 

christos