From owner-freebsd-net@FreeBSD.ORG Wed Jan 14 12:45:46 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E66316A4CE; Wed, 14 Jan 2004 12:45:46 -0800 (PST) Received: from mail.npubs.com (mail.writemehere.com [209.66.100.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A86643D88; Wed, 14 Jan 2004 12:45:11 -0800 (PST) (envelope-from nielsen@memberwebs.com) Resent-Message-Id: Message-ID: <4005AA55.3080202@memberwebs.com> From: Nielsen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Resent-Date: Wed, 14 Jan 2004 20:45:30 +0000 (GMT) Resent-From: nielsen@memberwebs.com (Postfix Filters) cc: freebsd-net@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Re: Gratituous ARP and the em driver X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Wed, 14 Jan 2004 20:45:46 -0000 X-List-Received-Date: Wed, 14 Jan 2004 20:45:46 -0000 Yes, this is the case. I tested it again, and the arp packet in question doesn't get to the other machines. The sending machine does send gratituous arp, however the em NIC is down for 3 or 4 seconds, and the packet isn't sent on the wire. I find it odd that the em driver would need to reinitialize the NIC each time an alias is added. I haven't seen any other network drivers do this. And, yes, it occurs every time an alias is added or removed from the NIC. Not just the first time. Cheers, Nate Robert Watson wrote: >On -1 xxx -1, Nielsen wrote: >If you run tcpdump on the machine to sniff the interface in question >looking for arp packets, does tcpdump see the gratuitous arp? I'm >guessing that it does, and the lack of sending the arp is a result of >delays in negotiating on the wire. Does this problem turn up only the >first time you raise the interface, or every time you change the IP >address on the interface? > >Robert N M Watson FreeBSD Core Team, TrustedBSD Projects >robert@fledge.watson.org Senior Research Scientist, McAfee Research > >