From: jamal <hadi@cyberus.ca>
To: Martin Mares <mj@ucw.cz>
Cc: Zdenek Radouch <zdenek@rcn.com>,
Steve Iribarne <steve.iribarne@dilithiumnetworks.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: 08 Mar 2005 09:17:50 -0500 [thread overview]
Message-ID: <1110291470.1043.211.camel@jzny.localdomain> (raw)
In-Reply-To: <20050308140301.GC20607@atrey.karlin.mff.cuni.cz>
On Tue, 2005-03-08 at 09:03, Martin Mares wrote:
> No, since this tends to interfere with the outside network using the
> same private (RFC 1918) addresses. People generally don't expect network
> equipment to collide with their perfectly legal addressing plan.
>
Aha! Thanks for clarifying this. So the problem domain is: "IP address
conflict" detection and somehow this is seen as a resolution to that
problem.
So what happens when you put tow or three of Zdenek's boxes in one
location? Back to square 1?
> On the other hand, if the manufacturer gets a small block of public
> addresses and uses it in all his devices (the same block everywhere)
> for internal purposes only (no packet ever escapes), everything is
> perfectly correct and no collisions can arise.
Yes, I see.
Except this wont be practical for IPV4 since those addresses are scarce.
May make sense for V6 though (becomes like MAC addresses on NICS).
cheers,
jamal
next prev parent reply other threads:[~2005-03-08 14:17 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
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 [this message]
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=1110291470.1043.211.camel@jzny.localdomain \
--to=hadi@cyberus.ca \
--cc=ak@muc.de \
--cc=emann@mrv.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=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