From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: OpenVPN transfer net changes in Core Update 70
Date: Thu, 04 Jul 2013 13:44:52 +0200 [thread overview]
Message-ID: <1372938292.15464.34.camel@rice-oxley.tremer.info> (raw)
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Hello,
in Core Update 70, we will ship some changes that affect OpenVPN N2N
connections. In order to have a smooth transition to what users might
need to take care of, I created a small technical guide about that.
Could you guys please review it and make improvements if any are needed.
After that it would be great if someone has the time to create the
translations.
http://wiki.ipfire.org/en/updates/start
http://wiki.ipfire.org/en/updates/openvpn-transfer-net-block
Thanks in advance!
-Michael
reply other threads:[~2013-07-04 11:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1372938292.15464.34.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=documentation@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