From owner-freebsd-current@FreeBSD.ORG  Thu Sep  8 21:45:45 2005
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 [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8599F16A41F
	for <freebsd-current@freebsd.org>; Thu,  8 Sep 2005 21:45:45 +0000 (GMT)
	(envelope-from jd@ugcs.caltech.edu)
Received: from ngwee.ugcs.caltech.edu (ngwee.ugcs.caltech.edu
	[131.215.176.116])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EF17F43D53
	for <freebsd-current@freebsd.org>; Thu,  8 Sep 2005 21:45:44 +0000 (GMT)
	(envelope-from jd@ugcs.caltech.edu)
Received: by ngwee.ugcs.caltech.edu (Postfix, from userid 3640)
	id 18D7ECC071; Thu,  8 Sep 2005 14:45:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by ngwee.ugcs.caltech.edu (Postfix) with ESMTP
	id BE802BD0A5; Thu,  8 Sep 2005 14:45:43 -0700 (PDT)
Date: Thu, 8 Sep 2005 14:45:43 -0700 (PDT)
From: Jon Dama <jd@ugcs.caltech.edu>
To: Lars Erik Gullerud <lerik@nolink.net>
In-Reply-To: <20050908220217.X64137@electra.nolink.net>
Message-ID: <Pine.LNX.4.53.0509081443080.18161@ngwee.ugcs.caltech.edu>
References: <20050901225346.0923E16A41F@hub.freebsd.org>
	<200509021003.39863.incmc@gmx.de>
	<20050902164957.GA22097@odin.ac.hmc.edu>
	<200509072128.04819.incmc@gmx.de>
	<20050907194130.GA2436@odin.ac.hmc.edu>
	<20050908220217.X64137@electra.nolink.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: freebsd-current@freebsd.org
Subject: Re: Default route doesn't change to wireless device (ath0)
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: Thu, 08 Sep 2005 21:45:45 -0000


> Bringing an interface down then back up is usually one of the "try this
> first" operations when troubleshooting all platforms I normally work on,
> exactly because it _does_ (normally) clear a lot of state info that you
> don't want around to confuse you (like the ARP cache and routing table
> entries).

Yes but surely you'd recognize a difference between a link state change
and issuing ifconfig ... down

In the latter case, I expect state to be flushed.  In the former, I expect
everything to resume when the link is restored.  Imagine having to
manually reinit your interfaces just because some joker temporary
unplugged your ethernet cable!