First off I love syslinux and it has worked flawless for us on the unix side of the realm. We're trying to use our ghost images within a dos netboot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba shares. From what I've read you can use the 'keeppxe' line and call the orrignal ip information recieved durning the pxe boot process? Is that correct, and if so how would I do that. If that is not the case and I can keep around universal pxe stack to load dhcp again so that it exhibts a vendor code, how could I do that? Basicaly I need a way to map a samba share after the netboot, and I would need an ip address on the network to do that. This would be an automated process so I cant just enter a static... has to be a dhcp enabled one, or one handed from the pxe process...
Jonathan Hurd wrote:> First off I love syslinux and it has worked flawless for us on the unix side of the realm. > > > We're trying to use our ghost images within a dos netboot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba shares. From what I've read you can use the 'keeppxe' line and call the orrignal ip information recieved durning the pxe boot process? Is that correct, and if so how would I do that. > > > If that is not the case and I can keep around universal pxe stack to load dhcp again so that it exhibts a vendor code, how could I do that? > > Basicaly I need a way to map a samba share after the netboot, and I would need an ip address on the network to do that. This would be an automated process so I cant just enter a static... has to be a dhcp enabled one, or one handed from the pxe process... > _______________________________________________ > SYSLINUX mailing list > Submissions to SYSLINUX at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > > >Use the keeppxe option in the boot stanza, and then use an UNDI driver for your networking in DOS. Like it says in the documentation. example pxelinux.cfg file --snip default nasty-dos-hack label nasty-dos-hack kernel memdisk append initrd=my.img.gz keeppxe --unsnip you'll need to fix-up your net/protocol.ini and net/system.ini We call \net\net.exe init /dynamic etc from autoexec.bat in the image and it picks up the (followed by \net\netbind.com) We're using the 3com UNDI driver, which can be lifted from the 3com MBA utility disks found at ftp://ftp.3com.com/pub/nic/3c90x/util430.exe. Note this doesn't restrict you to using 3com network cards, it works with any PXE-capable card that we've tried. HTH -- ian
Jonathan Hurd wrote:> First off I love syslinux and it has worked flawless for us on the unix side of the realm. > > > We're trying to use our ghost images within a dos netboot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba shares. From what I've read you can use the 'keeppxe' line and call the orrignal ip information recieved durning the pxe boot process? Is that correct, and if so how would I do that. > > > If that is not the case and I can keep around universal pxe stack to load dhcp again so that it exhibts a vendor code, how could I do that? > > Basicaly I need a way to map a samba share after the netboot, and I would need an ip address on the network to do that. This would be an automated process so I cant just enter a static... has to be a dhcp enabled one, or one handed from the pxe process...Ultimately this is a question about the DOS networking stack you're using, not about SYSLINUX, which makes it difficult to answer. With the "keeppxe" option, syslinux will keep the PXE stack loaded (it eats up a LOT of low memory, however.) If you're using MEMDISK, an alternative is to specify "ipappend 1" and then use the MEMDISK query API to get the ip= line from the memdisk saved command line. The keeppxe option has the advantage that you can use an UNDI driver in DOS, which means your networking is hardware-independent... as long as you're willing to lose 64-128K of DOS memory. -hpa
Yeah ghost works fine in dos as far as imaging a host. It's just I want to
ghost the client from an image file located on a samba host. To do that I need
IP connectivity.
And yes I've look at G4U and definitly want to try it out in the near
future, but need to get something up interim.
----- Original Message ----
From: Michael D. Setzer II <mikes at kuentos.guam.net>
To: Jonathan Hurd <texasjhurd at yahoo.com>
Sent: Friday, December 14, 2007 4:01:50 PM
Subject: Re: [syslinux] KEEPPXE/DOS
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Unfortunately, I don't know anything about the kepppxedos, but do have a
question of what you are trying to do? I assume that you are talking about a
Norton Ghos Image, and that is the reference to DOS.
I've used Notron in the past, but it failed to work with the later LVM
partitions, so I had to find a program that supported my lab setups. I found
that g4u worked fine, and later g4l also worked. G4U is netbsd bassed, and
g4l is linux based. Both use dd with compression and ftp to make and
restore images. G4L also includes NTFSCLONE for doing a faster copy of
the ntfs partition data. Niether program does on the fly resizing like Norton,
but do work with LVM and other partition types, and don't have the expense
of having to buy a license for each machine or getting a site license. My
college has a site license an older Norton Ghost, but didn't get any support
from them with the LVM failures.
Hopefully, you will get a response that works for your current setup, but if
not, you might want to look at other options. Also, udpcast is a program if
you want to image lots of machines at once.
On 14 Dec 2007 at 13:02, Jonathan Hurd wrote:
Date sent: Fri, 14 Dec 2007 13:02:43 -0800 (PST)
From: Jonathan Hurd <texasjhurd at yahoo.com>
To: syslinux at zytor.com
Subject: [syslinux] KEEPPXE/DOS
Send reply to: For discussion of SYSLINUX and tftp-hpa
<syslinux at zytor.com>
<mailto:syslinux-
request at zytor.com?subject=unsubscribe>
<mailto:syslinux-
request at zytor.com?subject=subscribe>
> First off I love syslinux and it has worked flawless for us on the unix
side of the realm.
>
>
> We're trying to use our ghost images within a dos netboot using
syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a
vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS
does not, so we cannot request a second IP after the pxe process to map samba
shares. From what I've read you can use the 'keeppxe' line and call
the orrignal ip information recieved durning the pxe boot process? Is that
correct, and if so how would I do that.
>
>
> If that is not the case and I can keep around universal pxe stack to load
dhcp again so that it exhibts a vendor code, how could I do that?
>
> Basicaly I need a way to map a samba share after the netboot, and I would
need an ip address on the network to do that. This would be an automated process
so I cant just enter a static... has to be a dhcp enabled one, or one handed
from the pxe process...
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
+----------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor
Guam Community College Computer Center
mailto:mikes at kuentos.guam.net
mailto:msetzerii at gmail.com
http://www.guam.net/home/mikes
Guam - Where America's Day Begins
+----------------------------------------------------------+
http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
BOINC at HOME CREDITS
SETI 4,244,741.524738 | EINSTEIN 1,285,697.675406 | ROSETTA
321,713.518155
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8 -- QDPGP 2.61c
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBR2JwsCzGQcr/2AKZEQJhqACfSCgJus49ae1tXcg3WtlKlpZNbIEAoPhQ
DCk8k/Tz97Ho1C4tjR+UDKPI
=rpV/
-----END PGP SIGNATURE-----
Thanks HPA, this is where I was getting at... First am I going in the right direction? I can only get an IP in two ways for the client to boot up a samba share. One, if I somehow grab the IP from pxe process through a memdisk query.Two, if I make a second DHCP request. Option two according to security standards will only work if I can provide some sort of DHCP identifer for those clients. Being that this is DOS, I dont think there is any single identifer to point it out from anything else (correct me if I'm wrong, and I could not find anything in the DHCP packets for dhcpd.conf to work with). So that really only leaves me with option 1. Can you explain how I would do a memdisk query to retrieve the IP (if possible with /dos), Subnet Mask, and GW from the pxeprocess. Your also telling me that there is no reason use the keeppxe line, that is only to keep the undi driver around. Instead I would use "ipappend 1"?? Like this? MENU Ghost KERNEL memdisk APPEND ipappend1 initrd=MSDOS.IMG Thanks ----- Original Message ---- From: H. Peter Anvin <hpa at zytor.com> To: For discussion of SYSLINUX and tftp-hpa <syslinux at zytor.com> Sent: Friday, December 14, 2007 4:12:33 PM Subject: Re: [syslinux] KEEPPXE/DOS Jonathan Hurd wrote:> First off I love syslinux and it has worked flawless for us on the unix side of the realm. > > > We're trying to use our ghost images within a dos netboot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba shares. From what I've read you can use the 'keeppxe' line and call the orrignal ip information recieved durning the pxe boot process? Is that correct, and if so how would I do that. > > > If that is not the case and I can keep around universal pxe stack to load dhcp again so that it exhibts a vendor code, how could I do that? > > Basicaly I need a way to map a samba share after the netboot, and I would need an ip address on the network to do that. This would be an automated process so I cant just enter a static... has to be a dhcp enabled one, or one handed from the pxe process...Ultimately this is a question about the DOS networking stack you're using, not about SYSLINUX, which makes it difficult to answer. With the "keeppxe" option, syslinux will keep the PXE stack loaded (it eats up a LOT of low memory, however.) If you're using MEMDISK, an alternative is to specify "ipappend 1" and then use the MEMDISK query API to get the ip= line from the memdisk saved command line. The keeppxe option has the advantage that you can use an UNDI driver in DOS, which means your networking is hardware-independent... as long as you're willing to lose 64-128K of DOS memory. -hpa _______________________________________________ SYSLINUX mailing list Submissions to SYSLINUX at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.
Err after reading up on the options the syslinux command line would be Menu Ghost KERNEL memdisk APPEND initrd=MSDOS.IMG IPAPPEND 1 and the ouput if quered would be: ip=<client-ip>:<boot-server-ip>:<gw-ip>:<netmask> ?? how could I query that information in PCDOS7, sorry if this is out of the scope of this group. ----- Original Message ---- From: Jonathan Hurd <texasjhurd at yahoo.com> To: For discussion of SYSLINUX and tftp-hpa <syslinux at zytor.com> Sent: Monday, December 17, 2007 8:56:09 AM Subject: Re: [syslinux] KEEPPXE/DOS Thanks HPA, this is where I was getting at... First am I going in the right direction? I can only get an IP in two ways for the client to boot up a samba share. One, if I somehow grab the IP from pxe process through a memdisk query.Two, if I make a second DHCP request. Option two according to security standards will only work if I can provide some sort of DHCP identifer for those clients. Being that this is DOS, I dont think there is any single identifer to point it out from anything else (correct me if I'm wrong, and I could not find anything in the DHCP packets for dhcpd.conf to work with). So that really only leaves me with option 1. Can you explain how I would do a memdisk query to retrieve the IP (if possible with /dos), Subnet Mask, and GW from the pxeprocess. Your also telling me that there is no reason use the keeppxe line, that is only to keep the undi driver around. Instead I would use "ipappend 1"?? Like this? MENU Ghost KERNEL memdisk APPEND ipappend1 initrd=MSDOS.IMG Thanks ----- Original Message ---- From: H. Peter Anvin <hpa at zytor.com> To: For discussion of SYSLINUX and tftp-hpa <syslinux at zytor.com> Sent: Friday, December 14, 2007 4:12:33 PM Subject: Re: [syslinux] KEEPPXE/DOS Jonathan Hurd wrote:> First off I love syslinux and it has worked flawless for us on the unix side of the realm. > > > We're trying to use our ghost images within a dos netboot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba shares. From what I've read you can use the 'keeppxe' line and call the orrignal ip information recieved durning the pxe boot process? Is that correct, and if so how would I do that. > > > If that is not the case and I can keep around universal pxe stack to load dhcp again so that it exhibts a vendor code, how could I do that? > > Basicaly I need a way to map a samba share after the netboot, and I would need an ip address on the network to do that. This would be an automated process so I cant just enter a static... has to be a dhcp enabled one, or one handed from the pxe process...Ultimately this is a question about the DOS networking stack you're using, not about SYSLINUX, which makes it difficult to answer. With the "keeppxe" option, syslinux will keep the PXE stack loaded (it eats up a LOT of low memory, however.) If you're using MEMDISK, an alternative is to specify "ipappend 1" and then use the MEMDISK query API to get the ip= line from the memdisk saved command line. The keeppxe option has the advantage that you can use an UNDI driver in DOS, which means your networking is hardware-independent... as long as you're willing to lose 64-128K of DOS memory. -hpa _______________________________________________ SYSLINUX mailing list Submissions to SYSLINUX at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.
Jonathan Hurd wrote:> Err after reading up on the options the syslinux command line would be > > Menu Ghost > KERNEL memdisk > APPEND initrd=MSDOS.IMG > IPAPPEND 1 > > and the ouput if quered would be: ip=<client-ip>:<boot-server-ip>:<gw-ip>:<netmask> ?? > > how could I query that information in PCDOS7, sorry if this is out of the scope of this group. >Definitely out of scope for *me*. -hpa
Has anyone gotten this to work? Loading the PXE UNDI driver so that it will spit out a vendor code durning the DHCP Discover? Everytime I try to do the following: 'you'll need to fix-up your net/protocol.ini and net/system.ini 'We call \net\net.exe init /dynamic etc from autoexec.bat in the image 'and it picks up the (followed by \net\netbind.com) it causes my system to reboot, guessing memory issues. ----- Original Message ---- From: Ian McDonald <iam at st-andrews.ac.uk> To: For discussion of SYSLINUX and tftp-hpa <syslinux at zytor.com> Sent: Friday, December 14, 2007 3:50:20 PM Subject: Re: [syslinux] KEEPPXE/DOS Jonathan Hurd wrote:> First off I love syslinux and it has worked flawless for us on the unix side of the realm. > > > We're trying to use our ghost images within a dos netboot using syslinux. Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code 'like windows/pxe/and other os's do". Unfortunatly DOS does not, so we cannot request a second IP after the pxe process to map samba shares. From what I've read you can use the 'keeppxe' line and call the orrignal ip information recieved durning the pxe boot process? Is that correct, and if so how would I do that. > > > If that is not the case and I can keep around universal pxe stack to load dhcp again so that it exhibts a vendor code, how could I do that? > > Basicaly I need a way to map a samba share after the netboot, and I would need an ip address on the network to do that. This would be an automated process so I cant just enter a static... has to be a dhcp enabled one, or one handed from the pxe process... > _______________________________________________ > SYSLINUX mailing list > Submissions to SYSLINUX at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > > >Use the keeppxe option in the boot stanza, and then use an UNDI driver for your networking in DOS. Like it says in the documentation. example pxelinux.cfg file --snip default nasty-dos-hack label nasty-dos-hack kernel memdisk append initrd=my.img.gz keeppxe --unsnip you'll need to fix-up your net/protocol.ini and net/system.ini We call \net\net.exe init /dynamic etc from autoexec.bat in the image and it picks up the (followed by \net\netbind.com) We're using the 3com UNDI driver, which can be lifted from the 3com MBA utility disks found at ftp://ftp.3com.com/pub/nic/3c90x/util430.exe. Note this doesn't restrict you to using 3com network cards, it works with any PXE-capable card that we've tried. HTH -- ian _______________________________________________ SYSLINUX mailing list Submissions to SYSLINUX at zytor.com Unsubscribe or set options at: http://www.zytor.com/mailman/listinfo/syslinux Please do not send private replies to mailing list traffic.
Hi Peter, yes that is correct. I am trying to load ghost under dos or any other
format.
I have no problem creating the disks so far, I can load the correct drivers
fine. The problem is when the client makes the second dhcp request it sends out
a DHCP discover packet to the DHCP server. Due to our security protocols we have
to somehow set a identifer in our dhcpd.conf to set aside this boot process from
any others. The easiest way is to use the DHCP Discover Option 60 Vendor Code
Identifer. Unfortunatly all the DOS network stacks that I've looked at
don't send out this identifer.
So really I need a way to either hack the dhcp process to output a vendor code,
or find one that will push out some kind of identifer that I can use in the
dhcpd.conf.
Currently I am using 'keeppxe' and the 3com undi driver.
----- Original Message ----
From: "Peter.Leenders at computacenter.com" <Peter.Leenders at
computacenter.com>
To: syslinux at zytor.com
Sent: Tuesday, December 18, 2007 2:56:30 AM
Subject: Re: [syslinux] KEEPPXE/DOS
Hello Jonathan,
what is your problem? As far as I suspect, you want to start via Ghost
under DOS with networksupport to store image files on the network.
A normal diskette may to small to get all your software on it. there
are to solutions to this:
* A simple solution will be to extend with winimage a pxe bootfloppy
from 1.4MB to 2.8MB and copy the ghost files to the bootimage. You
can use your normal bootfloppy as base for this (and do not use the
keeppxe option).
* The other solution will be to start ghost directly from the network
- you may need it anyway to store your image files
For multiple networkcard support under dos there are a lot of different
solutions, e.g. these 3 ones:
* If you want to autodetect your network card you can use tools like
nicfind from Shane Kent you just have to evaluate the %nicnum%
variable after starting nicfind.
* or use as a complete solution barts network bootdisk (based on the
modboot disk - a tricky solution).
These two solutions have to be adept to every different nic you use
and dos drivers must exist (not for e.gsome sis-nics). Also there are
some nics with bootix firmware that crash the nicfind autodection
(don't if this also occurs with barts network bootdisk).
* The third solution will be to use the keeppxe option. This solution
has the charm that your boot disk will get hardware independent
(if this leaves enought lower dos memory for ghost). Undi drivers
are only availible for MS-Net clients, other solutions like netware
clients are tricky but possible (you have to use shims for this).
Remark:
Keep in mind that, if you use himem in config.sys, that the testmem option
is set to off (otherwise your bootimage in memory may be corrupted by
himem).
Links:
Bart'sNetwork bootdisk from Bart Lagerweij:
http://www.nu2.nu/bootdisk/network/
http://www.nu2.nu/bootdisk/modboot/
http://www.nu2.nu/bootdisk/network/makedisk-old/
Nicfind from Shane Kent:
http://www.pcworld.com/downloads/file/fid,60471-order,3-page,1-c,lanutilities/description.html
Peter Leenders
This email is confidential. If you are not the intended recipient, you must
not disclose or use the information contained in it. If you have received
this mail in error, please tell us immediately by return email and delete
the document.
Jonathan Hurd
<texasjhurd at yahoo
.com> To
Sent by: For discussion of SYSLINUX and
syslinux-bounces@ tftp-hpa <syslinux at zytor.com>
zytor.com cc
Subject
17.12.2007 22:12 Re: [syslinux] KEEPPXE/DOS
Please respond to
For discussion of
SYSLINUX and
tftp-hpa
<syslinux at zytor.c
om>
Has anyone gotten this to work? Loading the PXE UNDI driver so that it will
spit out a vendor code durning the DHCP Discover?
Everytime I try to do the following:
'you'll need to fix-up your net/protocol.ini and net/system.ini
'We call \net\net.exe init /dynamic etc from autoexec.bat in the image
'and it picks up the (followed by \net\netbind.com)
it causes my system to reboot, guessing memory issues.
----- Original Message ----
From: Ian McDonald <iam at st-andrews.ac.uk>
To: For discussion of SYSLINUX and tftp-hpa <syslinux at zytor.com>
Sent: Friday, December 14, 2007 3:50:20 PM
Subject: Re: [syslinux] KEEPPXE/DOS
Jonathan Hurd wrote:> First off I love syslinux and it has worked flawless for us on the unix
side of the realm.>
>
> We're trying to use our ghost images within a dos netboot using
syslinux.
Unfortunatly we can only pass DHCP ip's to hosts that exhibit a vendor code
'like windows/pxe/and other os's do". Unfortunatly DOS does not, so
we
cannot request a second IP after the pxe process to map samba shares. From
what I've read you can use the 'keeppxe' line and call the orrignal
ip
information recieved durning the pxe boot process? Is that correct, and if
so how would I do that.>
>
> If that is not the case and I can keep around universal pxe stack to load
dhcp again so that it exhibts a vendor code, how could I do
that?>
> Basicaly I need a way to map a samba share after the netboot, and I would
need an ip address on the network to do that. This would be an automated
process so I cant just enter a static... has to be a dhcp enabled one, or
one handed from the pxe process...> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>
>
Use the keeppxe option in the boot stanza, and then use an UNDI driver
for your networking in DOS. Like it says in the documentation.
example pxelinux.cfg file
--snip
default nasty-dos-hack
label nasty-dos-hack
kernel memdisk
append initrd=my.img.gz keeppxe
--unsnip
you'll need to fix-up your net/protocol.ini and net/system.ini
We call \net\net.exe init /dynamic etc from autoexec.bat in the image
and it picks up the (followed by \net\netbind.com)
We're using the 3com UNDI driver, which can be lifted from the 3com MBA
utility disks found at ftp://ftp.3com.com/pub/nic/3c90x/util430.exe.
Note this doesn't restrict you to using 3com network cards, it works
with any PXE-capable card that we've tried.
HTH
--
ian
_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.
_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.
_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.
Seemingly Similar Threads
- syslinux PXE boot version upgrade, network no longer working
- Current pxelinux always unloads undi driver
- Problem with Symantec's UNDI driver and PXELINUX
- keeppxe - documentation recommendation
- Syslinux 3.70 - BSS DOS boot says: "Could not find kernel Image: linux".