On Sun, May 02, 2010 at 09:48:02AM -0400, Evgeny Yurchenko wrote: > Eugen Leitl wrote: > >I'm attempting to simulate a production network 88.198.238.112/28 > >with gateway 88.198.238.113 on the OPT1 interface (set to 88.198.238.113) > >but I'm too dense to figure out how override the default route, which sends > >the packet to WAN. > > > >I obviously need to do something along the lines of > >route add -net 88.198.238.112/28 88.198.238.113 > > > >Help? > > > > > Create two routes via web-interface: > 1. On OPT1 0.0.0.0/1 to 88.198.238.113
This basically means everything goes to 88.198.238.113. > 2. On OPT1 128.0.0.0/1 to 88.198.238.113 Can you explain what 128.0.0.0 is there for? > It will replace your default route to WAN. Thanks, Evgeny. Is there a less nuclear option? I would like to keep the rest of the routes unperturbed, so I can consult other online sources while working on the new systems. Is that feasible? I have 3 NICs: WAN, OPT1 and LAN. I've bound the new network to OPT1. The systems in the network do not necessarily need Internet access, but it would be a nice to have. -- Eugen* Leitl <a href="http://leitl.org">leitl</a> http://leitl.org ______________________________________________________________ ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org 8B29F6BE: 099D 78BA 2FD3 B014 B08A 7779 75B0 2443 8B29 F6BE --------------------------------------------------------------------- To unsubscribe, e-mail: discussion-unsubscr...@pfsense.com For additional commands, e-mail: discussion-h...@pfsense.com Commercial support available - https://portal.pfsense.org