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 48ABE32A124 for ; Thu, 21 Oct 2004 11:08:54 +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 51565-04 for ; Thu, 21 Oct 2004 10:08:42 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id EEB8032A11A for ; Thu, 21 Oct 2004 11:08:42 +0100 (BST) Received: (qmail 31740 invoked by uid 500); 21 Oct 2004 10:19:23 -0000 Date: Thu, 21 Oct 2004 05:19:23 -0500 From: Bruno Wolff III To: Gaetano Mendola Cc: pgsql-admin@postgresql.org Subject: Re: NIC to NIC connection Message-ID: <20041021101923.GA31585@wolff.to> Mail-Followup-To: Gaetano Mendola , pgsql-admin@postgresql.org 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.5.6i 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/275 X-Sequence-Number: 15268 On Thu, Oct 21, 2004 at 10:07:33 +0200, Gaetano Mendola wrote: > 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, 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. Switches don't do arps; they are a layer 2 device (and hence don't know about IP addresses. They cache mac address port bindings. If their cache expires before the cached IP mac address bindings in some attached device then they can get requests to send to mac addresses for which they don't have a cached port. In that case they are supposed to do a port flood of the packet. I actually had a problem with a switch that was misconfigured and didn't do a port flood in these circumstances. That combined with a linux box that wasn't chatty enough to stay in the switch's cache and that the router cached IP address - mac address bindings for hours while the switch kept mac address - port bindings for minutes caused my machine to be unreachable to other hosts for periods of time.