From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: Status emails and IP Blocklists Date: Sat, 01 Dec 2018 21:18:43 +0100 Message-ID: <9ebbbe98-98a8-03af-9de4-f2e5ff999fce@link38.eu> In-Reply-To: <1c66503b47593dd61f22167c559fe81cde60bf5c.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3264783945643983737==" List-Id: --===============3264783945643983737== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit 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 --===============3264783945643983737==--