On Thu, Jun 16, 2005 at 01:37:12PM -0400, MW Mike Weiner (5028) wrote:
> On Thu, 16 Jun 2005, MW Mike Weiner (5028) wrote:
>
> > ...
> > filename "/tftp/pxelinux.0";
> > }
> >
> > My current /tftp (/tftpboot) tree looks like the following:
> > -rw-r--r-- 1 root root 2443013 Jun 16 09:56 initrd-fc2.img
> > drwxr-xr-x 2 root root 4096 Jun 16 10:28 ks
> > -rw-r--r-- 1 root root 12952 Jun 16 10:08 pxelinux.0
> > drwxr-xr-x 2 root root 4096 Jun 16 10:33 pxelinux.cfg
> > -rw-r--r-- 1 root root 1209805 Jun 16 09:56 vmlinuz-fc2
>
> If your tftp server is configured to serve files from the /tftp
> directory, you should have filename "pxelinux.0"
> --
>
> Michael -
>
> Thanks for your response, I made the change and tested it remotely using
> a tftp client and do see the pxelinux.0 there and can successfully grab
> it. Also tested the dhcpd to ensure it truly is working. That all works,
> so now to figure out why the client isnt being told or isnt listening to
> dhcpd when being instructed about the PXECLIENT stuff, as in the
> following:
>
> group {
> # option dhcp-class-identifier "PXEClient";
> next-server 10.10.232.54;
> filename "pxelinux.0";
> }
>
> But never seems to get that information nor tftp the bootloader.
For testing, just remove the 'group {' and matching '}'.
I just have the next-server and filename lines as the first two
in de dhcp conf file.
-Marcel
--
======-------- Marcel J.E. Mol MESA Consulting B.V.
=======--------- ph. +31-(0)6-54724868 P.O. Box 112
=======--------- marcel@xxxxxxx 2630 AC Nootdorp
__==== www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____
They couldn't think of a number, Linux user 1148 -- counter.li.org
so they gave me a name! -- Rupert Hine -- www.ruperthine.com
