We've added two lines for the 192.168.3.0 subnet, the lines are: /opt/ltsp/i386 192.168.3.0/255.255.255.0(ro, no_root_squash) var/opt/ltsp/swapfiles 192.168.3.0/255.255.255.0(rw, no_root_squash)
Thanks again, Maria -----Ursprungligt meddelande----- Från: rob apodaca [mailto:[EMAIL PROTECTED]] Skickat: den 16 augusti 2002 07:44 Till: Maria Backlund Kopia: [EMAIL PROTECTED] Ämne: Re: [Ltsp-discuss] Unable to route mount request? On Fri, 16 Aug 2002 11:12:43 +0200 "Maria Backlund" <[EMAIL PROTECTED]> wrote: > Hi there! > > We've built a network using RedHat 7.2 combinded with LTSP. We've > tried two different structures but only one of them works and we > wonder why. The first, working structure is: > > 192.168.2.2 (client1) > | > 192.168.2.1 / 192.168.1.10 (server1) > | > 192.168.1.20 / 192.168.0.20 (gateway) > | > Hub - 192.168.0.10 (server2) > | > 192.168.0.11 (client2) > > Client2 boots and loads the kernel from server2 and then sends out a > mountrequest and mounts from server1. Everything works fine! > > We would like to have this structure though, and have tried it: > > 192.168.2.2 (client1) > | > 192.168.2.1 / 192.168.1.10 (server1) > | > 192.168.1.20 / 192.168.0.20 (gateway) > | > 192.168.0.10 / 192.168.3.1 (server2) > | > 192.168.3.2 (client2) > > Client2 boots and loads the kernel from server2 and then sends the > mountrequest. This however, only reaches one of the interfaces on > server2 (192.168.3.1) and doesn't go any further. Thus, client2 is > unable to mount and remains waiting. At first we thought we had a > routing problem but if we let client2 mount from server2 then client2 > can both ping and run telnet from server1. Is routing of mount > requests different from routing of other packages? It seems strange > that server2 ( a linux terminal server) don't seem to route it but > that our freeBSD-gateway does in the first structure. Can anyone give > us a hint or some ideas/explanations? > > Thanks, Maria & Fredrik I am thinking it is not a routing problem (proven by your ability to ping and telnet from server1). Perhaps clients on 192.168.3.0 are not allowed to mount /opt/ltsp/i386. What does your /etc/exports file on server1 look like? ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _____________________________________________________________________ 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
