From: Benjamin Jeeves <benjamin@benjamin76.plus.com>
To: nfs@lists.sourceforge.net
Subject: Re: Help needed
Date: Wed, 4 May 2005 13:39:37 +0100 [thread overview]
Message-ID: <200505041339.37074.benjamin@benjamin76.plus.com> (raw)
In-Reply-To: <1115210110.10831.10.camel@lade.trondhjem.org>
Hi
Thank you I have thought of that option but was not sure if i should go down
that route but it does look like it now?
Thank you
On Wednesday 04 May 2005 13:35, Trond Myklebust wrote:
> on den 04.05.2005 Klokka 12:06 (+0100) skreiv Benjamin Jeeves:
> > Hi all
> >
> > This is the first time posting to this list so please understand if this
> > quistion has been posted before.
> >
> > I have one server with 4 ethernet card in all running on 192.168.1.*
> > network what i want to do is run nfs on.
> >
> > eth2 192.168.1.6 running nfs
> > eth3 192.168.1.7 running nfs
> >
> > eth2 would export samething like this /backup then /store.
> >
> > eth3 would export samething like this /folder3 /folder4
> >
> > but at this time all I can do is make it work on all of the ethernet
> > cards and only work on the first ethernet card eth0 for all requests.
> >
> > I have search gooogle and man pages but can not find anything or would I
> > need to do load balancing for this to work?
> >
> > I have tryed this in the /etc/exports file:
> > 192.168.1.6:/backup 192.168.1.12(rw,root_squash,sync)
> > 192.168.1.6:/store 192.168.1.12(rw,root_squash,sync)
> > 192.168.1.7:/folder3 192.168.1.14(rw,root_squash,sync)
> > 192.168.1.7:/folder4 192.168.1.14(rw,root_squash,sync)
>
> That sort of syntax is definitely not supported. NFS shouldn't have to
> know or care about how you want to organise your network.
>
> If you want to enforce no NFS traffic on eth0, then how about using
> iptables to block traffic to port 2049 on that interface?
>
> You might then add static routes to 192.168.1.12 and 192.168.1.14 and/or
> set up iptables rules on the server if you want to enforce which
> interface those machines are allowed to talk to.
>
> Cheers,
> Trond
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2005-05-04 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 11:06 Help needed Benjamin Jeeves
2005-05-04 12:26 ` Neil Horman
2005-05-04 12:35 ` Benjamin Jeeves
2005-05-05 13:18 ` Neil Horman
2005-05-04 12:35 ` Trond Myklebust
2005-05-04 12:39 ` Benjamin Jeeves [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200505041339.37074.benjamin@benjamin76.plus.com \
--to=benjamin@benjamin76.plus.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox