From owner-freebsd-stable@FreeBSD.ORG Wed Aug 16 15:58:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59F6716A4DD; Wed, 16 Aug 2006 15:58:50 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B26843D4C; Wed, 16 Aug 2006 15:58:49 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id k7GFwk4t087378; Wed, 16 Aug 2006 19:58:46 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id k7GFwiws087377; Wed, 16 Aug 2006 19:58:44 +0400 (MSD) (envelope-from yar) Date: Wed, 16 Aug 2006 19:58:44 +0400 From: Yar Tikhiy To: Brooks Davis Message-ID: <20060816155844.GA85503@comp.chem.msu.su> References: <20060815040736.2f85f090.drl@MyBSD.org.my> <9405D801-3435-419A-9541-E1A9B2CF26D2@lassitu.de> <20060816081130.GB81271@comp.chem.msu.su> <20060816145419.GB62485@lor.one-eyed-alien.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060816145419.GB62485@lor.one-eyed-alien.net> User-Agent: Mutt/1.5.9i Cc: drl@MyBSD.org.my, brooks@freebsd.org, freebsd-stable@freebsd.org, Stefan Bethke , thompsa@freebsd.org Subject: Re: Default route (IPv4) demolished by destroying clone (gif/gre) interface 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: Wed, 16 Aug 2006 15:58:50 -0000 On Wed, Aug 16, 2006 at 09:54:19AM -0500, Brooks Davis wrote: > On Wed, Aug 16, 2006 at 10:23:13AM +0200, Stefan Bethke wrote: > > > > Ouch. Don't ppp(8), OpenVPN etc. destroy the tun interface they're > > using when they exit? Flushing all routes then would be rather > > harmful. I'm glad I haven't updated to a newer -stable yet then :-) > > In general, no since tun interfaces can not be destroyed. Did you mean "in particular"? :-) The problem can be triggered by destroying any interface that can be destroyed. Just imagine getting rid of a defunct gif tunnel on a remote router, or removing an unused vlan, and totally losing connectivity to the router due to its default route having been flushed. The scenario still can be quite unpleasant. I'd rather change the default for $removable_route_flush to NO and let the kernel choose which routes should be flushed upon the physical ejection or software destruction of an interface. Note that this doesn't include static_routes_${ifn}, which are handled separately by pccard_ether_stop(). -- Yar