netdev
[Top] [All Lists]

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

To: Steve Iribarne <steve.iribarne@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Do you know the TCP stack? (127.x.x.x routing)
From: "Catalin(ux aka Dino) BOIE" <util@xxxxxxxxxxxxxxx>
Date: Thu, 10 Mar 2005 08:48:34 +0200 (EET)
Cc: hadi@xxxxxxxxxx, Henrik Nordstrom <hno@xxxxxxxxxxxxxxx>, Martin Mares <mj@xxxxxx>, Zdenek Radouch <zdenek@xxxxxxx>, Eran Mann <emann@xxxxxxx>, Thomas Graf <tgraf@xxxxxxx>, Andi Kleen <ak@xxxxxx>, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx
In-reply-to: <B8561865DB141248943E2376D0E85215FFE1C8@DHOST001-17.DEX001.intermedia.net>
References: <B8561865DB141248943E2376D0E85215FFE1C8@DHOST001-17.DEX001.intermedia.net>
Sender: netdev-bounce@xxxxxxxxxxx
1st bug:  Customer had the same 10.100.xx.xx/24 net that I had and my
inter-system communication wouldn't work, because all my routes got
screwed up.  (i.e the SNMP sub-agents couldn't talk with the master).

1st response to bug:  Well can you use another network address range?
Customer response:  Hell no.

Solution to bug1:  Easy, let the user configure the mgmt network ip
address.
Customers answer to bug1 solution:  Get the hell out of here; you don't
do out-of-band mgmt.  Do you know what a security risk this is for me?
Blah blah blah....  Even though all inter-chassis communication was done
securely, I couldn't convince them. I had a customer boot me out of his
office and boot our company out **because** of my design.  Not a good
feeling.

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.


---
Catalin(ux aka Dino) BOIE
catab at deuroconsult.ro
http://kernel.umbrella.ro/

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