YES! It was the algorithms! I finally got a tunnel! I have no idea which specific algorithm it was that was missing, I just enabled a bunch of them, but most likely AES, which I guess is the de facto standard for symmetric cryptography rather than DES. By the way, where do I see which algorithms are being negotiated? I could see them only after the connection succeeded by using ipsec statusall, in the security association section, that was empty before when it failed.
Thanks again for all your prompt and clear replies! Next I guess I will see if something can be done to make this work with IPv6 and with certificates rather than username and password. So I am sorry, but you will probably hear a lot from me again :) Federico -----Opprinnelig melding----- Fra: Tobias Brunner [mailto:[email protected]] Sendt: 26. oktober 2011 16:04 Til: Mancini, Federico Kopi: [email protected] Emne: Re: [strongSwan] Strongswan on android gingerbread Hi Federico, > What else could it be? (just as a note I have note enabled anything > extra with the cryptographic API modules. ) It could very well be a problem with the algorithms. Which algorithms are negotiated between the two hosts? Did you configure anything special on the responder? Regards, Tobias _______________________________________________ Users mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/users
