domain-search garbage in format string

[Shane Kerr]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Geoff,

This is the right forum. I've created a ticket about this issue that you'll be
CC'd on, which we'll get to shortly (unless you want to submit a patch). :)

Sorry about the slow response, but our huge DHCP team was all away for the holidays!

Kingsmill, Geoff wrote:
> Ted and Simon,
> Thanks for the responses. Is this forum sufficient for reporting the
> problem? If not then how do I report the problem so that this gets fixed?
> 
> Thanks,
> Geoff..
> 
> On Dec 22, 2006, at 3:14 PM, Kingsmill, Geoff wrote:
>> Can anyone provide any insight as to why this is failing?
> 
> Presumably 3.1.0a2 implements encoding format 'D' but not decoding  
> it.   Should be pretty easy to fix... :'}
> 
> -----Original Message-----
> From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On Behalf
> Of Simon Hobson
> Sent: Saturday, December 23, 2006 9:10 AM
> To: dhcp-users at isc.org
> Subject: Re: domain-search garbage in format string
> 
> Kingsmill, Geoff wrote:
>> I just tried to use the new dhcp option 119 (domain-search) feature in the
>> dhcp 3.1.0a2 kit.
>> Unfortunately I cannot get it to work. When I run dhclient I get the
> error:-
>> Domain-search: garbage in format string: D
>> Domain-search: 8 extra bytes
>>
>> A network trace shows the dhcp option 119 data as
>>
>> HEX-DATA:  77     08     02     68 70 03     63 6f 6d 00
>> FORMATTED: option 8bytes 2bytes h  p  3bytes c  o  m  end
>>            119    total
>>
>> If I have read RFC3397 correctly then this looks correct.
> 
> I agree, it looks right to me. That suggests a client bug.
> 
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFmkS5MsfZxBO4kbQRAkosAJ45lzeIiS9vLy704rL7w/+rRlrKwgCg5hkG
NSFtT0uBAjWRLCCO8c5PT2Y=
=E8f3
-----END PGP SIGNATURE-----