> Absolutely DO NOT do this. Each interface needs a unique address (and > IMHO, a unique DNS name). The whole premise of IP routing and network > function is based on this concept.
You don't have to have a per interface IP address or DNS (or indeed MAC address), but they must be at least per host (and virtual machines with their own IP stack are a host). IP is quite happy with that situation. > happen. IP routing is based on knowing a destination that you CAN reach > to send packets to destinations that you don't know how to reach. > Without unique addresses, the whole thing falls apart. If every instance of the address is owned by the same machine this is untrue - it doesn't matter which interface it arrives upon. IP is like postal mail, you can have ten mail boxes all with the same number providing they are for the same house and nobody gets confused. The only notionally "not allowed" case is two machines with the same IP address that one is not usually permissible although there are situations you can and people do it to make get multiple sites around the world to appear on the same address and have packets routed to the nearest instance. That requires a knowledge of BGP4, backbone route visibility and an expert so don't try it at home. > (the only reason that your setup hasn't already fallen is that some of > the older IBM stacks permitted this configuration error. The new ones > don't.) Sounds like a new added bug as you describe it. Alan ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
