public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: Status emails and IP Blocklists
Date: Sat, 01 Dec 2018 21:18:43 +0100	[thread overview]
Message-ID: <9ebbbe98-98a8-03af-9de4-f2e5ff999fce@link38.eu> (raw)
In-Reply-To: <1c66503b47593dd61f22167c559fe81cde60bf5c.camel@ipfire.org>

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

Hello Tim, hello Michael,

> 
>> The second addon handles the setting up and updating of IP Address
>> Blocklists in the firewall.  It includes options to select which lists
>> to use, and some control over how frequently to check for updates.
> 
> I guess Peter might be quite excited about this :)
I _am_ excited about this indeed. Especially the "Emerging FW" combined
list sounds very interesting. Dropping bogon traffic is also a good
idea, as it prevents some hijacked BGP allocation stuff.

> 
> I personally do not have much use for this, but again, why should this not
> become part of IPFire?
> 
@Michael: Why do you have no use for this? Speaking about the mentioned
Emerging FW list, enabling it as a default sounds reasonable to me. Networks
listed there usually are so bad one even does not want to route or peer
to it (DROP = Don't route or peer). :-)

Could we enable the bogon list as a default for dial-up interfaces in
IPFire 3.x ?

Thanks, and best regards,
Peter Müller
-- 
Microsoft DNS service terminates abnormally when it recieves a response
to a DNS query that was never made.  Fix Information: Run your DNS
service on a different platform.
		-- bugtraq

       reply	other threads:[~2018-12-01 20:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1c66503b47593dd61f22167c559fe81cde60bf5c.camel@ipfire.org>
2018-12-01 20:18 ` Peter Müller [this message]
2018-12-02 11:12   ` Michael Tremer
2018-12-02 12:08     ` Peter Müller
2018-12-02 12:10       ` Michael Tremer
     [not found] <c4c6137e-5f6a-8ee7-c36e-8deded18f28a@tfitzgeorge.me.uk>
2019-04-01 11:07 ` Michael Tremer
     [not found] <745dc6bc-4ac4-8b43-415b-17c35d2fb219@tfitzgeorge.me.uk>
2018-12-01 19:46 ` Michael Tremer
2018-11-29 21:11 Tim FitzGeorge

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=9ebbbe98-98a8-03af-9de4-f2e5ff999fce@link38.eu \
    --to=peter.mueller@link38.eu \
    --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