From: "H. Peter Anvin" <hpa@zytor.com>
To: Dylan <autofs@dylan.me.uk>
Cc: autofs@linux.kernel.org, Eric Werme USG <werme@alpha.zk3.dec.com>
Subject: Re: autofs no_local_binds option (nfs <-> bind mounts)
Date: Tue, 13 Jan 2004 12:25:48 -0800 [thread overview]
Message-ID: <4004544C.7030904@zytor.com> (raw)
In-Reply-To: <200401132023.49657.autofs@dylan.me.uk>
Dylan wrote:
> On Tuesday 13 January 2004 20:03 pm, H. Peter Anvin wrote:
>
>
>>However, this doesn't address the issue of the client being *the same
>>system*, in which case you can't just move the IP address away from
>>it, since local == remote; you can no longer send packets to the
>>server and get a response back. You can do it if you can get the
>>client and the server sides to bind to *different* IP addresses, in
>>which case the current autofs behaviour will correctly see them as
>>being separate and mount NFS.
>
> Would binding an alias address to the interface be sufficient?
>
No, you have to force the local port to not be bound to the same
address. I think this can be done with iptables rules, but I'm not
sure... I'm not a networking wizard.
-hpa
next prev parent reply other threads:[~2004-01-13 20:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 19:58 autofs no_local_binds option (nfs <-> bind mounts) Eric Werme USG
2004-01-13 20:03 ` H. Peter Anvin
2004-01-13 20:23 ` Dylan
2004-01-13 20:25 ` H. Peter Anvin [this message]
2004-01-13 20:58 ` Mike Waychison
2004-01-13 21:06 ` H. Peter Anvin
2004-01-13 20:42 ` Eric Werme USG
2004-01-13 20:54 ` H. Peter Anvin
2004-01-13 21:04 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 14:26 MARX,ALEXANDER (HP-Germany,ex1)
2004-01-13 17:14 ` H. Peter Anvin
2004-01-13 17:48 ` Mike Waychison
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=4004544C.7030904@zytor.com \
--to=hpa@zytor.com \
--cc=autofs@dylan.me.uk \
--cc=autofs@linux.kernel.org \
--cc=werme@alpha.zk3.dec.com \
/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.