| Summary: | DHCP hostname set as Hexadecimal string | ||
|---|---|---|---|
| Product: | Base System | Reporter: | satherrl <satherrl> |
| Component: | bin | Assignee: | Doug Barton <dougb> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 4.5-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
satherrl
2002-02-08 05:10:01 UTC
State Changed From-To: open->feedback I don't think this is necessary. The comment at the top of that file says that a value of 'X' means that the client will print in hex only if the hostname is non-printable ASCII characters. What value is the DHCP server trying to return to the client? It sounds like the DHCP server is sending a corrupted host name or something. Responsible Changed From-To: freebsd-bugs->murray I'm working on DHCP in FreeBSD. >The comment at the top of that file says that a value of 'X' means
>that the client will print in hex only if the hostname is
>non-printable ASCII characters. What value is the DHCP server trying
>to return to the client? It sounds like the DHCP server is sending a
>corrupted host name or something.
err - no.
its been a while but.
pretty_print_option() just picks out the X and dumps the line in XX:XX... :XX
format
write_client_lease() picks out the hostname and writes it via
pretty_print_option() - no check is done for its validity
the dhclient-script picks out the XX:XX:XX...XX hostname
a packet sniffer revealed a syntactically correct reply from both
dhcpd/FreeBSD and from an NT box
State Changed From-To: feedback->open I am no longer maintaining DHCP. Maybe this was fixed in 3.0.1? Responsible Changed From-To: murray->bugs I am no longer maintaining DHCP. Maybe this was fixed in 3.0.1? Responsible Changed From-To: bugs->freebsd-bugs Canonicalize assignment. State Changed From-To: open->closed 1. Old, unsupported FreeBSD version 2. Likely OBE Responsible Changed From-To: freebsd-bugs->dougb I closed it |