From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: OpenVPN - Path MTU Discovery
Date: Thu, 15 Nov 2012 22:58:55 +0100 [thread overview]
Message-ID: <1353016735.1735.49.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <50A3FD89.4000005@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
Hey Stefan,
I reviewed the code in your git repository, because looking at diffs is
much easier.
Key 32 is used in the CCD patch and the MTU-DISC patch, so please move
your key to at least number 38, so we won't have any conflicts here.
Rest looks good but needs some testing to be merged.
Michael
On Wed, 2012-11-14 at 21:22 +0100, Stefan Schantl wrote:
> Dear Mailinglist Followers,
>
> I've implemented the option to configure "Path MTU Discovery" for OpenVPN.
> This can be done by using the Web-Userinterface, and is available for
> Roadwarrior and Net-to-Net connections.
>
> To get this cool feature into the main distribution we need more
> feedback from testes, so I've attached the files to this announcement.
>
> Just download them and place the ovpnmain.cgi into your
> "/srv/web/ipfire/cgi-bin/" directory.
> The language files have to be copied to the "/var/ipfire/langs" directory.
>
> At the end, the language cache have to be updated by using the following
> command:
>
> perl -e "require '/var/ipfire/lang.pl'; &Lang::BuildCacheLang"
>
> NOTE - Always create a backup of your existing files!
>
> Please test and phone back any problems or errors.
>
> Best regards,
>
> Stefan
>
>
>
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
parent reply other threads:[~2012-11-15 21:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <50A3FD89.4000005@ipfire.org>]
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=1353016735.1735.49.camel@rice-oxley.tremer.info \
--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