From: NeilBrown <neilb@suse.de>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs-utils: Support binding to source address.
Date: Thu, 9 Jun 2011 16:38:23 +1000 [thread overview]
Message-ID: <20110609163823.689d6601@notabene.brown> (raw)
In-Reply-To: <4DF06430.1040608@candelatech.com>
On Wed, 08 Jun 2011 23:12:00 -0700 Ben Greear <greearb@candelatech.com> wrote:
> On 06/08/2011 10:47 PM, NeilBrown wrote:
> > On Wed, 8 Jun 2011 10:39:08 -0700 greearb@candelatech.com wrote:
> >
> >> From: Ben Greear<greearb@candelatech.com>
> >>
> >> This lets one specify the source IP address for
> >> sockets, allowing users to leverage routing rules
> >> on multi-homed systems.
> >>
> >
> > I gotta say I think this is rather horrible.....
>
> And you haven't even seen the kernel side yet ;)
>
> > As I understand it, the problem is bindresvport.
> > It binds to a port number before making a connection, so the local address
> > that is bound to is the 'default' rather than the best one to reach the given
> > target. And in some network configs this can be bad, because e.g. the target
> > may not be able to reply to that 'default' address.
> >
> > So you want to be able to specify the local endpoint fully when you bind, so
> > you require/allow the user to specify the local endpoint.
> >
> > Wouldn't it be soooo much nicer if the tools could just figure out the
> > 'correct' local endpoint and just use that? Obviously "yes" but maybe that
> > isn't straight forward. Have you looked into that at all?
>
> Not nicer in all cases.
>
> Sometimes a user knows best, and may want to use non-obvious
> routing setups, such as rules that send pkts to different gateways
> if they are from different source addresses.
I cannot say that I am convinced. Such rules sound like they are asking for
trouble and I'm not surprised when they get it.
> >
> > What think you?
>
> I think I really do want to specify the local IP address. There
> are lots of other tools that allow this (ping, ssh, cifs, etc),
> and there is a good reason for allowing it, primarily when used
> in conjunction with routing rules that are based on source
> IP.
ping is a debugging tool and clearly a special case. ssh is a bit of a
special case too. cifs less so. But there are far more tools that don't
allow you to specify a local endpoint address and I feel we should be strongly
discouraging configurations which need them.
So while I'm still not convinced your solution is a good idea, I admit I am
somewhat less convinced that it is a bad idea and I won't try to road-block.
But if some day someone points to existing use in nfs-utils as a
justification for adding source-address setting in firefox, I think I might
just scream.
Thanks,
NeilBrown
prev parent reply other threads:[~2011-06-09 6:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 17:39 [PATCH] nfs-utils: Support binding to source address greearb
2011-06-08 18:36 ` Jim Rees
2011-06-08 18:39 ` Ben Greear
2011-06-08 20:45 ` Chuck Lever
2011-06-08 19:11 ` J. Bruce Fields
2011-06-08 19:17 ` Ben Greear
2011-06-08 20:41 ` Chuck Lever
2011-06-08 20:54 ` Ben Greear
2011-06-08 21:16 ` Chuck Lever
2011-06-08 21:30 ` Ben Greear
2011-06-09 5:47 ` NeilBrown
2011-06-09 6:12 ` Ben Greear
2011-06-09 6:38 ` NeilBrown [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=20110609163823.689d6601@notabene.brown \
--to=neilb@suse.de \
--cc=greearb@candelatech.com \
--cc=linux-nfs@vger.kernel.org \
/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