From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-net@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Al Boldi <a1426z@gawab.com>
Subject: Re: [RFC] ip / ifconfig redesign
Date: Thu, 08 Dec 2005 03:15:51 -0700 [thread overview]
Message-ID: <m164pzc2so.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20051202211920.GJ13985@lug-owl.de> (Jan-Benedict Glaw's message of "Fri, 2 Dec 2005 22:19:20 +0100")
Jan-Benedict Glaw <jbglaw@lug-owl.de> writes:
> On Fri, 2005-12-02 22:53:19 +0300, Al Boldi <a1426z@gawab.com> wrote:
>
>> The obvious benefit here, would be the transparent ability for apps to bind
>> to addresses, regardless of the link existence.
>
> # echo 1 > /proc/sys/net/ipv4/ip_nonlocal_bind
>
> and/or bind to address 0 (aka 0.0.0.0) instead of a given IP address.
Or equally:
int opt = 1;
setsockopt(fd, IPFREEBIND, &opt, sizeof(opt));
in your application.
It's cool the backwards compatibility is so good no one even
noticed it was implemented :)
And from the kernel source as to why this behaviour is not
the default.
/* Not specified by any standard per-se, however it breaks too
* many applications when removed. It is unfortunate since
* allowing applications to make a non-local bind solves
* several problems with systems using dynamic addressing.
* (ie. your servers still start up even if your ISDN link
* is temporarily down)
*/
Eric
next prev parent reply other threads:[~2005-12-08 10:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 19:53 [RFC] ip / ifconfig redesign Al Boldi
2005-12-02 19:59 ` Pekka Savola
2005-12-02 20:08 ` Ben Greear
2005-12-02 20:38 ` linux-os (Dick Johnson)
2005-12-02 22:49 ` Jesper Juhl
2005-12-10 18:51 ` Stefan Smietanowski
2005-12-02 21:19 ` Jan-Benedict Glaw
2005-12-08 10:15 ` Eric W. Biederman [this message]
2005-12-02 22:40 ` Jeff V. Merkey
2005-12-03 13:46 ` Al Boldi
2005-12-11 4:59 ` Bernd Eckenfels
2005-12-14 14:19 ` Al Boldi
[not found] <447BB19E14004A4388CB9A864D2BA7630DF693@hq-ex-6.brocade.com>
2005-12-03 14:58 ` Jan-Benedict Glaw
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=m164pzc2so.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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