i think this is a common practice but not mandatory. Now, the client may
make this assumption and possibly ignore the dhcp option. If you want to
be sure that dhcp send the proper option, take a sniffer trace and see
if it is set properly
JeF
On Sun, 2003-02-02 at 08:04, Dave Watkins wrote:
> I c
I could be wrong but it is my understanding that the TFTP has to be the
same machine as the DHCP server. Certainly that is the onbly way I've ever
been able to get it working.
At 21:14 1/02/2003 +0100, [EMAIL PROTECTED] wrote:
hi all,
Am using dhcp3-server and have noticed that the 'next-server
Hi all,
am getting good at answering my own questions...
The autoconfig option is used so that you can PASS the kernel
info, and not for booting and starting a dhcp client, etc...
my mistake...
Used etherboot to get it working...
On Sat, Feb 01, 2003 at 05:53:43PM +0100, [EMAIL PROTECTED] wro
hi all,
Am using dhcp3-server and have noticed that the 'next-server'
option doesnt seem to work when booting of 3c905tx-m cards with
PXE or via their own mode with DHCP... it works however with
BOOTP.
have also tried 'server-name, and option tftp-server-name'...
For some reason the machine kee
I made a mistake in the kernel config
Have now got the kernel to boot, but it doesnt seem to want to
contact the bootp or dhcp server.
Any ideas?
Thanks
Andrew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi all,
Am trying to setup boot floppy so that I can boot via DHCP,
and mount the kernel via NFS.
Have compiled a 2.4.18 with 'autoconfigure IP' - DHCP enabled.
The kernel has NO modules.
Took a formated 3.5" disk, and then
dd if=bzImage of=/dev/fd0
mknod /dev/nfs c 0 255
rdev /dev/fd0 /dev/nfs
6 matches
Mail list logo
