Traffic is going to go to the defined default route if a specific route doesn't exist for it, so it depends how you have things configured.
*route print* will show what routes are currently defined and which is default (0.0.0.0) Traffic not destined for either 10.0.x.x or 128.125.x.x is going to take the default route. You probably want to make 128.125.n.y the default gateway if there is public access to this system. Jeff On Tue, Jun 2, 2009 at 1:01 PM, Salvador Manzo <[email protected]> wrote: > All, > Quick question showcasing why being self-taught isn't always the best > possible option. > > I have a situation where I will need to have multiple IPs on a server, > with most traffic going through a private VPN EXCEPT for a single > publicly addressable subnet. > > 10.0.0.1 Private Gateway > 10.0.x.x Range > > Public > 128.125.n.y Normal Public Gateway > 128.125.x.x Range > > In this situation, would > > ROUTE -p ADD 128.125.0.0 MASK 255.255.0.0 128.125.n.y METRIC 2 IF 2 > > put me in a place where all traffic NOT destined for the 128.125 IP > range would go through the private gateway, but all traffic on the > 128.125 range goes through the public gateway? > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
