Re: verbose dhcp output

[Dan Williams <dcbw redhat com>]

On Sun, 2005-01-16 at 10:53 +0100, j bootlab org wrote:
> the connection seems fine, but at some point i get nonstop output to syslog:
> Jan 16 10:48:51 localhost NetworkManager: DHCP: actual data length was 100
> Jan 16 10:48:51 localhost NetworkManager: DHCP: Reply message was not not UDP (ip_hdr->protocol = 6, IPPROTO_UDP = 17), won't use it.
> Jan 16 10:48:51 localhost NetworkManager: DHCP: Waiting for reply...
> Jan 16 10:48:51 localhost NetworkManager: DHCP waiting for data, overall end_time = {1105885633s, -28774us}
> Jan 16 10:48:51 localhost NetworkManager: DHCP waiting for data of minimum size 28, remaining timeout = {16701s, 91084us}
> Jan 16 10:48:51 localhost NetworkManager: DHCP: Got some data to check for reply packet.
> Jan 16 10:48:51 localhost NetworkManager: DHCP: actual data length was 1500
> Jan 16 10:48:51 localhost NetworkManager: DHCP: Reply message was not not UDP (ip_hdr->protocol = 6, IPPROTO_UDP = 17), won't use it.
> Jan 16 10:48:51 localhost NetworkManager: DHCP: Waiting for reply...
> Jan 16 10:48:51 localhost NetworkManager: DHCP waiting for data, overall end_time = {1105885633s, -28774us}
> Jan 16 10:48:51 localhost NetworkManager: DHCP waiting for data of minimum size 28, remaining timeout = {16701s, 66944us}
> 
> "actual data length was" is  most of the time 1500 and sometimes 100.
> any idea what could cause this and/or how to silence it?

Well, we basically need to be sure that DHCP is working correctly for
users now and then make the DHCP bits of the code shut up.  I left all
the debugging syslog()s there so its easier for us to find bugs.  We
should probably have a proper "NetworkManager --verbose-level=x" and tie
the syslogs to that, either by making our own "nm_syslog (level,
"message", ...)" function with varargs, or some other way.

Patches? :)

Dan