From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Roadwarrior IPSec Revisitec
Date: Mon, 10 Dec 2018 19:16:00 +0000 [thread overview]
Message-ID: <9DC6DCF5-DC52-420A-9ACD-4209977EEE2D@ipfire.org> (raw)
In-Reply-To: <182A6807-0C08-41FA-8167-C7A006A19162@rymes.com>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
Hey Tom,
I am also quite frustrated about this. IPsec as a protocol is working well, but 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 IPFire 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 has already been put into that.
However, my time is very limited at the moment and unfortunately I am very busy dealing with loads of other things in this project. Therefore progress has been … slow. So everyone who can contribute and help out so that more free time is available will be greatly appreciated of course.
-Michael
prev parent reply other threads:[~2018-12-10 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 1:20 Tom Rymes
2018-12-10 1:22 ` Tom Rymes
2018-12-10 19:16 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9DC6DCF5-DC52-420A-9ACD-4209977EEE2D@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox