From owner-freebsd-questions@FreeBSD.ORG Mon Apr 11 01:27:20 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A225316A4CE; Mon, 11 Apr 2005 01:27:20 +0000 (GMT) Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E57C43D49; Mon, 11 Apr 2005 01:27:20 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98])j3B1RINn077939; Sun, 10 Apr 2005 18:27:18 -0700 (PDT) Date: Mon, 11 Apr 2005 10:27:17 +0900 Message-ID: From: gnn@FreeBSD.org To: Sergey Matveychuk In-Reply-To: <42590AB3.3070106@FreeBSD.org> References: <42590AB3.3070106@FreeBSD.org> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3.50 (powerpc-apple-darwin7.7.0) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII cc: questions@FreeBSD.org cc: net@FreeBSD.org Subject: Re: route entries after ICMP redirect X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2005 01:27:20 -0000 At Sun, 10 Apr 2005 15:14:59 +0400, Sergey Matveychuk wrote: > > I've got some problem with route entries that was created after ICMP > redirect messages. They are never expired. > > Our default gateway (it's a HP switch) send ICMP redirect messages if it > see a short path to destination. It's makes it not so overloaded. But > pathes sometime changed. There is no problem with Windows workstations, > they are rebooted daily. But my FreeBSD boxes hold dinamic route entries > forever. > > I've looked through RFCs and Stevens' books and found no answer on what > TTL for this entries. > Now I just add route flush as cron job. But may be there is another way? Routes set through the redirect path do not have a timeout associated with them. The redirect message usually implies an error in the network setup of your machines which would have to be handled by a human being changing the configuration. If you want to handle this in a more clever way than a cron job you could write a small daemon which reads routing messages and does "the right thing" for whatever your situation is. Later, George