public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: ue <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: IPset and Firewall documentation
Date: Wed, 11 Nov 2015 09:39:57 +0100	[thread overview]
Message-ID: <F9B64B9E-8EFE-47AF-8A75-B9A19B931819@ipfire.org> (raw)
In-Reply-To: <1446914329.2401.1.camel@ipfire.org>

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

Hi Michael,
have added the IPset wiki now under "Related" section in the firewall documentation --> http://wiki.ipfire.org/en/configuration/firewall/start .

Hi all,
it might be great if you can go for a correction reading, you can find the wiki in here --> http://wiki.ipfire.org/en/configuration/firewall/ipset. If you think there should be something changed or missing, please let it me know or change it by your own.

Greetings,

Erik

Am 07.11.2015 um 17:38 schrieb Michael Tremer:

> I think it should be a subpage of the firewall documentation because
> this is obviously a part of the firewall. And on the main firewall page
> where all the links are it should be somewhere at the bottom.
> 
> I do not really want to encourage many people to use this, because I
> think that we have many other options and I am not sure about the
> quality of the blacklists and so on. That is why I won't give this such
> a high priority.
> 
> Best,
> -Michael
> 
> On Sat, 2015-11-07 at 16:15 +0100, ue wrote:
>> Hi Michael and Matthias,
>> you are probably wright. Should i take the IPset wiki into the
>> optimizations section or do you both have a better idea ? To
>> configure IPset we will need also some entries in firewall.local...
>> 
>> Michael, what are you thinking about the link for the firewall
>> documentation on the wiki main page ?
>> 
>> Greetings,
>> 
>> Erik
>> 
>> 
>> Am 07.11.2015 um 14:37 schrieb Michael Tremer:
>> 
>>> I think this is a pretty advanced thing and probably not many
>>> people
>>> will use this. Hence it does not make too much sense to have it at
>>> the
>>> start of the configuration page. It is probably only interesting
>>> for
>>> people who are explicitly searching for "ipset".
>>> 
>>> -Michael
>>> 
>>> On Sat, 2015-11-07 at 07:24 +0100, Matthias Fischer wrote:
>>>> Hi,
>>>> 
>>>> On 07.11.2015 07:11, ue wrote:
>>>>> ...I ask myself again if it is may a good idea to place a link
>>>>> for
>>>> the firewall documentation at the wikis first page in here 
>>>> -->https://wiki.ipfire.org/en/start  cause of it´s importance but
>>>> also 
>>>> to leave it in the configuration section.
>>>>> ...
>>>> 
>>>> I agree with you.
>>>> 
>>>> I think especially for beginners, it would be handy if the
>>>> documentation 
>>>> link(s) can easily be found.
>>>> 
>>>> Best,
>>>> Matthias
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Documentation mailing list
>>>> Documentation(a)lists.ipfire.org
>>>> http://lists.ipfire.org/mailman/listinfo/documentation
>> 
>> _______________________________________________
>> Documentation mailing list
>> Documentation(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/documentation


      reply	other threads:[~2015-11-11  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07  6:11 ue
2015-11-07  6:24 ` Matthias Fischer
2015-11-07 13:37   ` Michael Tremer
2015-11-07 15:15     ` ue
2015-11-07 16:38       ` Michael Tremer
2015-11-11  8:39         ` ue [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=F9B64B9E-8EFE-47AF-8A75-B9A19B931819@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