From owner-freebsd-questions@freebsd.org Wed Jan 18 17:17:50 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30A5ACB6C6A for ; Wed, 18 Jan 2017 17:17:50 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from webmail.dweimer.net (24-240-198-187.static.stls.mo.charter.com [24.240.198.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.dweimer.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 069F016E1 for ; Wed, 18 Jan 2017 17:17:49 +0000 (UTC) (envelope-from dweimer@dweimer.net) Received: from www.dweimer.net (localhost [10.9.5.2]) by webmail.dweimer.net (8.15.2/8.15.2) with ESMTP id v0IGtWO3075452 for ; Wed, 18 Jan 2017 10:55:32 -0600 (CST) (envelope-from dweimer@dweimer.net) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 18 Jan 2017 10:55:32 -0600 From: "Dean E. Weimer" To: FreeBSD Questions Subject: Tuning Route Cache Organization: dweimer.net Reply-To: dweimer@dweimer.net Mail-Reply-To: dweimer@dweimer.net Message-ID: X-Sender: dweimer@dweimer.net User-Agent: Roundcube Webmail/1.3-beta X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2017 17:17:50 -0000 I have been searching, but so far unsuccessfully found any hints. I have a situation that occurred with a FreeBSD server that is running 11.0 that is in a DMZ with its default router directing traffic to other routers in the same subnet. we had one of those routers get swapped out last night. however the FreeBSD server still had the old router in its cache, and couldn't communicate with the remote sites. Example FreeBSD servers IP: 192.168.1.10 default gateway 192.168.1.1 route to 10.10.10.1/24 via 192.168.1.2 route to 10.10.20.1/24 via 192.168.1.3 the route to 10.10.20.1/24 was change to go through 192.168.1.4 around 10 pm last night as of 9am this morning the freebsd server still had cached route entries pointing the 10.10.20.1/24 devices through 192.168.1.3 instead of retrying the default route to receive the updated path. I need to find a way to shorten this cache, I understand why its there to prevent repeated lookups, this doesn't happen all the time but I am thinking if I could change this cache length to a couple of hours this would have saved me a lot of trouble. As the routes would have cleared out over night and when users got back on the network in the morning everything would have been working. Of course it would have also helped had the admin working with the provider informed me they were making a change, but somehow I don't think FreeBSD can solve that one for me. -- Thanks, Dean E. Weimer http://www.dweimer.net/