Hi Jim,
Thanks for your concern,
Actually this message does not exist anymore. It was when I used 2 IPs
addresses on the same ethernet namely
eth1: 192.168.1.1
eth1:0 192.168.0.1
I wanted to make sure the error did not come from the 2 ip addresses and now
everything goes on eth1 that is 192.168.1.1 and the actual messages are:
Looking up port of RPC 100003/2 on 192.168.1.1
Looking up port of RPC 100005/1 on 192.168.1.1
VFS: Mounted Root (NFS filesystem)
Freeing unused kernel memory: 56k freed
nfs: Server 192.168.0.1 not responding, timed out
nfs: Server 192.168.0.1 not responding, still trying
Here is my dhcp.conf file, although i am not sure it goes till it reads it:
[Default]
# SERVER = 192.168.0.254
SERVER = 192.168.1.1
XSERVER = XF86_SVGA
X_MOUSE_PROTOCOL = "PS/2"
X_MOUSE_DEVICE = "/dev/psaux"
X_MOUSE_RESOLUTION = 400
X_MOUSE_BUTTONS = 3
USE_XFS = N
LOCAL_APPS = N
LOCAL_WM = N
# UI_MODE = GUI
UI_MODE = SHELL
RUNLEVEL = 3
Thanks for helping me
Cheers
Jacques
Jim McQuillan wrote:
>
> Jacques,
>
> I'm interested in the warning message about 'Gateway not on directly
> connected network'.
>
> I'd like to see your dhcpd.conf file, to see how you've configured it.
>
> Thanks,
>
> Jim McQuillan
> [EMAIL PROTECTED]
>
> Jacques B. Siboni wrote:
>
> >Hi,
> >
> >I am coming back with the (nearly) same question. I did not receive any hint
> >from it.
> >
> >But the things are a bit more pure.
> >
> >>I have installed the ltsp package on a linux box running redhat 7.0
> >>
> >>I built an etherboot diskette on one machine.
> >>
> >
> >It boots ok till after the root file system is mounted.
> >When I check the rpcdump it says nfs detects some directories
> >but then nfs does not respond.
> >
> >
> >
> >Last messages associated with boot on the client machine are:
> >
> >IP-Config: Gateway not on directly connected network
> >Looking up port of RPC 100003/2 on 192.168.0.1
> >Looking up port of RPC 100005/1 on 192.168.0.1
> >VFS: Mounted Root (NFS filesystem)
> >nfs: Server 192.168.0.1 not responding, time out
> >nfs: Server 192.168.0.1 not responding, still trying
> >
> >here are some logs of the tcpdump: sorry it is not easy to read, but i see
> >there are access to "dev", then "console", then "init"
> >and then nothing more.
> >
> >What do you think, could it be a problem with the init code?
> >
> >I'd really appreciate some help as I really don't know what to do now.
> >
> >Am I the only one with this problem?
> >
> >BTW I have just updated to kernel 2.2.19-7.0.8. I thought it could help, but
> >it did'nt.
> >
> >I hope someone can give me some hints or, if not, where to look at
> >
> >Thanks in advance
> >
> >Jacques
> >
> >
> >
> >18:29:16.100255 > 192.168.1.1.2049 > 192.168.1.3.62922340: reply ok 96 getattr
> >DIR 40755 ids 0/0 sz 1024 (ttl 64, id 45914)
> >18:29:16.101090 < 192.168.1.3.79699556 > 192.168.1.1.2049: 100 statfs fh
> >Unknown/1 (ttl 64, id 6)
> >18:29:16.102182 > 192.168.1.1.2049 > 192.168.1.3.79699556: reply ok 48 statfs
> >tsize 8192 bsize 1024 blocks 1740759 bfree 877710 bavail 787746 (ttl 64, id
> >45915)
> >18:29:16.103048 < 192.168.1.3.96476772 > 192.168.1.1.2049: 108 lookup fh
> >Unknown/1 "dev" (ttl 64, id 7)
> >18:29:16.144391 > 192.168.1.1.2049 > 192.168.1.3.96476772: reply ok 128 lookup
> >fh Unknown/1 DIR 40755 ids 0/0 sz 1024 nlink 3 rdev ffffffff fsid 804 nodeid
> >1a933 a/m/ctime 1000702682.000000 [|nfs] (ttl 64, id 45916)
> >18:29:16.145268 < 192.168.1.3.113253988 > 192.168.1.1.2049: 112 lookup fh
> >Unknown/1 "console" (ttl 64, id 8)
> >18:29:16.155726 > 192.168.1.1.2049 > 192.168.1.3.113253988: reply ok 128
> >lookup fh Unknown/1 CHR 20644 ids 0/0 sz 0 nlink 1 rdev 400 fsid 804 nodeid
> >1a937 a/m/ctime 1000673220.000000 [|nfs] (ttl 64, id 45917)
> >18:29:16.156730 < 192.168.1.3.130031204 > 192.168.1.1.2049: 108 lookup fh
> >Unknown/1 [|nfs] (ttl 64, id 9)
> >18:29:16.157497 > 192.168.1.1.2049 > 192.168.1.3.130031204: reply ok 128
> >lookup fh Unknown/1 DIR 40755 ids 0/0 sz 1024 nlink 2 rdev ffffffff fsid 804
> >nodeid 40002 a/m/ctime 1000702682.000000 [|nfs] (ttl 64, id 45918)
> >18:29:16.158346 < 192.168.1.3.146808420 > 192.168.1.1.2049: 108 lookup fh
> >Unknown/1 "init" (ttl 64, id 10)
> >18:29:16.182219 > 192.168.1.1.2049 > 192.168.1.3.146808420: reply ok 128
> >lookup fh Unknown/1 REG 100755 ids 0/0 sz 27452 nlink 1 rdev ffffffff fsid 804
> >nodeid 40037 a/m/ctime 1000693919.000000 [|nfs] (ttl 64, id 45919)
> >18:29:16.183154 < 192.168.1.3.163585636 > 192.168.1.1.2049: 112 read fh
> >Unknown/1 4096 bytes @ 0 (ttl 64, id 11)
> >18:29:16.877818 < 192.168.1.3.163585636 > 192.168.1.1.2049: 112 read fh
> >Unknown/1 4096 bytes @ 0 (ttl 64, id 12)
> >18:29:18.277747 < 192.168.1.3.163585636 > 192.168.1.1.2049: 112 read fh
> >Unknown/1 4096 bytes @ 0 (ttl 64, id 13)
> >
> >
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax: 33 (0) 1 42 28 76 78
Home Page: http://www.lutecium.org/jacsib/
_____________________________________________________________________
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
