Date: Mon, 20 Jun 2011 17:18:39 -0600 From: Elliot Finley <efinley.lists@gmail.com> To: Jon Radel <jon@radel.com> Cc: freebsd-questions@freebsd.org Subject: Re: Two Networks on one System Message-ID: <BANLkTinZBRPy=oafWM03_36rT9eqY_ZoRw@mail.gmail.com> In-Reply-To: <4DFFD0A7.8010806@radel.com> References: <201106202107.p5KL7PW0091851@x.it.okstate.edu> <4DFFC61B.2080201@radel.com> <27899_1308609017_4DFFC9F9_27899_767_1_D9B37353831173459FDAA836D3B43499BF89C588@WADPMBXV0.waddell.com> <4DFFD0A7.8010806@radel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 20, 2011 at 4:58 PM, Jon Radel <jon@radel.com> wrote: > > On 6/20/11 6:30 PM, Gary Gatten wrote: > >> I was kinda going this route as well - policy based routing type thing, >> but, is there an "easier" way? > > Not that I know of given a constraint of completely disjoint networks. > However, I won't be too terribly surprised if somebody comes up with > something elegant that makes us all go, "Ooooooo, what a disgustingly neat > hack." If it's two completely disjoint networks, the two networks don't use overlapping IP space and the IP space on at least one of the networks is known, then just use standard routing. put in static routes for the known space and a default route on the other interface for the unknown space. If the two networks are using overlapping space, then the only way to differentiate the packets are which interface they came in... then you'll have to use a PF hack. Elliot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTinZBRPy=oafWM03_36rT9eqY_ZoRw>