Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I've just built a machine from old bits, with a hard drive so old that it can't take FC3, so I installed RH9 on it. I want to share a directory from the FC3 machine to the RH9 one. Both machines can ping each other, I have exported the directory I want to share on the FC3 machine; the /etc/exports file reads: /imports/4network 192.168.0.5(ro,insecure,sync)
The nfs daemon is running on the FC3 server.
When I try to mount the share directory on the RH9 client using mount lerebus:/imports/4network /mnt/network/
<lerebus is the FC3 machine name, assigned 192.168.0.2 in /etc/hosts file in the RH9 machine>
I get the error mount: RPC: Remote system error - No route to host
I've done a search for this on the net and it seems to be a firewall problem on the server. However, (a) all the solutions seem to deal with ipchains rather than iptables and (b) this firewall configuration stuff is all new to me and fairly unintelligible, so I don't know what to change to fix this problem and still keep the security tight.
rpcinfo -p on the RH9 client gives: program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 32768 status
391002 2 tcp 32768 sgi_fam
100011 1 udp 729 rquotad
100011 2 udp 729 rquotad
100011 1 tcp 732 rquotad
100011 2 tcp 732 rquotad
I agree, stoping firewall isn't a final solution ! The issue is that nfs uses sun-rpc which elects a dynamical port to transfer the files. So you cannot set up an iptables rule to match nfs... that's a typical connexion tracking issue. The link below explains hos to configure nfs so that it uses allways the same port, thus you'll be able to create a rule for it : http://www.lowth.com/LinWiz/nfs_help.html
as for the timeout, I see this error every time I try to mount through nfs a filesystem that's not accessible (not mounted on the nfs server, nfs server down...).
I propose that you:
_ check out that you wrote the right IP address in /etc/exports
_ check out that nfs-kernell-server and nfs-common run on the server (I believe that both are needed)
_ check out that there's not a firewall on the client side that would block nfs
OK thanks, I'm away at the moment but I'll give it a try once I'm back in a couple of days. Although I have a suspiscion that the article you linked to is one that lost me in jargon when I looked around for solutions before...not to worry, I'll have a crack at it
Is there an easier way to do what I'm trying to do? I'm pretty sure I read somewhere that linux is *the* system for networking - one of the reasons I thought I'd try to link the machines. To my simple mind (not kidding, very much a newbie) it seems anything but...I can get the linux machine talking to windows easier than to another linux box!
I had to stop both the client and server firewalls to get the mount command to work. Thanks for the suggestion, I had assumed stopping just the server firewall would be enough.
I had a look at the article at http://www.lowth.com/LinWiz/nfs_help.html. However, I'm not clear on which rules should be changed for which machine. Should both firewalls have all the changes implemented? Or should some changes be implemented for the server and others for the client? I had a look at the wizards linked from that page too, but still confused. Sorry, obviously security isn't my background! All help appreciated as always.