[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dhcp-client
Subject:    evaluating extended tags
From:       "Sascha Juch" <Juch () sepago ! de>
Date:       2004-08-02 11:50:20
Message-ID: 75FBAF4B06609F4BB994B92502E964EA07FEDA () dc03 ! sepago ! de
[Download RAW message or body]

   *** From dhcp-client -- To unsubscribe, see the end of this message. ***

Hello list members,
I have a problem to evaluate extended tags within dhclient-script.

I set them in the DHCP-Server via
option loc_160 code 160 = text;

and within the host declaration with
option loc_160 "valuefor160";

In dhclient.conf I set 
request loc_160;

When in the context of dhclient-script, I can see via 
echo `env` > /tmp/envs
that the extended vars have been transmitted from the dhcp-Server and
set with correct values
They are named $new_#<no>, e.g. $new_#160 for the extended tag 160.

Now my question is how I can access them? I tried it with $new_#160,
$new_\#160, ${new_#160} but none of them worked.

I know this is more of an shell issue but I couldn't find examples on
vars named with an "#" in them.

Has anybody successfully got the values from extended tags?

Or is there a way to tell the client to name them different - e.g.
$new_160?

Many thanks in advance,
Sascha.



-----------------------------------------------------------------------
To unsubscribe from this list, visit http://www.isc.org/dhcp-lists.html
or send mail to dhcp-client-request@isc.org with the subject line of
'unsubscribe'.
-----------------------------------------------------------------------

[prev in list] [next in list] [prev in thread] [next in thread]