From owner-freebsd-arch@FreeBSD.ORG Mon Nov 7 14:40: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 2EF1F16A41F; Mon, 7 Nov 2005 14:40:50 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C73EB43D69; Mon, 7 Nov 2005 14:40:46 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id CF5D846B8C; Mon, 7 Nov 2005 09:40:43 -0500 (EST) Date: Mon, 7 Nov 2005 14:40:43 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Gleb Smirnoff In-Reply-To: <20051107140451.GU91530@cell.sick.ru> Message-ID: <20051107143620.P9690@fledge.watson.org> References: <20051107140451.GU91530@cell.sick.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@FreeBSD.org Subject: Re: ARP request retransmitting X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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 14:40:50 -0000 On Mon, 7 Nov 2005, Gleb Smirnoff wrote: > I have a proposition on changing the behavior of ARP retransmitting. > Currently we after sending several ARP requests, sending ARP requests > for given IP is suppressed for some interval (by default 20 seconds). > Probably this feature was designed in early 90th, when sending one > additional broadcast packet was an expensive thing. > > I suggest to keep sending ARP requests while there is a demand for this > (we are trying to transmit packets to this particular IP), ratelimiting > these requests to one per second. This will help in a quite common case, > when some host on net is rebooting, and we are waiting for him to come > up, and notice this only after 1 - 20 seconds since the time it is > reachable. While networks have gotten a lot faster in the last few years, I've noticed that many of the ones I deal with have also gotten a lot larger in terms of number of hosts. This has been possible both because of the absolute increase in bandwidth, and also because of the widespread use of switches to suppress unnecessary unicast traffic to segments. I worry that significantly increasing the amount of broadcast traffic will be a problem for sites with large bridged network configurations. On the other hand, they already have to deal with things like windows network neighborhoods, various service discovery protocols, and so on. Do you have any information on what other operating systems may have done in terms of tweaking ARP for improved responsiveness? I imagine we can't be the first to discuss such changes, and if there is already a widely deployed system with ARP adaptations of this sort, it would be interesting to know if they've seen any problems or have recommendations. Robert N M Watson