Hi there,
for our setup it would be nice to have pxelinux trying to load files like
/tftpboot/pxelinux.cfg/00:80:C8:6D:EE:7F instead of something like
/tftpboot/pxelinux.cfg/0A010708
The reason is, that with this setup I would be able to boot a machine in
different networks be means of dhcp and dynamic DNS updates.
I saw, in pxelinux.doc, that this is no Problem using ISC dhcp and doing
this on the server side in conjunction with the special syslinux dhcp
options.
Unfortunately our server DHCP Server runs on Win2k (I would rather have it
running on any Unix myself, but this is not an Option) so it won't work this
way.
I'm very bad in X86 assembly language. Where would I need to change the code
of pxelinux to achieve this?
Sven
--
"Das ist halt der Unterschied: Unix ist ein Betriebssystem mit Tradition,
die anderen sind einfach von sich aus unlogisch."
(Anselm Lingnau in de.comp.os.unix.discussion)
/me ist giggls at ircnet, http://geggus.net/sven/ im WWW
Hi, Sven Geggus <sven at geggus.net> schrieb am 11.04.02:> for our setup it would be nice to have pxelinux trying to load files like > /tftpboot/pxelinux.cfg/00:80:C8:6D:EE:7F instead of something like > /tftpboot/pxelinux.cfg/0A010708 > > The reason is, that with this setup I would be able to boot a machine in > different networks be means of dhcp and dynamic DNS updates. > > I saw, in pxelinux.doc, that this is no Problem using ISC dhcp and doing > this on the server side in conjunction with the special syslinux dhcp > options. > > Unfortunately our server DHCP Server runs on Win2k (I would rather have it > running on any Unix myself, but this is not an Option) so it won't work this > way. > > I'm very bad in X86 assembly language. Where would I need to change the code > of pxelinux to achieve this?I don't think that you need to change anything. I did the thing with the special dhcp options with an AIX dhcp server, and I think that you can also give special DHCP options to the W2K-dhcp server. Try giving these options to the server, and do a tcpdump to know if it gives these to the client. BTW, this would give one DHCP entry for every client, but you already knew that. Regards, Josef ________________________________________________________________ Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13
Hello *, exactly for this purpose we has made some minor changes in the PXELINUX code. I think also that the MAC address should be the determining client property. Additional it is possible with this modification to put further config files in the client directory. The structur would look like this: /tftpboot/clients/00-80-C8-6D-EE-7F/pxelinux.cfg Before the file pxelinux.cfg is downloaded, another small file is downloaded with only one number in it. This file decides whether the computer is booting by network or by the fixed disk. This file is called client.dat: /tftpboot/clients/00-80-C8-6D-EE-7F/client.dat Is the number smaller than 3 or exact 3, the computer is booting by the network. The File pxelinux.cfg is downloaded and is executed. With a number more largely than 3, the computer is booting by hard disk. The file pxelinux.cfg would be the same like 0A010708... I like PXELINUX very much and I would be pleased if this into the code would flow. All further functionality was preserved and should to be functioned as used. /robert -- ----------------------------------------------------------------- Dipl.-Ing.(FH) Robert Stoo? - phone: +49-30-20631-621 ASDIS Software AG Neue Gr?nstra?e 25 D-10179 Berlin Germany http://www.asdis.de/ ---------------- mailto:RStooss at asdis.de --- -------------- next part -------------- A non-text attachment was scrubbed... Name: Pxelinux.zip Type: application/x-zip-compressed Size: 42059 bytes Desc: not available URL: <http://www.zytor.com/pipermail/syslinux/attachments/20020416/2fee110d/attachment.bin>