public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] firewall: Allow traffic from multicast networks
Date: Wed, 26 Apr 2023 05:47:14 +0100	[thread overview]
Message-ID: <4EE84A19-8F5C-4959-9251-D612DEDDE795@ipfire.org> (raw)
In-Reply-To: <20230425184009.3674-1-stefan.schantl@ipfire.org>

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

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 25 Apr 2023, at 19:40, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> The multicast network segment 224.0.0.0/4 is used for a lot of
> different services provided by the local ISP's. (IPTV etc.)
> 
> We have to allow traffic from this networks when using one of
> the BOGON blocklists in order to get those ISP services still
> accessable.
> 
> https://www.iana.org/assignments/multicast-addresses/multicast-addresses.xhtml
> 
> Fixes 13092.
> 
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> config/firewall/rules.pl | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/config/firewall/rules.pl b/config/firewall/rules.pl
> index 6c08feb86..7edb910e2 100644
> --- a/config/firewall/rules.pl
> +++ b/config/firewall/rules.pl
> @@ -55,6 +55,7 @@ my @PRIVATE_NETWORKS = (
> "172.16.0.0/12",
> "192.168.0.0/16",
> "100.64.0.0/10",
> + "224.0.0.0/4",
> );
> 
> # MARK masks
> -- 
> 2.30.2
> 


      reply	other threads:[~2023-04-26  4:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 18:40 Stefan Schantl
2023-04-26  4:47 ` Michael Tremer [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=4EE84A19-8F5C-4959-9251-D612DEDDE795@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --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