From owner-freebsd-stable@FreeBSD.ORG Mon Jun 20 05:59:00 2005 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 4102E16A41F; Mon, 20 Jun 2005 05:59:00 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCCB043D4C; Mon, 20 Jun 2005 05:58:58 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.172] (hac.vuokselantie10.fi [193.64.42.172]) by silver.he.iki.fi (Postfix) with ESMTP id 765F4BB42; Mon, 20 Jun 2005 08:58:55 +0300 (EEST) Message-ID: <42B65B5A.40005@he.iki.fi> Date: Mon, 20 Jun 2005 08:59:54 +0300 From: Petri Helenius User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Tancsa References: <51688.147.175.8.5.1119105461.squirrel@webmail.satronet.sk> <42B46C9B.7000206@mac.com> <200506190004.48066.vanco@satro.sk> <200506182214.33279.josemi@redesjm.local> <20050619082944.GA11972@cell.sick.ru> <6.2.1.2.0.20050619161035.03720998@64.7.153.2> In-Reply-To: <6.2.1.2.0.20050619161035.03720998@64.7.153.2> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Gleb Smirnoff , freebsd-stable@freebsd.org Subject: Re: Routes not deleted after link down 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: Mon, 20 Jun 2005 05:59:00 -0000 Mike Tancsa wrote: > > I like this idea as well, but you need to control how the routes would > come back after the interface comes back up ? This seems more of the > province of a routing daemon like quagga as opposed to a kernel > feature no ? The connected interface should try to transmit packets according to it's netmask when the interface is operational. So it should come back up "immediately". (at least when the mentioned sysctl is enabled) Pete