From: David Liontooth <liontooth@cogweb.net>
To: nfs@lists.sourceforge.net
Subject: NFS using iptables PREROUTING?
Date: Sun, 08 Jul 2007 09:18:24 -0700 [thread overview]
Message-ID: <46910E50.2020000@cogweb.net> (raw)
Is it possible to access an NFS server on a private network from a
machine on a public network?
I have a Debian box B on a private network visible only to a gateway G.
B has drive partitions I would like to mount on outside box A.
To make B visible to A, I use this sort of thing for ssh:
iptables -t nat -A PREROUTING -p tcp -d 128.65.183.178 --dport 9000 -j
DNAT --to 192.168.0.1:22
This allows me to ssh directly from A to B, as if B were on a public
network. Can I do the same with NFS?
So far, I've figured out how to fix the port of mountd, statd, and
lockd, and I can preroute these ports, along with 2049 for nfs and 111
for portmap.
For each of these, I can preroute tcp and udp packets on G:
# Forward tcp and udp on port 111 for portmap on A
iptables -t nat -A PREROUTING -p tcp -d 128.65.183.178 --dport 9200 -j
DNAT --to 192.168.0.3:111
iptables -t nat -A PREROUTING -p udp -d 128.65.183.178 --dport 9200 -j
DNAT --to 192.168.0.3:111
# Forward tcp and upd for port 2049 for nfs to A (tcp may not be needed)
iptables -t nat -A PREROUTING -p tcp -d 128.65.183.178 --dport 9201 -j
DNAT --to 192.168.0.3:2049
iptables -t nat -A PREROUTING -p udp -d 128.65.183.178 --dport 9201 -j
DNAT --to 192.168.0.3:2049
# Forward tcp and udp for lockd (port assigned in A:/boot/grub/menu.lst)
iptables -t nat -A PREROUTING -p tcp -d 128.65.183.178 --dport 9202 -j
DNAT --to 192.168.0.3:4000
iptables -t nat -A PREROUTING -p udp -d 128.65.183.178 --dport 9202 -j
DNAT --to 192.168.0.3:4000
# Forward tcp and udp for mountd (port assigned in
A:/etc/default/nfs-common)
iptables -t nat -A PREROUTING -p tcp -d 128.65.183.178 --dport 9203 -j
DNAT --to 192.168.0.3:4001
iptables -t nat -A PREROUTING -p udp -d 128.65.183.178 --dport 9203 -j
DNAT --to 192.168.0.3:4001
# Forward tcp and udp for statd (port assigned in A:/etc/default/nfs-common)
iptables -t nat -A PREROUTING -p tcp -d 128.65.183.178 --dport 9204 -j
DNAT --to 192.168.0.3:4002
iptables -t nat -A PREROUTING -p udp -d 128.65.183.178 --dport 9204 -j
DNAT --to 192.168.0.3:4002
# Do you need a POSTROUTING line to take outgoing tcp/udp for statd on
port 4003?
However, at this point I get a sinking feeling this is still not possible.
Is there a way on the client A to specify where to look for the
different NFS resources on B (via G)?
How do I tell NFS that for this particular mount B, and only for B,
portmap is on 9200, nfs is on 9201, lockd on 9202, mountd on 9203, and
statd on 9204?
Can I specify all of this in /etc/fstab? For ssh, I can specify
host:port in /etc/ssh/ssh_config, but it uses only one service.
On A, I also mount several other NFS drives, and they need the default
ports.
G, the gateway, also exports its own drives to A via NFS, using the
default ports.
I would prefer straight NFS with iptables to ssh tunneling, but can it
be done?
Cheers,
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-07-08 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 16:18 David Liontooth [this message]
2007-07-09 6:25 ` NFS using iptables PREROUTING? David Liontooth
2007-07-09 10:39 ` Jeff Layton
2007-07-09 18:37 ` David Liontooth
-- strict thread matches above, loose matches on Subject: below --
2007-07-09 0:40 David Liontooth
2007-07-09 6:22 ` David Liontooth
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=46910E50.2020000@cogweb.net \
--to=liontooth@cogweb.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.