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

Andreas Lundqvist writes:
 >     *** From dhcp-server -- To unsubscribe, see the end of this message. ***
 > 
 > Hi 
 > 
 > I just cant get the dhcpd.conf the right way and I was wondering if any
 > one could help me. I'm running dhcp-3.0-alpha-19990424 with bootp and dhcp
I've studied this for a problem we had. I'd used it with dhcpd-2.0pl6
and it worked great for me. I hope this helps you.

>From RFC2132 (8.4 Vendor Specific Information):
<RFC2132>
   If a vendor potentially encodes more than one item of information in
   this option, then the vendor SHOULD encode the option using
   "Encapsulated vendor-specific options" as described below:

   The Encapsulated vendor-specific options field SHOULD be encoded as a
   sequence of code/length/value fields of identical syntax to the DHCP
   options field with the following exceptions:

*snip*

   The code for this option is 43 and its minimum length is 1.

   Code   Len   Vendor-specific information
   +-----+-----+-----+-----+---
   |  43 |  n  |  i1 |  i2 | ...
   +-----+-----+-----+-----+---

   When encapsulated vendor-specific extensions are used, the
   information bytes 1-n have the following format:

    Code   Len   Data item        Code   Len   Data item       Code
   +-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
   |  T1 |  n  |  d1 |  d2 | ... |  T2 |  n  |  D1 |  D2 | ... | ... |
   +-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
</RFC2132>

Then as you send a vendor specific information you have to encode it
in such way.
Suppose that you have to send this vendor specific code to a DHCP client
(that it interprets in some way): 128
and that the parameters that you associate to this code (remember this 
codes are the only way to pass parameters "vendor specific" to the
client) are the string: "myparameters"
all you have to send via the vendor specific option is (in decimal):
          
                 m   y   p   a   r   a   m   e   t   e   r   s 
 43 14 128  12 109 121 112  97 114  97 109 101 116 101 114 115  

 ^   ^   ^   ^     Number of bytes composing the word "myparameters"
 |   |   |   |_____|
 |   |   |_________________ Code you have to send to the client (T1)
 |   |
 |   |___Total Length of the options \  You don't have to worry about
 |                                    } these two values. Ted had
 |_ DHCP Vendor Specific Option code /  thought for you =8^)

I've no experience in using dhcp-3.0-alpha-19990424 but I'm reading
the man page right now. 
It seems to me that in the case above you'd have to put in your dhcpd.conf 
this line:

option vendor-encapsulated-options
        80:0c:6d:79:70:61:72:61:6d:65:74:65:72:73;

i.e. 128,12,109,121,112,97,114,97,109,101,116,101,114,115 in hexadecimal

How this can help you?
Well. The dhcptab file is designed to specify in a formal way the vendor
specific options. As an example from your dhcptab file (I've cut some
to read better all):

SNCboot s Vendor=SUNW.PCNFS.5.1.1,12,ASCII,1,0

says that SNCboot is a symbol (i.e. you can put that with a value in
the subsequent lines of the file; SNCboot="/tftp/boot" )
that the client class allowed to receive this option are: SUNW.PCNFS.5.1.1
that the length of the data is:                           12
that the type of the data is:                             ASCII
that granyularity is (the times you can repeat that):     1
that the maximum number of repeatition are (0=nolimits):  0

In our case it would be:

marty  s Vendor=MartysPcClass,64,ASCII,1,0

allowing the symbol `marty' to contain a string of ascii characters of 
length of 60; later then in the file you'll have:

martyspcname m  :Include=default:marty="a very very very long string that it fits in a 
64 chars line":

I'm not explaining well this in wordds (because of my poor english
too) but if you lokk at the file you'll understand all.
You have to search through your dhcptab file to search the options you 
find useful for you and translate them. You'll find more infos on the
syntax of the dhcptab file typing this command:

man dhcptab

on your Sun box =8^). If that don't help you I'll make it to find out
the solution. Surely you have to know which options you need.

I'm not currently using  dhcp-3.0-alpha-19990424 and then I don't know 
exactly how it works, but fast reading the man page I'm sure that it
works very fine. There are some features which I don't know about.
I'll trying to figure out that. I think that Ted can give you some
hints on that.

I hope this helps
Best Regards
Antonio Maiorca

-- 
Antonio '[EMAIL PROTECTED]' Maiorca


------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED]   Please try to use the web
page first - it will take a long time for your request to be processed by hand.

Archives for this mailing list are available at 
http://www.webnology.com/list-archives/dhcp/dhcp-server

------------------------------------------------------------------------------

Reply via email to