X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D2F6E32AE63 for ; Thu, 21 Oct 2004 16:10:28 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 52279-06 for ; Thu, 21 Oct 2004 15:10:23 +0000 (GMT) Received: from expredir4.cites.uiuc.edu (expredir4.cites.uiuc.edu [128.174.5.187]) by svr1.postgresql.org (Postfix) with ESMTP id F1C3E32ABF5 for ; Thu, 21 Oct 2004 16:10:21 +0100 (BST) Received: from firefox.cites.uiuc.edu (firefox.ci.uiuc.edu [192.17.25.8]) by expredir4.cites.uiuc.edu (8.12.11/8.12.11) with ESMTP id i9LFAGNU007339; Thu, 21 Oct 2004 10:10:16 -0500 (CDT) Received: by firefox.cites.uiuc.edu (Postfix, from userid 79964) id A47AC2B7354; Thu, 21 Oct 2004 10:10:15 -0500 (CDT) Date: Thu, 21 Oct 2004 10:10:15 -0500 From: "Jay A. Kreibich" To: Gaetano Mendola Cc: Bruno Wolff III , pgsql-admin@postgresql.org Subject: Re: NIC to NIC connection Message-ID: <20041021151015.GA21697@uiuc.edu> Reply-To: jak@uiuc.edu References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41776E45.2070109@bigfoot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41776E45.2070109@bigfoot.com> User-Agent: Mutt/1.4.1i X-URL: http://www.uiuc.edu/~jak (includes PGP key) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/279 X-Sequence-Number: 15272 On Thu, Oct 21, 2004 at 10:07:33AM +0200, Gaetano Mendola scratched on the wall: > Bruno Wolff III wrote: > >Also I believe that if > >a switch doesn't remember where a particular mac address is it will send > >the packet to all of the attached ports. > > I don't think so, I guess the switch perform a sort of arpping in order to > detect who have a macaddress assigned, No, he's right. If the MAC to port mapping has not been learned by the switch, the packet is flooded to all ports or (for really bad switches) dropped. A switch is a pure layer-two device and ARP involves layer-three addresses and concepts. The only part of a switch that will ARP is the management system, assuming it has an IP address of its own. This is actually a standard test we run when evaluating switches for deployment on campus. We hook about ten devices up to a switch and send them tons of traffic. The systems count incoming packets but they do not generate any traffic, so the switch is forced to flood all the traffic. The vast majority of low-cost switches roll over and die at that point. > even the multicast is not sent > to all ports but only to that ports where "someone" sent an arp packet > saying the he was registered to a multicast address. Not ARP, IGMP (Internet Group Management Protocol). It's part of the IP suite, and is much higher up in the protocol stack. And again, this isn't true unless the switch does IGMP snooping or has multicast assist from the router. IGMP snooping is becoming more common on higher-end switches, but there are some companies that prefer the router assist design. The problem with that is that the switches and routers need to be from the same company. IGMP snooping is also really tricky to do right, and there are still some situations where you are forced to flood traffic. -j -- Jay A. Kreibich | Comm. Technologies, R&D jak@uiuc.edu | Campus IT & Edu. Svcs. | University of Illinois at U/C