From owner-freebsd-arch@FreeBSD.ORG Mon Nov 7 23:45:50 2005 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D7C616A41F for ; Mon, 7 Nov 2005 23:45:50 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id E816143D49 for ; Mon, 7 Nov 2005 23:45:49 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jA7NjnHs042843; Mon, 7 Nov 2005 15:45:49 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jA7NjnYw042842; Mon, 7 Nov 2005 15:45:49 -0800 (PST) (envelope-from jmg) Date: Mon, 7 Nov 2005 15:45:48 -0800 From: John-Mark Gurney To: Charles Swiger Message-ID: <20051107234548.GF775@funkthat.com> Mail-Followup-To: Charles Swiger , Garance A Drosihn , arch@freebsd.org References: <20051107140451.GU91530@cell.sick.ru> <436F7DDB.40703@mac.com> <20051107224338.GE775@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: arch@freebsd.org, Garance A Drosihn Subject: Re: ARP request retransmitting X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2005 23:45:50 -0000 Charles Swiger wrote this message on Mon, Nov 07, 2005 at 18:17 -0500: > On Nov 7, 2005, at 5:43 PM, John-Mark Gurney wrote: > >>While that "other hand" is true, here at RPI we deal with some of > >>those other-hand issues by simply turning them off. We turn off > >>multi-cast by default on some of our networks, for instance. But > >>there's no way we can turn off ARP, so I think more care needs to > >>be taken to make sure ARP remains network-friendly. > > > >And most places that have VERY large number of hosts in a broadcast > >domain (a partially populated class b), have smart switches that cache > >arp requests, and prevent the arp traffic from killing the network... > > Really? You're saying that "tcpdump -nt arp" never shows any > requests except those made by the local host? > > Which vendor and which switch model? Just a random search for smart arp large, turned up user's manual for the WaveSwitch 9000, from Plaintree Systems.. The docs say: Address Resolution Protocol (ARP) is the means by which a host or router maps an IP address to a physical address. WaveSwitch 9000 software contains the SmartARP feature that allows for reduced impact of ARP broadcasting. Normally, ARP broadcasts are flooded to all ports on a switch. Switch ports that are not connected to the target host must, therefore, receive and partially process the broadcast frames. This can potentially affect the performance of all hosts on the bridged network. With the SmartARP feature, ARP broadcasts are confined to only the applicable switch ports (see Figure 67). And the diagram shows the arp request being restricted to only the port with the router and the host on it... A coworker also says that the Foundary switches can do it, and did it like five years ago... I haven't confirmed this myself... > Smart switches will generally keep track of 1000 or 4000 or so MAC > addresses and the ports those MACs are associated with, but I am not > aware of anything in them which blocks ARP traffic or anything else > which uses the all-ones broadcast MAC address. I can see ARP > requests going out from any/all of the other machines on the network > I'm using right now (using several 3com SuperStack 3300's), and I've > seen the same thing on networks using the HP Procurve or Cisco 29xx > switches. I'd imagine you have to turn it on... since it'd have odd behavior if you weren't expecting it... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."