From owner-freebsd-current@FreeBSD.ORG Thu Sep 8 22:13:08 2005 Return-Path: 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 C0A6216A41F for ; Thu, 8 Sep 2005 22:13:08 +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 4530643D49 for ; Thu, 8 Sep 2005 22:13:08 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by ngwee.ugcs.caltech.edu (Postfix, from userid 3640) id 7A858CC071; Thu, 8 Sep 2005 15:13:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ngwee.ugcs.caltech.edu (Postfix) with ESMTP id 4739ABD0A5; Thu, 8 Sep 2005 15:13:07 -0700 (PDT) Date: Thu, 8 Sep 2005 15:13:07 -0700 (PDT) From: Jon Dama To: Brooks Davis In-Reply-To: <20050908214834.GA8000@odin.ac.hmc.edu> Message-ID: References: <20050901225346.0923E16A41F@hub.freebsd.org> <200509072128.04819.incmc@gmx.de> <20050907194130.GA2436@odin.ac.hmc.edu> <200509072223.20560.incmc@gmx.de> <20050907211811.GA19570@odin.ac.hmc.edu> <20050908214834.GA8000@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Jochen Gensch , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2005 22:13:08 -0000 > > > > And whenever there is a wireless network available (where the system can log > > > > in an get a network connection) the default route should be switched to that > > > > wireless nic. Or even better, if both connections work, automatically choose > > > > the faster one :-). > > > > > > That's the goal we're headed towards. Unfortunatly, it's not an instant > > > thing, particularly when people trying things like what you're doing > > > that don't map well into the old world view of static devices that don't > > > change networks. The old model is wrong and has been so for quite some > > > time, but that doesn't mean there aren't assumptions related to it all > > > over the place. > > > > Again, the problem is with the routing code. You should NOT need to be > > deleting default routes simply because one link goes down and another > > comes up on a different interface. > > > > Deleting the route simply because the interface went down is a hack. > > Got a new routing implemention handy? Until then, well have to live > with hacks. :( True enough. I think the general idea is that you need a two layer routing table. One that keeps tract of what is possible, and one that keeps track of what is happening w.r.t existing flows. Once an interface link goes down, the route in the second table invaliadates and you go back to the first to find a new route. afaik, this is what is done in SunOS, on cisco hardware... MS might do it too, certainly their handling of default routes meshes well with the wireless world. Some discussion of this on the dragonfly lists a while back. I don't know if anything became of it: http://leaf.dragonflybsd.org/mailarchive/kernel/2003-10/msg00079.html