Tom Sightler wrote:
> I disagree, it would take only a few lines to address the OP's request
(traffic that comes in on one interface goes out on the same interface)
with policy routing, especially since he states that the device does not
do any routing. That means that any inbound traffic to that server has
to be directed to the IP address of the interface, and thus the
responses will need to come from the IP address on which the connection
is made.
Tom, you're going to wake up in the morning and wonder what the heck
it was you were thinking. (Or maybe I will.) If the box does not
serve as a router, then policy routing is a complete non-starter.
Think about it. The only reason for traffic to come into this box, is
to interact with some application there. Then the OS needs to know
how to route the REPLY traffic. It doesn't know what interface the
http request came in on, for example. It isn't the same traffic going
out!
Policy routing would allow you to use a "default route" for all
connections that came in on the external interface, and a completely
separate "default route" for connections that came on the internal
interface, all without knowing anything but IP addresses of the gateways
on each interface.
No, absolutely not. You are describing a router. Guess we'll have to
agree to disagree...
-Ed
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
