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/ - : send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
