From owner-freebsd-net@FreeBSD.ORG  Sun May 13 07:09:21 2012
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 968D2106564A
	for <net@freebsd.org>; Sun, 13 May 2012 07:09:21 +0000 (UTC)
	(envelope-from brett@lariat.net)
Received: from lariat.net (lariat.net [66.62.230.51])
	by mx1.freebsd.org (Postfix) with ESMTP id 3878D8FC12
	for <net@freebsd.org>; Sun, 13 May 2012 07:09:20 +0000 (UTC)
Received: from WildRover.lariat.net (IDENT:ppp1000.lariat.net@lariat.net
	[66.119.58.2] (may be forged))
	by lariat.net (8.9.3/8.9.3) with ESMTP id AAA00422
	for <net@freebsd.org>; Sun, 13 May 2012 00:50:52 -0600 (MDT)
Message-Id: <201205130650.AAA00422@lariat.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 13 May 2012 00:50:52 -0600
To: net@freebsd.org
From: Brett Glass <brett@lariat.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 
Subject: static_routes not working
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 13 May 2012 07:09:21 -0000

Everyone:

On a new 9.0 machine I tried using the variable static_routes (and 
corresponding route_XXX variables) to create static routes in 
/etc/rc.conf. Doesn't work at boot, though it does when 
/etc/netstart is run afterward. It appears that /etc/rc.d/routing, 
where the variable is processed, is not being executed at boot 
time. Have reproduced the same problem on 8.x machines as well. All 
have custom, IPv4-only kernels. What might be wrong?

--Brett Glass