On Fri, 2002-06-07 at 08:21, Stephen Torri wrote: > The only information that I heard about IPSec is that it cannot be NAT. > IPs on both ends must remain what they are during the connection. This > is not official or confirmed information. Just what I heard second hand. > So the two end points I believe they were trying to imply should be the > client and the firewall (if you are using NAT ofcourse).
This is true, but only if your IPSec stack does authentication (the AH protocol IIRC). Basically, this protocol does a checksum on the packets, including the source IP address. Therefore a NAT router/firewall will change the source IP address, but it can't touch the checksum, so the destination system will reject the packet because "it has been altered in transit". Some IPSec implementations allow you to disable AH in order to circumvent this problem, but you lose a lot of the IPSec's security. There are other alternatives in this type of scenario: 1. Make your router/firewall the IPSec gateway. 2. Use a TCP based VPN software (i.e.: vtund or ssh) Cheers., -- Javier Gostling Ingeniero de Sistemas Virtualia S.A. [EMAIL PROTECTED] Fono: +56 (2) 202-6264 x 130 Fax: +56 (2) 342-8763 Av. Kennedy 5757, of 1502 Las Condes Santiago Chile _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
