From owner-freebsd-current Sun May 7 18:53:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id B861537B84C for ; Sun, 7 May 2000 18:53:18 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 6B3DD4CE0F; Sun, 7 May 2000 21:52:45 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id VAA11790; Sun, 7 May 2000 21:52:09 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id SAA09656; Sun, 7 May 2000 18:50:51 -0700 (PDT) Message-Id: <200005080150.SAA09656@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: dhesi@rahul.net Subject: Re: gratuituous arp for multiple IP addresses Cc: freebsd-current@freebsd.org References: <20000504191638.64E077D0D@yellow.rahul.net> Date: Sun, 7 May 2000 18:50:50 -0700 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD 4.0-RELEASE does the gratuitous ARP when ifconfig'ing an alias: fenestro# ifconfig de1 1.2.3.5 alias 18:35:47.269471 0:40:5:42:d6:de Broadcast arp 42: arp who-has 1.2.3.5 tell 1.2.3.5 FreeBSD 3.4-STABLE also does: mango# ifconfig xl0 135.197.2.250 netmask 255.255.255.255 alias 18:39:12.509125 0:10:4b:cc:83:5f Broadcast arp 42: arp who-has 135.197.2.250 tell 135.197.2.250 I'm not sure what this says; it's entirely possible that there are conditions under which it doesn't or it fails for some reason. For example, there was a certain failure mode with sending multicast leave messages; the packet would be sent to the chip to be sent and then the multicast filter would be changed causing the chip to reset and lose the packet that's currently being transmitted. Adding an alias shouldn't cause the chip to be reset so that's not likely to be the exact problem, but perhaps something similar is happening. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message