public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. df6b9ebfbc36dd14de9159af1fbeab963c6dd7c9
Date: Thu, 27 Feb 2014 13:36:08 +0100	[thread overview]
Message-ID: <20140227123608.C772A20413@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  df6b9ebfbc36dd14de9159af1fbeab963c6dd7c9 (commit)
      from  c9cd26f2000a0f2218defca31faf6652740f9617 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit df6b9ebfbc36dd14de9159af1fbeab963c6dd7c9
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Feb 27 13:32:13 2014 +0100

    openvpn: Provide a basic set of configuration settings.
    
    These are the defaults as in the CGI script, but when you don't
    set up the roadwarrior server, the configuration file remains
    empty and the openvpnctrl binary will end itself because it cannot
    read a proper configuration.

-----------------------------------------------------------------------

Summary of changes:
 config/ovpn/settings | 6 ++++++
 1 file changed, 6 insertions(+)

Difference in files:
diff --git a/config/ovpn/settings b/config/ovpn/settings
index e69de29..b78fc32 100644
--- a/config/ovpn/settings
+++ b/config/ovpn/settings
@@ -0,0 +1,6 @@
+ENABLED=off
+ENABLED_BLUE=off
+ENABLED_ORANGE=off
+DDEST_PORT=1149
+DPROTOCOL=udp
+VPN_IP=


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2014-02-27 12:36 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=20140227123608.C772A20413@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@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