I've got a tunnel between FreesWAN (Linux) and ipsec.exe (WIN2000) (OR SENTINEL 1.4 - the same problem) and problem with PING behind NAT. If I have public IP adress everyting is SUPER OK but from local IP after NAT (Client) my ping do not go over NAT PC :( In both causes (with and within NAT) Tunnel is ESTABLISHED but from NAT the packet loose on this NAT pc. Looking to packets on NAT device I receive IP-SIPP packet but in my opinion there should UDP packet (when nat is turned on). If my NAT device is windows pc with LAN from IpsecClient and DialUp connection to the FreeSwan server I receive packets on LAN (IP-SIPP) but no one packet goes through DialUp interface. So in my opinion problem is with NAT device. So: I do not receive any packet on Freeswan server from Client instead of whole process while establishing connection.
Situation: [FreeSWAN] <internet> [IpSec Client] -- everytging is OK. [FreeSWAN] <internet> [NAT] [IpSec Client] -- ping NOT OK :( but ipsec connection is established correctly (QUICK & MAIN MODE) Freeswan version 2.0 with x.509 + NAT-T patch In log everything seems to be ok: .. (config)nat_traversal=yes (log) NAT-Traversal: Result using draft-ietf-ipsec-nat-t-ike-02/03: peer is NATed but what can be wrong ??? PLEASE, HELP ME ... Sawo _______________________________________________ FreeS/WAN Users mailing list [EMAIL PROTECTED] https://mj2.freeswan.org/cgi-bin/mj_wwwusr
