From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] New structure for the IPSec Wiki
Date: Tue, 24 Apr 2012 13:12:51 +0200 [thread overview]
Message-ID: <57CC1DFF-4309-49E3-A0A8-3932C8001CB1@ipfire.org> (raw)
In-Reply-To: <4F9677F4.5030508@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2426 bytes --]
Hi Daniel,
o.k. i started now with the IPSec wiki´s new structure and made some subcategories. I have copied the actual information from the orig wiki in the new structure, also i tried to collect some other how-to´s from other users (L2TP with IPSec). So take a look for the first try --> http://wiki.ipfire.org/nonpublic/de/configuration/services/ipsec
I think there can be some more info´s/screenies, etc. in it for example i think the Roadwarrior needs some fixes and may some additional knowledge.
Erik
Am 24.04.2012 um 11:52 schrieb Daniel Weismüller:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Erik,
>
> I think it would be fine if we have one ipsec wiki with subcategories
> like "ipsec with ios", etc.
>
> Daniel
>
> Am 23.04.2012 15:47, schrieb Erik K.:
>> Hi all,
>>
>> regarding to the newest changes in the IPSec wiki -->
>> http://wiki.ipfire.org/de/configuration/services/ipsec/ios it might
>> be an idea to bring a new structure for the IPSec wiki up. There
>> are also another part for L2TP with IPSec at this time only in NON
>> Public area --> http://wiki.ipfire.org/nonpublic/l2tp . What are
>> you thinking about to keep all informations together in a new
>> structure ?
>>
>> Greetings
>>
>> Erik
>>
>> _______________________________________________ Documentation
>> mailing list Documentation(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/documentation
>
> - --
> __________________________________________
>
> You need a firewall?
> Easy to use? Powerful? Modular? For free?
>
> www.ipfire.org
> An Open Source Firewall Solution
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJPlnf0AAoJEFHacdtWfTAWcuYH/iAaEppXdQK3bQnpxJPx4cUp
> YKU/LrGeWQC6kCv+KPDHpeqwuRRSmfaYgK8/WQE8IKIcx1DpYKo9fiMszE3PYESn
> oSkzhjKuAZnN8Cc1+WYS/tr2eFoL3ZSxOYKOJ41csUJqXJ5VG+6PrVrbOioKrRd2
> Shgz2kB9Yk4+PdEIuon1RYnIrmPN5LcGLlzDm7D54xYb+mUjN950AdjOxUQ1qq2l
> Hi/VhPDoZ9ggpbDRXelxMoV4qI7ORwFooZw+IbEQ6hZxbcyKYhtERnln6dnPS8mC
> 0PBWSdSX6Rh0fCQgbkfDwvZWDh+54i1nrGCBEIQfi5HQADbVZll3szuV8ZBWF4I=
> =AQ++
> -----END PGP SIGNATURE-----
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
prev parent reply other threads:[~2012-04-24 11:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 13:47 Erik K.
2012-04-24 9:52 ` Daniel Weismüller
2012-04-24 11:12 ` Erik K. [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=57CC1DFF-4309-49E3-A0A8-3932C8001CB1@ipfire.org \
--to=ummeegge@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