On Tue, Jul 16, 2002 at 06:28:48AM -0700, Charles Griffin wrote:
After that, I thought I'd try the wireless orinoco card. Worked beautifully, also right out of the box! All I had to do was set up a second pcmcia nic in yast2. Works great!!!
Good news.
Here's my question, after my long-winded introduction: how do I set up a file-sharing network between my laptop and desktop considering that I have a wireless ap/router that assigns ip's via dhcp? I read the SuSE 8.0 manuals on this subject but they were not very informative.
I understand that I have to set up a NFS server on the desktop, designate which directories I want to share (which will only be my /home directory on the desktop), and then set up a NFS client on the laptop.
I tried doing this in Yast2 but was having some trouble. I think I got the NFS server set up ok, and designated the /home directory as the one to be shared. I wasn't sure what to put in the box about the wildcards, but...
The problem came in setting up the laptop. In the yast2 nfs client module, I let it browse the network to find the ip of the desktop, but instead it only listed the ip of the linksys ap/router (192.168.1.1) and the ip of the laptop, which was assigned 192.168.1.102 via dhcp. The desktop was assigned 192.168.1.100 via dhcp. When I tried manually entering that value in yast2, it hung. Also, in the box about which filesystem, is this where I put /home? Also, what happens if the ip of the desktop changes via dhcp? (e.g. I boot the laptop first which gets .100 -- now mounting /home in desktop configured at .100 will not work?)
For a server (NFS or otherwise), I strongly suggest that you give it a fixed IP address instead of using DHCP. If the IP changes, you will have to rely on DNS to resolve the name and you probably don't want the hassle of running an internal DNS for a couple of computers. So, just fix the IP at 192.168.1.100 on the server and put an entry in your client /etc/hosts file to map the server name to the it. It would help if you posted the contents of the /etc/exports file from your server. That shows what NFS is exporting to your network. You can restrict access by IP, network address, host, and other things. Also, make sure you don't have NFS firewalled on your server. For the client side, once the NFS client packages are installed, make sure portmap and rpc.statd are running. Then, to mount an NFS directory on the client, you can use: mount -t nfs servername:/exported-file-system /local-mount-point Now, the files on the remote system are accessible in /local-mount-point. Putting an entry in your /etc/fstab on the client makes is even easier to mount NFS shares. For example, here is an entry from my /etc/fstab for an NFS share on the host "slippery" which has exported /datacore: slippery:/datacore /mnt/slippery/datacore nfs noauto,user,exec,rsize=8192,wsize=8192,hard,intr 0 0 This is all ONE line (it is wrapped in e-mail due to length). The options after exec are for performance and safety. Now, I can mount it with just: mount /mnt/slippery/datacore Once all this is working, you'll be ready for the final frontier, automount! There are some tricky things to keep in mind regarding NFS security. Access rights through NFS are set up in the /etc/exports file on the NFS server. The rights determine who can mount the NFS file system and what they can do to files on the file system. However, it uses the UIDs of the user who mounts the share and NOT the user name. So, make sure the UIDs of your client users match the UIDs of the server users. The names don't matter, only the UID. A quick read of the NFS HOW-TO can help you with some of the trickier parts. Best Regards, Keith -- LPIC-2, MCSE, N+ Right behind you, I see the millions Got spam? Get spastic http://spastic.sourceforge.net