From owner-freebsd-stable@FreeBSD.ORG Wed Aug 16 08:11:37 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 24DB016A4E5; Wed, 16 Aug 2006 08:11:37 +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 6D02C43D62; Wed, 16 Aug 2006 08:11:35 +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 k7G8BW5G081986; Wed, 16 Aug 2006 12:11:32 +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 k7G8BUfh081981; Wed, 16 Aug 2006 12:11:30 +0400 (MSD) (envelope-from yar) Date: Wed, 16 Aug 2006 12:11:30 +0400 From: Yar Tikhiy To: Stefan Bethke Message-ID: <20060816081130.GB81271@comp.chem.msu.su> References: <20060815040736.2f85f090.drl@MyBSD.org.my> <9405D801-3435-419A-9541-E1A9B2CF26D2@lassitu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9405D801-3435-419A-9541-E1A9B2CF26D2@lassitu.de> User-Agent: Mutt/1.5.9i Cc: drl@MyBSD.org.my, brooks@freebsd.org, freebsd-stable@freebsd.org, 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 08:11:37 -0000 On Tue, Aug 15, 2006 at 07:26:08PM +0200, Stefan Bethke wrote: > Am 14.08.2006 um 22:07 schrieb Darryl Yeoh: > > >While destroying gif interface, I notice it also removes IPv4 > >default route. Has anyone else > >encountered this ? > > No problem on a FreeBSD 6.1-STABLE #8: Fri Jun 16 17:15:03 CEST 2006. ^^^^^^ > > You don't happen to have any devfs rules that would cause this? As a matter of fact, the issue appeared in 6-STABLE on Jul 24 and is still there. Now devd(8) will invoke "/etc/pccard_ether stop" when any network interface is destroyed. In turn, pccard_ether will flush all -inet routes if the rc.conf(5) variable removable_route_flush is set to YES, which is its default setting. Previously, this scenario would take place only when an Ethernet interface was destroyed. The question is: Do all the routes really need to be flushed upon the destruction of an interface? Any ideas? -- Yar