Thanks, Sudev...
I have no idea where the "101" came from and, on a
reboot of the client, it doesn't show up.?.
I tried removing the quotes, then the client will not
get as far and the card is not properly recognized.
It's interesting that these were placed upon
installation automatically with the quotes. I didn't
do it. RH9 identifies the card as a NE2000 clone which
is partially correct on the version of the card that
is in the server. However, the driver is different
from etherboot (rom-o-matic) and a ne2000 clone driver
will not boot card. Weird!
Regards,
Dana
--- Sudev Barar <[EMAIL PROTECTED]> wrote:
> On Wed, 2004-05-12 at 07:05, Dana Persells wrote:
> > I'm running rtl8039 on server and 1 client and a
> > 3com905 on the other client. Both clients are
> picking
> Earlier post: your dhcpd.conf showed:
>
> host ws001 {
> hardware ethernet 00:4F:49:00:1A:CB;
> fixed-address 192.168.0.102;
> filename
> "/lts/vmlinuz-2.4.24-ltsp-4";
> # option option-128 e4:45:74:68:00:00;
> #This is NOT a MAC address
> # option option-129 "NIC=ne IO=0x300";
> }
>
> If you are using rtl8039 in ws001 then the lines
> option128/129 should
> not have been commented out!!
> Secondly your output log is showing:
>
> May 11 19:24:32 DanaLinux dhcpd: DHCPREQUEST for
> 192.168.0.102 (192.168.0.101) from 00:4f:49:00:1a:cb
> via eth0
>
> What is 192.168.0.101?? Your server was 192.168.0.6
> ?? On my system the
> cycle of DHCPDISCOVER / OFFER / REQUEST / PACK is
> cycled through twice
> as is given below. And since the DHCP server is same
> as LTSP server the
> DISCOVERY and REQQUEST is done by 192.168.0.254.
> AFter this the host
> name is picked up from /etc/hosts file and then
> authentication mount
> starts:
>
> May 3 08:25:22 server dhcpd: DHCPDISCOVER from
> 00:80:48:2a:02:3f via
> eth0
> May 3 08:25:22 server dhcpd: DHCPOFFER on
> 192.168.0.123 to
> 00:80:48:2a:02:3f via eth0
> May 3 08:25:22 server dhcpd: DHCPREQUEST for
> 192.168.0.123
> (192.168.0.254) from 00:80:48:2a:02:3f via eth0
> May 3 08:25:22 server dhcpd: DHCPACK on
> 192.168.0.123 to
> 00:80:48:2a:02:3f via eth0
> May 3 08:25:29 server dhcpd: DHCPDISCOVER from
> 00:80:48:2a:02:3f via
> eth0
> May 3 08:25:29 server dhcpd: DHCPOFFER on
> 192.168.0.123 to
> 00:80:48:2a:02:3f via eth0
> May 3 08:25:31 server dhcpd: DHCPREQUEST for
> 192.168.0.123
> (192.168.0.254) from 00:80:48:2a:02:3f via eth0
> May 3 08:25:31 server dhcpd: DHCPACK on
> 192.168.0.123 to
> 00:80:48:2a:02:3f via eth0
> May 3 08:25:31 server rpc.mountd: authenticated
> mount request from
> ws123.ltsp:691 for /opt/ltsp/i386 (/opt/ltsp/i386)
> May 3 08:25:34 server rpc.mountd: authenticated
> mount request from
> ws123.ltsp:794 for /var/opt/ltsp/swapfiles
> (/var/opt/ltsp/swapfiles)
> May 3 08:25:34 server rpc.mountd: authenticated
> mount request from
> ws123.ltsp:804 for /usr/X11R6/lib/X11/fonts
> (/usr/X11R6/lib/X11/fonts)...
>
>
> So it seems that the DHCP is getting broken
> somewhere. Most likely due
> to option 128 / 129 not being passed on.
> I am trying to help and at the same time understand
> the whole process.
> De-mystifying a problem is best way to do so. Please
> do give a little
> slack if your feel I am way off here.
>
> --
> Sudev Barar
> Learning Linux
>
__________________________________
Do you Yahoo!?
Yahoo! Movies - Buy advance tickets for 'Shrek 2'
http://movies.yahoo.com/showtimes/movie?mid=1808405861
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
