Mailing List Archive: syslinux: users

few question

Index | Next | Previous | View Threaded

pierre-yves.verdon at wanadooportails

Jan 14, 2002, 9:38 AM

Post #1 of 3 (990 views)
Permalink

few question

hi,
i'm wondering aboot the option "vendor-class identifier" what means
these two number? i have actually us it in my dhcpd.conf, and all is
working, but i don't know what it mean....
if substring (option vendor-class-identifier, 0, 3) = "PXE"

i have the same question for the "option vendor-encapsulated-options" ?

this is just because, i just read a ltsp pxe howto and that both of
these option have different parameter

for example:
option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;

and I use:
option vendor-encapsulated-options
09:0f:80:00:0c:4e:65:74:77:6f:72:6b:20:62:6f:6f:74:0a:07:00:50:72:6f:6d:70:74:06:01:02:08:03:80:00:00:47:04:80:00:00:00:ff;

i suppose the vendor-encapsulated-options identify the network device,
am i right?

http://www.ltsp.org/documentation/pxe.howto.html

--
pierre-yves

giulioo at pobox

Jan 14, 2002, 10:24 AM

Post #2 of 3 (916 views)
Permalink

few question [In reply to]

On Mon, 14 Jan 2002 17:51:08 +0100, you wrote:

>working, but i don't know what it mean....
>if substring (option vendor-class-identifier, 0, 3) = "PXE"
vendor-class-identifier is something the client will tell the server.
pxe clients tell the server "PXEClient" (ie they set vendor-class-identifier
= PXEClient) meaning they are pxe clients.
Etherboot clients will set it to "Etherboot"

>i have the same question for the "option vendor-encapsulated-options" ?
This is something the server tell the client, and the client may be
programmmed to do something different depending on what it receives.

>for example:
>option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;
This is hex for "Etherboot", etherboot clients may be programmed to only
consider dhcp servers which use this id.

>option vendor-encapsulated-options
>09:0f:80:00:0c:4e:65:74:77:6f:72:6b:20:62:6f:6f:74:0a:07:00:50:72:6f:6d:70:74:06:01:02:08:03:80:00:00:47:04:80:00:00:00:ff;
This contains some ascii strings "..Network boot ... prompt"

See
http://www.geocrawler.com/archives/3/5299/2001/7/100/6129709/
for interesting examples on the use of the above parameters (this is for
etherboot users, and you usually won't need it if you use pxelinux, but it
shows how these parameters can be used).

Note that usually you can boot pxe clients with pxelinux without having to
use any of the above parameters.

--
giulioo [at] pobox

jsiemes at web

Jan 14, 2002, 11:01 AM

Post #3 of 3 (923 views)
Permalink

few question [In reply to]

Hi,

> >working, but i don't know what it mean....
> >if substring (option vendor-class-identifier, 0, 3) = "PXE"
> vendor-class-identifier is something the client will tell the server.
> pxe clients tell the server "PXEClient" (ie they set vendor-class-identifier
> = PXEClient) meaning they are pxe clients.
> Etherboot clients will set it to "Etherboot"

It used to identify the hardware, thus I've some entry "IBM-8364-TXX"
here, some other called "IBMNSM A.2.0". The first one is a
networkstation 2800, while the latter one is a networkstation 1000.

> >i have the same question for the "option vendor-encapsulated-options" ?
> This is something the server tell the client, and the client may be
> programmmed to do something different depending on what it receives.
>
> >for example:
> >option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;
> This is hex for "Etherboot", etherboot clients may be programmed to only
> consider dhcp servers which use this id.

This used to be some extension for vendor-specific options. You can use
this option to send some vendor-defined options to the client. These
depend on the server _and_ the client, and were used before PXE was
born.

PXE defines the 'Vendor-class-identifier' to be 'PXEClient', followed
by options the server should negotiate. E.g. the UUID etc.pp. is sent
from the client to the server, and the server can react on these options.

Somewhere else (I think also in this option ...) the MTFTP options
(Multicast TFTP) are set.

So if you like to try something in these options: They're highly
Rom dependent, so one PXE Rom will support one while the other one
doesn't like this option at all (i.e. won't boot!). It can also
impact other (non-PXE) DHCP clients.

Usually you won't need any of these, despite the 'magic' string
found in the pxelinux documentation. This switches all MTFTP related
things off if your pxe rom really wants to talk MTFTP.

Regards,

Josef

________________________________________________________________
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr!
Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads