Tom Sightler wrote:
On Fri, 2008-07-25 at 08:17 -0600, Ed Brown wrote:
There can't be two 'default routes'. I think
static routes are the only way to accomplish this.
...
however, by using policy based routing, you can add
significantly more complex logic to this decision.
Well you got me there, saying 'only way' was just asking for trouble.
But policy routing is hardly a practical answer to the OP's
question. And it's really a semantic stretch to say that policy
routing is a way of having multiple "default routes". You can only
have one "default route", period. If you have multiple defined
routes, whether static or 'policy' based, they aren't "defaults", you
are explicitly configuring them, whatever the criteria (source ip,
dest ip, etc).
Some of the simplest options are simply to have two "default routes"
based on the source IP address. That way, a service on bound to one
address would use one "default route" and a service bount to another IP
address would use a different "default route".
Binding applications to particular interfaces really hasn't anything
to do with routing. And you still have to configure routing to
non-local networks for the application to be able to communicate with
them. Again, you can NOT have more than one "default route".
-Ed
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
