Bug 20371
| Summary: | dhclient inserts bogus configurations | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Phil Homewood <pdh> |
| Component: | bin | Assignee: | Martin Blapp <mbr> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 4.1-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-bugs->obrien Over to the maintainer. Responsible Changed From-To: obrien->freebsd-bugs I am not the single dhclient maintainer now. State Changed From-To: open->feedback Does this problem still exist with DHCP 3.0? Can you try DHCP 3.0 from ports (or in the base system of -CURRENT). Responsible Changed From-To: freebsd-bugs->murray Does this problem still exist with DHCP 3.0? Can you try DHCP 3.0 from ports (or in the base system of -CURRENT). No can do. I left that employer over 12 months ago, and that particular network was dismantled not long thereafter. Responsible Changed From-To: murray->mbr Take this PR. I'll look into this. State Changed From-To: feedback->closed The submitter cannot test this anymore. As many many releases have passed, I think this PR can be closed. |
dhclient seems to have two odd bugs: 1) the broadcast address applied to the interface, if not specified by the DHCP server, is wrong - on this /24 it gets a.b.c.0 instead of a.b.c.255 2) the "domain" specified by the DHCP server somehow gets "\000" (four characters, NOT a literal null) appended to it before dhclient-script uses it to build /etc/resolv.conf. Fix: Unknown. How-To-Repeat: run dhclient with a DHCP server that doesn't supply broadcast address. (Not sure what triggers the "\000" feature.)