From owner-freebsd-stable@FreeBSD.ORG Mon Nov 20 00:55:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C72F16A415 for ; Mon, 20 Nov 2006 00:55:29 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from alias2.ihug.co.nz (alias2.ihug.co.nz [203.96.222.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF77F43D55 for ; Mon, 20 Nov 2006 00:55:10 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: from ironport4.ihug.co.nz [203.109.254.24] by alias2.ihug.co.nz with esmtp (Exim 3.36 #1 (Debian)) id 1GlxP4-0000lj-00; Mon, 20 Nov 2006 13:52:54 +1300 Received: from 203-109-251-39.static.bliink.ihug.co.nz (HELO heff.fud.org.nz) ([203.109.251.39]) by ironport4.ihug.co.nz with ESMTP; 20 Nov 2006 13:58:52 +1300 X-Ironport-Seen: Yes Received: by heff.fud.org.nz (Postfix, from userid 1001) id 791D71CC29; Mon, 20 Nov 2006 13:55:20 +1300 (NZDT) Date: Mon, 20 Nov 2006 13:55:20 +1300 From: Andrew Thompson To: freebsd-stable@freebsd.org Message-ID: <20061120005520.GB79115@heff.fud.org.nz> References: <20061120004957.GA1270@seth.augenstein.ten> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061120004957.GA1270@seth.augenstein.ten> User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: 6.2-RC1 /boot/loader | dhclient X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 00:55:29 -0000 On Mon, Nov 20, 2006 at 01:49:57AM +0100, Norbert Augenstein wrote: > Hi list, > > i just want to note that after updating to RC1 /boot/loader > still refuses to boot with Grub. -> endless rebooting > chainloading works though, fortunately. > > dhclient shows a similar behavior to that Steve Franks reported > Nov 13 on -CURRENT. > After 20 min of inactivity the route gets flushed on my laptop, > calling dhclient wi0 from the command line remedies the problem > until it gets flushed again. > isc-dhclient does not exhibit this behavior, the route never gets > flushed. Linkstate handling is known to be broken in wi(4) which dhclient relies on, you may just have to use isc-dhclient. Andrew