Date: Thu, 8 Sep 2005 14:45:43 -0700 (PDT) From: Jon Dama <jd@ugcs.caltech.edu> To: Lars Erik Gullerud <lerik@nolink.net> Cc: freebsd-current@freebsd.org Subject: Re: Default route doesn't change to wireless device (ath0) Message-ID: <Pine.LNX.4.53.0509081443080.18161@ngwee.ugcs.caltech.edu> In-Reply-To: <20050908220217.X64137@electra.nolink.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.53.0509081443080.18161>