Date: Sun, 08 Sep 2024 11:57:30 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 281361] ddclient: messages about unknown DHCP option keep cluttering the log Message-ID: <bug-281361-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281361 Bug ID: 281361 Summary: ddclient: messages about unknown DHCP option keep cluttering the log Product: Base System Version: 14.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: michael@vonglasow.com I keep getting the following error message in the log every time the IP con= fig on the external interface is renewed (15 minutes with my ISP): > Error:dhclient:unknown dhcp option value 0x7d **To Reproduce** Steps to reproduce the behavior: * Set up a network with a DHCP server. * Configure the DHCP server to send an unknown DHCP option (0x7d is known to work) * Configure a short timeout (under an hour) for DHCP leases. * Configure DHCP on one interface, and connect it to the network with DHCP server configured in the previous steps. * Observe the log **Expected behavior** I would expect ddclient to silently ignore any options it does not understa= nd (which is the recommended standard behavior for most parsers). If it does l= og a message at all, the log level should be Debug or Information at most, not Error. **Describe alternatives you considered** Reconfiguring the DHCP server to not set any obscure options ddclient does = not need or understand is not an option: the DHCP server is beyond my control (I probably won=E2=80=99t get my ISP to configure their DHCP server the way I = think it should be), and since lease times are such that renewals happen every 15 minutes, this really clutters up the logs. There may certainly be legit use cases why a DHCP server would specify DHCP options which some DHCP clients = do not understand. **Additional context** I=E2=80=99ve verified DHCP traffic with a packet capture tool, and the DHCP= offer indeed does have the unsupported option in it. The log entry has been around for a few versions and might have been present ever since I started using OPNsense on that particular ISP. It makes the logs hard to read when you=E2=80=99re trying to debug somethin= g, especially since it is logged as an error. The lower the log level, the eas= ier it is to filter out. Should I have filed this bug against the wrong component, please feel free = to move it or let me know where it should go. **Environment** OPNsense 24.7.3_1-amd64 (based on FreeBSD 14.1-release-p3); Franco Fichtner suggested I file my issue as a bug here (however, I don=E2=80=99t agree wit= h him that this is just a minor annoyance) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281361-227>