From: Thomas Graf <tgraf@suug.ch>
To: Andi Kleen <ak@muc.de>
Cc: Zdenek Radouch <zdenek@rcn.com>, Martin Mares <mj@ucw.cz>,
netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: Do you know the TCP stack? (127.x.x.x routing)
Date: Sun, 6 Mar 2005 22:50:11 +0100 [thread overview]
Message-ID: <20050306215011.GS31837@postel.suug.ch> (raw)
In-Reply-To: <20050306213047.GA65970@muc.de>
* Andi Kleen <20050306213047.GA65970@muc.de> 2005-03-06 22:30
> On Sun, Mar 06, 2005 at 09:45:16PM +0100, Thomas Graf wrote:
> > Yes, it will work around the martian route and arp checks but
> > will probably break quite a few usersapce applications.
>
> Unlikely. glibc has an own LOOPBACK() and all modern distributions
> use separate kernel/user headers anyways.
I was rather referring to the reduced loopback scope. I'm aware of
at least 3 applications that make extensive use of big portions of
the scope to multiplex streams and they depend on LOOPBACK() to make
sure the addresses they use will be looped back.
I agree that userspace has its own LOOPBACK macro in most cases but
this is exactly the problem, it may result in userspace assuming
certain addreses to be regarded as loopback by the kernel when they
won't. This of course heavily depends on how the LOOPBACK macro is
changed. I just wanted to point out that it may affect userspace
under certain circumstances.
next prev parent reply other threads:[~2005-03-06 21:50 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 2:20 Do you know the TCP stack? (127.x.x.x routing) Zdenek Radouch
2005-03-06 9:56 ` Martin Mares
2005-03-06 17:01 ` Zdenek Radouch
2005-03-06 17:12 ` alex
2005-03-06 17:31 ` Thomas Graf
2005-03-06 19:48 ` Zdenek Radouch
2005-03-06 20:19 ` alex
2005-03-06 20:19 ` Andi Kleen
2005-03-06 20:45 ` Thomas Graf
2005-03-06 21:30 ` Andi Kleen
2005-03-06 21:50 ` Thomas Graf [this message]
2005-03-06 21:50 ` Zdenek Radouch
2005-03-07 7:01 ` Sumit Pandya
2005-03-07 8:05 ` Eran Mann
2005-03-07 12:14 ` jamal
2005-03-07 23:50 ` jamal
2005-03-08 3:15 ` Zdenek Radouch
2005-03-08 13:34 ` jamal
2005-03-08 13:51 ` Martin Mares
2005-03-08 13:58 ` jamal
2005-03-08 14:03 ` Martin Mares
2005-03-08 14:17 ` jamal
2005-03-08 14:20 ` Martin Mares
2005-03-08 18:40 ` Henrik Nordstrom
2005-03-08 21:17 ` jamal
2005-03-09 9:09 ` Henrik Nordstrom
2005-03-09 12:39 ` jamal
2005-03-09 13:39 ` Zdenek Radouch
2005-03-09 14:18 ` jamal
2005-03-09 16:46 ` Jason Lunz
2005-03-10 10:10 ` Henrik Nordstrom
2005-03-09 17:52 ` Matt Mackall
2005-03-10 6:57 ` Catalin(ux aka Dino) BOIE
2005-03-09 22:34 ` Henrik Nordstrom
2005-03-10 1:47 ` Jamie Lokier
2005-03-08 18:34 ` Henrik Nordstrom
2005-03-09 5:33 ` Zdenek Radouch
2005-03-08 14:02 ` Thomas Graf
-- strict thread matches above, loose matches on Subject: below --
2005-03-08 15:07 Steve Iribarne
2005-03-09 15:01 Steve Iribarne
2005-03-09 16:00 ` jamal
2005-03-10 6:48 ` Catalin(ux aka Dino) BOIE
2005-03-09 17:33 Steve Iribarne
2005-03-09 19:40 ` jamal
2005-03-09 21:57 Steve Iribarne
2005-03-10 0:11 ` jamal
2005-03-09 23:51 Boian Bonev
2005-03-10 0:23 ` Jason Lunz
2005-03-10 14:35 Steve Iribarne
2005-03-10 14:49 ` Dmitry Torokhov
2005-03-10 15:04 Steve Iribarne
2005-03-10 15:25 ` Catalin(ux aka Dino) BOIE
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=20050306215011.GS31837@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=ak@muc.de \
--cc=linux-net@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=netdev@oss.sgi.com \
--cc=zdenek@rcn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).