From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Roadwarrior IPSec Revisitec Date: Mon, 10 Dec 2018 19:16:00 +0000 Message-ID: <9DC6DCF5-DC52-420A-9ACD-4209977EEE2D@ipfire.org> In-Reply-To: <182A6807-0C08-41FA-8167-C7A006A19162@rymes.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8235571721758320169==" List-Id: --===============8235571721758320169== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hey Tom, I am also quite frustrated about this. IPsec as a protocol is working well, b= ut getting client support working is indeed a PITA. However, this will be a huge job to get it to work better. There are loads of= hacks around and I am not sure what has been tested as working and what now. Right now, I am using OpenVPN for RW and IPsec for N2N connections. Although = OpenVPN has other issues, this is working quite well across multiple clients,= but always requires additional software to be installed. I would propose the following process: I would prefer to implement this in IP= Fire 3 first. That does not help much with running this right now, but it is = a good playing ground to build this properly and experiment. Loads of work ha= s already been put into that. However, my time is very limited at the moment and unfortunately I am very bu= sy dealing with loads of other things in this project. Therefore progress has= been =E2=80=A6 slow. So everyone who can contribute and help out so that mor= e free time is available will be greatly appreciated of course. -Michael --===============8235571721758320169==--