netdev
[Top] [All Lists]

Re: Do you know the TCP stack? (127.x.x.x routing)

To: Martin Mares <mj@xxxxxx>
Subject: Re: Do you know the TCP stack? (127.x.x.x routing)
From: jamal <hadi@xxxxxxxxxx>
Date: 08 Mar 2005 09:17:50 -0500
Cc: Zdenek Radouch <zdenek@xxxxxxx>, Steve Iribarne <steve.iribarne@xxxxxxxxxxxxxxxxxxxxx>, Eran Mann <emann@xxxxxxx>, Thomas Graf <tgraf@xxxxxxx>, Andi Kleen <ak@xxxxxx>, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx
In-reply-to: <20050308140301.GC20607@xxxxxxxxxxxxxxxxxxxxxxxx>
Organization: jamalopolous
References: <E1D7zBN-0004hX-00@xxxxxxxxxxxxxxxxxxxxxxx> <20050306173145.GQ31837@xxxxxxxxxxxxxx> <E1D81mg-0002rz-00@xxxxxxxxxxxxxxxxxxxxxxx> <m1y8d0mss2.fsf@xxxxxx> <3sp35g$7hpm0@xxxxxxxxxxxxxxxxxxxxxxx> <422C0B50.20500@xxxxxxx> <3sp35g$7rsc1@xxxxxxxxxxxxxxxxxxxxxxx> <1110288879.1050.167.camel@xxxxxxxxxxxxxxxx> <20050308135134.GA20607@xxxxxxxxxxxxxxxxxxxxxxxx> <1110290300.1050.190.camel@xxxxxxxxxxxxxxxx> <20050308140301.GC20607@xxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
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


<Prev in Thread] Current Thread [Next in Thread>