-----BEGIN PGP SIGNED MESSAGE----- On Saturday 09 August 2003 19:43, Sven Schuster wrote: > Hello everybody, > > I'm quite new to ipsec and especially linxu freeswan (but not to > linux). I've spend some time reading about the ipsec protocolls > at first, to understand how everythings works. And now I'm about > to go from theory to practice. I've compiled my own kernel 2.4.21 > with super-freeswan 1.99.7.3 and some other patches (netfilter > p-o-m stuff, cipe, pptp). > In my first test I'd just like to connect two of my pcs on my > local network via an ipsec esp tunnel. The problem is, it just > doesn't work. When I ping machine #2 and do a tcpdump on the > second machine, I see the esp packets arriving there, but no reply > is sent out.
If you're getting to the stage where ESP packets are being sent, then I'd guess you've successfully established a tunnel. Read this mail re: troubleshooting packet flow problems. http:/lists.freeswan.org/pipermail/users/2003-March/019309.html (doc/trouble.html can also be helpful.) Don't forget that you can tcpdump the ipsec interface to see the clear traffic. I'd bet that your packets are getting snared by iptables rules. > Does anybody know what I'm getting wrong here?? Hope anybody > can help me, thanks for every pointer!!!! If some more information > is needed, I'll happily post it here! Post the output of "ipsec barf' from both sides to the web. It's a summary of (most of) the information needed to debug FreeS/WAN issues. - -- Sam Sgro [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv Comment: For the matching public key, finger the Reply-To: address. iQCVAwUBPzWwzEOSC4btEQUtAQHjyAP/U3UDbkemjivHt2Gh36W3GzXVzGUFiqlr E0UZu2xG9aWTa38bwHnwyeqdEBSUh2gxYDRtXc6BzGFZmdahFLoHNzpUGlmcQCn+ RA1vPnh3XZHFbJCbldwf/ADQQZmeEuiU8yKLRpfetgD0fuDwBu9os4/JLDtap7Zr KlnVqr0Hi8o= =t6MT -----END PGP SIGNATURE----- _______________________________________________ FreeS/WAN Users mailing list [EMAIL PROTECTED] https://mj2.freeswan.org/cgi-bin/mj_wwwusr
