Right, and only one physical adapter = only one libpcap stream. All that is new.
However, it's possible that the multiple IP -> single MAC is what's poisoning the upstream switch. Either because it's a cheap piece 'o kit (a/k/a cr*p), or because it's trying to be clever. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth Porter Sent: Wednesday, June 08, 2005 12:22 PM To: [email protected] Subject: RE: [Ntop] Broadcast? --On Wednesday, June 08, 2005 6:14 AM -0500 Burton Strauss <[EMAIL PROTECTED]> wrote: > Now it's odd to have multiple interfaces on the same subnet, but > that's an internal routing problem. And it's also odd to have this on > an upstream switch (with the same MAC address, especially), but it > doesn't violate any network rules. In this case it was a case of transitioning a new host to replace an old one. The new one was brought in and given the 2nd address, tested, then assigned the first address, then the 2nd address was supposed be decommissioned. Except another admin decided he liked to keep it. ;) It's also useful if you need more than one SSL-capable virtual host on the same box, since the certificate follows the address. (The "eth1:1" name is typical Linux syntax for an alias of interface eth1, with a different IP address. There's only one physical adapter here.) _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
