pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Gaetano Mendola <mendola@bigfoot.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: NIC to NIC connection
Date: Thu, 21 Oct 2004 05:19:23 -0500
Message-ID: <20041021101923.GA31585@wolff.to> (raw)
In-Reply-To: <41776E45.2070109@bigfoot.com>
References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com>
	<00d001c4b5f9$f4d63660$8300a8c0@solent>
	<20041019220133.GA2957@wolff.to>
	<41776E45.2070109@bigfoot.com>

On Thu, Oct 21, 2004 at 10:07:33 +0200,
  Gaetano Mendola <mendola@bigfoot.com> 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.



view thread (20+ messages)  latest in thread

Message-ID: <20041021101923.GA31585@wolff.to>
Permalink:  ../20041021101923.GA31585@wolff.to/
Also on:    postgresql.org/message-id/20041021101923.GA31585@wolff.to

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: bruno@wolff.to, mendola@bigfoot.com
  Subject: Re: NIC to NIC connection
  In-Reply-To: <20041021101923.GA31585@wolff.to>
  References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com> <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41776E45.2070109@bigfoot.com> <20041021101923.GA31585@wolff.to>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox