From: peter.mueller@ipfire.org
To: development@lists.ipfire.org
Subject: Re: Extremely poor OpenVPN performance, help wanted
Date: Tue, 29 Oct 2019 17:41:00 +0000 [thread overview]
Message-ID: <38b6b0bc-ab10-7b6d-a337-fbb30318f72f@ipfire.org> (raw)
In-Reply-To: <7E7947DC-3E0D-4102-9E78-38720BA958BF@rymes.com>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
Hello *,
just to ensure everybody is informed: This seems to be a FreeBSD
related problem, as a Debian machine using the same OpenVPN roadwarrior
configuration against the same IPFire instance did not suffer packet
loss.
Unfortunately, IPsec on FreeBSD using Strongswan does not work very
well either, as I could not figure out how to set the routes needed
(the actual IPsec tunnel is successfully established, but no traffic
will be routed through it). This leaves me with an operating system
whose VPN capabilities are not working or poorly documented... :-/
Anyway, IPFire does not do anything wrong here. Just thougt you might
want to know. :-)
Thanks, and best regards,
Peter Müller
prev parent reply other threads:[~2019-10-29 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 16:22 peter.mueller
2019-09-24 17:04 ` Tom Rymes
2019-09-25 19:13 ` peter.mueller
2019-09-26 3:21 ` Tom Rymes
2019-10-29 17:41 ` peter.mueller [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=38b6b0bc-ab10-7b6d-a337-fbb30318f72f@ipfire.org \
--to=peter.mueller@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