From: Andi Kleen <ak@muc.de>
To: Thomas Graf <tgraf@suug.ch>
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: 6 Mar 2005 22:30:47 +0100
Date: Sun, 6 Mar 2005 22:30:47 +0100 [thread overview]
Message-ID: <20050306213047.GA65970@muc.de> (raw)
In-Reply-To: <20050306204516.GR31837@postel.suug.ch>
On Sun, Mar 06, 2005 at 09:45:16PM +0100, Thomas Graf wrote:
> * Andi Kleen <m1y8d0mss2.fsf@muc.de> 2005-03-06 21:19
> > Zdenek Radouch <zdenek@rcn.com> writes:
> > >
> > > There is no doubt that the 127.x net is treated in a special
> > > way. If I have to believe what I just learned, then the 127
> >
> > It is. 127.* is hardcoded in the routing engine and e.g.
> > it won't accept outside packets with a loopback address.
> >
> > Most likely it's enough to change the "LOOPBACK" macro to allow
> > parts of the Class A to be used for other purposes.
>
> 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.
-Andi
next prev parent reply other threads:[~2005-03-06 21:30 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 [this message]
2005-03-06 21:50 ` Thomas Graf
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=20050306213047.GA65970@muc.de \
--to=ak@muc.de \
--cc=linux-net@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
--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).