pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jay A. Kreibich <jak@uiuc.edu>
To: Gaetano Mendola <mendola@bigfoot.com>
Cc: Bruno Wolff III <bruno@wolff.to>
Cc: pgsql-admin@postgresql.org
Subject: Re: NIC to NIC connection
Date: Thu, 21 Oct 2004 10:10:15 -0500
Message-ID: <20041021151015.GA21697@uiuc.edu> (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: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.
          <http://www.uiuc.edu/~jak; | University of Illinois at U/C



view thread (20+ messages)  latest in thread

Message-ID: <20041021151015.GA21697@uiuc.edu>
Permalink:  ../20041021151015.GA21697@uiuc.edu/
Also on:    postgresql.org/message-id/20041021151015.GA21697@uiuc.edu

 · 

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: jak@uiuc.edu, mendola@bigfoot.com, bruno@wolff.to
  Subject: Re: NIC to NIC connection
  In-Reply-To: <20041021151015.GA21697@uiuc.edu>
  References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com> <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41776E45.2070109@bigfoot.com> <20041021151015.GA21697@uiuc.edu>

* 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