Dhcp client issue

[Ed Greshko]

Philip A. Prindeville wrote:
> On 01/28/2010 01:27 PM, Ed Greshko wrote:
>   
>> Ed Greshko wrote:
>>   
>>     
>>> Philip A. Prindeville wrote:
>>>   
>>>
>>>     
>>>       
>>>> but when I try this, I get:
>>>>
>>>>
>>>> Jan 28 09:03:35 builder dhclient[25694]: /etc/dhcp/dhclient.conf line 4: expecting string or hexadecimal data.
>>>> Jan 28 09:03:35 builder dhclient[25694]: #011send dhcp-client-identifier hardware;
>>>> Jan 28 09:03:35 builder dhclient[25694]:                                      ^
>>>> Jan 28 09:03:35 builder dhclient[25694]: /etc/dhcp/dhclient.conf line 4: expecting a statement.
>>>> Jan 28 09:03:35 builder dhclient[25694]: #011send dhcp-client-identifier hardware;
>>>> Jan 28 09:03:35 builder dhclient[25694]:                                              ^
>>>> Jan 28 09:03:35 builder dhclient[25694]: /etc/dhcp/dhclient.conf line 5: semicolon expected.
>>>> Jan 28 09:03:35 builder dhclient[25694]: 
>>>> Jan 28 09:03:35 builder dhclient[25694]: ^
>>>> Jan 28 09:03:35 builder dhclient[25694]: /etc/dhcp/dhclient.conf line 5: unterminated interface declaration.
>>>> Jan 28 09:03:35 builder dhclient[25694]: 
>>>> Jan 28 09:03:35 builder dhclient[25694]: ^
>>>>
>>>>
>>>>
>>>> So it's not clear to me from the manual where you can have a dynamic
>>>> expression, and where you're required to have a literal.
>>>>
>>>>   
>>>>     
>>>>       
>>>>         
>>> If I have time later in the day I'll see if I can be helpful.
>>>
>>>   
>>>     
>>>       
>> I could not get back to sleep....
>>
>> Even though I didn't try the following as of yet, maybe you could?
>>
>> To make it easy to parse...maybe they are expecting a string to be
>> enclosed in quotes.  Have you tried....
>>
>> send dhcp-client-identifier "hardware" ;
>>
>>   
>>     
>
> Hardware is a keyword that evaluates to the MAC address of the interface
> the packet is being sent on:
>
>        hardware
>
>           The hardware operator returns a data string whose first  element  is
>           the  type of network interface indicated in packet being considered,
>           and whose subsequent elements are client’s link-layer address. [...]
>
>
> as I mentioned.  The problem being that it's accessible in some contexts, but not this one, apparently.
>
> So I don't want "hardware" as the string, I want:
>
> 01:XX:XX:XX:XX:XX:XX
>
> where XX:XX:XX:XX:XX:XX is the MAC address of eth0 (or whatever).
>
> Sorry if I didn't make that clear.
>
>   
No, it was finally clear.....  I just had some weird thought that
01:XX:XX:XX:XX:XX:XX and hardware are both "strings" and someone wrote a
lousy parser and would key off of "hardware" to do the right thing....

It was 5AM or there abouts when I wrote it...and only got up to give one
of my cats water.....  :-(

We'll see what the light of day brings....

-- 
Life is like an analogy.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20100129/caa45e19/attachment.bin