Date: Tue, 18 Jul 2006 11:30:50 -0400 From: "Andy Greenwood" <greenwood.andy@gmail.com> To: "Free BSD Questions list" <freebsd-questions@freebsd.org> Subject: Re: Adding a (non default) route via rc.conf Message-ID: <3ee9ca710607180830o538c9d45p98bbc87ef7ab09c1@mail.gmail.com> In-Reply-To: <20060718152444.GA23912@teddy.fas.com> References: <20060718152444.GA23912@teddy.fas.com>
next in thread | previous in thread | raw e-mail | index | archive | help
in rc.conf, put something like this: static_routes="legacy" route_legacy="-net 192.168.2 192.168.1.150" the static_routes line is a list of network names that you want to put routes in for, then each name gets its own route_name line. As for your sanity check, I don't see why it would be a problem. On 7/18/06, stan <stanb@panix.com> wrote: > What's th sytax for addid a static (non default) route via rc.conf? > > And while I'm here, how about a sanity check to make certain this is really > what I want to do. > > Historicaly, the machine in question has lived on a network with only one > gateway off that net. Now, as part of a transition, I'm changing the > default route to point to a new address, but the old (ex default troute > machine) still is the only way to certain legacy networks. > > > Is this the best way to handle this? > > -- > U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror > - New York Times 9/3/1967 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ee9ca710607180830o538c9d45p98bbc87ef7ab09c1>