 Re: Client side translation/routing?
If you've got client-side NAT turned on (the default) it does the NAT first, then makes a routing decision based on the translated destination.
This makes life easy.
If you turn it off, it makes a routing decision based on the address before it's done any NATting - so you end up having to put a whole lot of /32 routes in for your NATs.
Use "translate on client side", it makes your life much easier. I can't think why you would do it the other way, unless you've upgraded a 4.1 system, and stupidity^Winertia has stopped you changing it. |