From owner-freebsd-current@FreeBSD.ORG  Tue Jun 19 10:12:12 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 7227716A474
	for <freebsd-current@freebsd.org>; Tue, 19 Jun 2007 10:12:12 +0000 (UTC)
	(envelope-from ianf@clue.co.za)
Received: from munchkin.clue.co.za (munchkin.clue.co.za [66.219.59.160])
	by mx1.freebsd.org (Postfix) with ESMTP id 40FE213C4B7
	for <freebsd-current@freebsd.org>; Tue, 19 Jun 2007 10:12:12 +0000 (UTC)
	(envelope-from ianf@clue.co.za)
DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=20070313; d=clue.co.za;
	h=Received:Received:Received:To:From:Subject:In-Reply-To:X-Attribution:Date:Message-Id;
	b=kZuJru56uJJVOc4nUB+zkwrcrLkfUeETpB0gyEqk1Vo2d8GTavJJd5LQOQ35WcLakNsGnEXel7ADSjWVfh+zcyWdkntXZ+skPHEp9P8+ZPwhGCWaVsjrVUbEd8J79uRvRYOjw0lioWDJnxei5G9y06jMqRu7wgh/Cr9bH82P0ZNCdtzpumcKanidj7Vc09u2u8sJQp7vg1tCPNKJmB6ECDRmt8vqcDp/txXTdVTyB4Hk2G84i+hwjkLwMtm9U0Tw;
Received: from uucp by munchkin.clue.co.za with local (Exim 4.66)
	(envelope-from <ianf@clue.co.za>)
	id 1I0agz-0004cn-J1; Tue, 19 Jun 2007 10:12:09 +0000
Received: from atlas.clue.co.za ([10.0.0.18] helo=clue.co.za)
	by urchin.clue.co.za with esmtpa (Exim 4.66)
	(envelope-from <ianf@clue.co.za>)
	id 1I0agB-0001gl-V9; Tue, 19 Jun 2007 10:11:20 +0000
Received: from localhost ([127.0.0.1] helo=clue.co.za)
	by clue.co.za with esmtp (Exim 4.67 (FreeBSD))
	(envelope-from <ianf@clue.co.za>)
	id 1I0agA-0000N9-Um; Tue, 19 Jun 2007 12:11:18 +0200
To: "Sepherosa Ziehau" <sepherosa@gmail.com>,
	"Rui Paulo" <rpaulo@fnop.net>, freebsd-current@freebsd.org
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: Message from Ian FREISLICH <ianf@clue.co.za> 
	of "Tue, 19 Jun 2007 07:12:56 +0200."
X-Attribution: BOFH
Date: Tue, 19 Jun 2007 12:11:18 +0200
Message-Id: <E1I0agA-0000N9-Um@clue.co.za>
Cc: 
Subject: Re: ath(4) problems after sam_wifi merge 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2007 10:12:12 -0000

Ian FREISLICH wrote:
> I'm not sure when this commit was made.  My last build was done on
> Saturday.  Further investigation shows that it's dhclient renewing
> leases.  Sometimes it gets the new lease, but then stops working.
> I'll fetch and build a more recent current today and see how it
> goes.

Replying to myself, it seems that when the DHCP lease is renewed,
the ARP table becomes stale in some fashion:

[apple] /usr/home/ianf $ arp -an
? (10.0.0.1) at 00:0e:0c:6b:25:5e on ath0 [ethernet]
? (10.0.0.20) at 00:0f:3d:a9:98:c4 on ath0 [ethernet]
? (10.0.0.220) at 00:16:17:7d:c5:b0 on ath0 [ethernet]
? (10.0.0.255) at ff:ff:ff:ff:ff:ff on ath0 permanent [ethernet]

10.0.0.1 is my gateway.

After a lease renewal the arp table looks exactly the same as above,
yet I am unable to reach 10.0.0.1.  If I manually delete the arp
entry, then I can once again reach that host.

Ian

--
Ian Freislich