> Date: Mon, 20 May 2002 16:53:38 -0700
> From: "Jesse Scott" <[EMAIL PROTECTED]>
> Subject: NFS mount problems after changing networks
>
> The workstation machine boots, gets it's DHCP address (10.66.6.24),
> downloads the kernel with TFTP, does the second DHCP request
> successfully, and then the NFS mount fails. I already went through and
> changed the IP address and masks everywhere I could find:
> /etc/dhcpd.conf, /etc/exports, /etc/hosts.allow,
> /opt/ltsp/i386/etc/lts.conf, but it still refuses to mount:
>
> Running dhclient
> eth0: Setting Rx mode to 1 addresses.
> Mounting root filesystem: /opt/ltsp/i386 from: 10.66.3.12 (the correct
> IP of the server)
> (null)mount: nfsmount failed: Bad file number
> NFS: mount program didn't pass remote address!
> mount: Mounting 10.66.3.12:/opt/ltsp/i386 on /mnt failed: Invalid
> argument
>
> ERROR! Failed to mount the root directory via NFS!
> Possible reasons include:
Jesse,
At first, I thought maybe you forgot to re-export your NFS shares after
altering /etc/exports, but the output from 'showmount -e' proves that
the shares are correctly exported.
> Here are all the appropriate files I can think of, let me know if you
> need to see another one:
<snip>
> This brings up my DHCP issue, the above config warns me about the
> obvious conflict between the 10.0.0.0/255.0.0.0 and
> 10.66.6.24/255.255.255.248 subnets, but it seems to work and do what I
> want DHCP wise (only respond to DHCPREQUEST's for the IP's in the range
> I've been granted control over).
I am a bit confused by your dhcpd.conf file. I'm not sure why you
declare subnets the way you do. I'm not a DHCP ueberhacker, though, so
maybe it's just over my head. It looks like there is a campus-wide DHCP
service for your A-class network (10.*.*.*) and you're trying to avoid
stepping on its toes. This is the classical problem with an LTSP server
joining a network that already has a DHCP server...
There are really two problems:
1) Prevent LTSP clients from listening to the "other" DHCP server.
2) Prevent "normal" clients from listening to your LTSP DHCP server.
There've been some ideas on the ltsp-developer from Ken Yap which would
solve problem #1 by adding an option to the etherboot code that would
require the DHCP server to contain a string like DHCP_VCI=Etherboot-5.0
and he also suggests a temporary fix:
> Here's a lower tech approach which can be deployed right away. If
> DHCP_REJECT is defined in option 129 as the IP address of a server to
> ignore, then dhclient will not accept replies from it. So you would set
> it to the IP address of the rival DHCP server. This works with the
> dhclient in current LTSP initrds.
You seem to have solved problem #2 by using the 'not authoritative' option.
Am I understanding your situation correctly?
> /etc/hosts.allow:
> bootpd: 0.0.0.0
> in.tftpd: 10.66.6.
> portmap: 10.66.6.
This got me for a while... My copy of mountd was compiled with
tcp_wrappers support! You might need to put a line like this in
hosts.allow:
mountd: 10.66.6.
You might also want to check to make sure that ipchains/iptables (a.k.a.
firewalling) isn't blocking the packets. Also, any messages in
/var/log/messages when the client fails to mount?
Jason
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_____________________________________________________________________
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.openprojects.net
