> -----Original Message----- > From: linux-net-owner@xxxxxxxxxxxxxxx > [mailto:linux-net-owner@xxxxxxxxxxxxxxx]On Behalf Of Henrik Nordstrom > Sent: Wednesday, August 31, 2005 2:48 AM > To: Al Boldi > Cc: linux-net@xxxxxxxxxxxxxxx > Subject: Re: Kernel Routing and the IntraNet > ... > > Should an IP be bound to a dev? > > Well, it is not. All configred IP addresses is available on > all IP enabled > interfaces. The minor detail on which interface the IP > address was added > only tells where the implicit route to that network should be > pointing.. FYI, it also defines the preferred source IP address of packets transmitted out that device. > >> The local IP stack will get somewhat upset if it receives > IP packets > >> with > >> a source IP matching one of it's own interfaces, as this indicates > >> something is wrong in the network either an IP conflict or > packets being > >> looped back to the sender host. > > I assume you are referring to unicast packets here. I would think that packets like this should be expected if one were to ping an attached subnet's broadcast address. Jeff Haran Brocade Communications Systems - : 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
