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: Sat, 07 Nov 2015 16:15:35 +0100	[thread overview]
Message-ID: <FA4E4572-0104-4C43-9D6B-469FE2A9EB0B@ipfire.org> (raw)
In-Reply-To: <1446903460.2587.7.camel@ipfire.org>

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

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


  reply	other threads:[~2015-11-07 15:15 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 [this message]
2015-11-07 16:38       ` Michael Tremer
2015-11-11  8:39         ` ue

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=FA4E4572-0104-4C43-9D6B-469FE2A9EB0B@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