mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Jeff Haran <jharan@Brocade.COM>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] ip / ifconfig redesign
Date: Sat, 3 Dec 2005 15:58:48 +0100	[thread overview]
Message-ID: <20051203145848.GK13985@lug-owl.de> (raw)
In-Reply-To: <447BB19E14004A4388CB9A864D2BA7630DF693@hq-ex-6.brocade.com>

[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]

On Fri, 2005-12-02 14:34:08 -0800, Jeff Haran <jharan@Brocade.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.
> kchan          :root> ip addr show
> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue 
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/16 scope host lo
> 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>     link/ether 00:05:1e:35:00:49 brd ff:ff:ff:ff:ff:ff
>     inet 10.32.246.19/20 brd 10.32.255.255 scope global eth0
>     inet 10.32.246.16/20 brd 10.32.255.255 scope global secondary eth0:1
> 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>     link/ether 00:05:1e:35:00:4a brd ff:ff:ff:ff:ff:ff
>     inet 10.0.0.6/24 brd 10.255.255.255 scope global eth1
> 4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>     link/ether 00:05:1e:35:00:4b brd ff:ff:ff:ff:ff:ff
>     inet 127.1.16.16/24 brd 127.255.255.255 scope global eth2
> 6: fc0: <BROADCAST,UP> mtu 2024 qdisc pfifo_fast qlen 100
>     link/ieee802 00:05:1e:35:00:49 brd ff:ff:ff:ff:ff:ff
>     inet 2.3.4.6/24 brd 2.3.4.255 scope global fc0
> kchan          :root> ip addr add 4.5.6.7
> Not enough information: "dev" argument is required.
> kchan          :root> 

We were talking about apps binding to a non-local address. That is,
some locally running server binds to any address that is not yet there
(anything except 0.0.0.0, 127.0.0.1, 10.32.246.19, 109.32.246.16,
10.0.0.6, 127.1.16.16, 2.3.4.6).  So we're talking about two different
subjects...

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 für einen Freien Staat voll Freier Bürger"  | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2005-12-03 14:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <447BB19E14004A4388CB9A864D2BA7630DF693@hq-ex-6.brocade.com>
2005-12-03 14:58 ` Jan-Benedict Glaw [this message]
2005-12-02 19:53 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
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

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=20051203145848.GK13985@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=jharan@Brocade.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

all inboxes | Powered by JetHome®