From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Steve Iribarne <steve.iribarne@dilithiumnetworks.com>
Cc: "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro>,
hadi@cyberus.ca, Henrik Nordstrom <hno@marasystems.com>,
Martin Mares <mj@ucw.cz>, Zdenek Radouch <zdenek@rcn.com>,
Eran Mann <emann@mrv.com>, Thomas Graf <tgraf@suug.ch>,
Andi Kleen <ak@muc.de>,
netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: Do you know the TCP stack? (127.x.x.x routing)
Date: Thu, 10 Mar 2005 09:49:40 -0500 [thread overview]
Message-ID: <d120d50005031006492511c48@mail.gmail.com> (raw)
In-Reply-To: <B8561865DB141248943E2376D0E85215FFE3D6@DHOST001-17.DEX001.intermedia.net>
On Thu, 10 Mar 2005 06:35:43 -0800, Steve Iribarne
<steve.iribarne@dilithiumnetworks.com> wrote:
> -> You say that a client will not allow you to use net 10.
> -> OK, but, the same client would not allow you to use 127/8 because
> they
> -> use
> -> it!
> -> What I'm saying is that 10.0.0.0/8 and 127.0.0.0/8 are the same. The
> -> customer can use them.
> -> You assume that the client will not use 127/8. Why? This is wrong.
> -> You can use it, the client can use it.
> ->
>
> No. If the client uses 127/8 on a linux box, it is just a loopback and
> will never go out on the wire and the applications (i.e. telnet, ftp,
> ping, whatever) will just loopback.
>
This assumes that the client did not apply the same hack you did.
--
Dmitry
next prev parent reply other threads:[~2005-03-10 14:49 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 14:35 Do you know the TCP stack? (127.x.x.x routing) Steve Iribarne
2005-03-10 14:49 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-10 15:04 Steve Iribarne
2005-03-10 15:25 ` Catalin(ux aka Dino) BOIE
2005-03-09 23:51 Boian Bonev
2005-03-10 0:23 ` Jason Lunz
2005-03-09 21:57 Steve Iribarne
2005-03-10 0:11 ` jamal
2005-03-09 17:33 Steve Iribarne
2005-03-09 19:40 ` jamal
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-08 15:07 Steve Iribarne
2005-03-06 2:20 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
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
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=d120d50005031006492511c48@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=ak@muc.de \
--cc=dtor_core@ameritech.net \
--cc=emann@mrv.com \
--cc=hadi@cyberus.ca \
--cc=hno@marasystems.com \
--cc=linux-net@vger.kernel.org \
--cc=mj@ucw.cz \
--cc=netdev@oss.sgi.com \
--cc=steve.iribarne@dilithiumnetworks.com \
--cc=tgraf@suug.ch \
--cc=util@deuroconsult.ro \
--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).