From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/2] iptables: Do not ship libxt_ddcp.so
Date: Sat, 19 Mar 2022 22:54:12 +0100 [thread overview]
Message-ID: <fdc15e28-4cca-9b7e-6e08-a1a28182180b@ipfire.org> (raw)
In-Reply-To: <8d581c78-6627-58ee-b095-055b895a810d@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
Reviewed-by: Adolf Belka <adolf.belka(a)ipfire.org>
On 19/03/2022 16:32, Peter Müller wrote:
> DCCP (Datagram Congestion Control Protocol) is not in use by IPFire, not
> even available as a kernel module. Therefore, there is no sense in
> shipping this module, since it cannot do anything.
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/rootfiles/common/iptables | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/config/rootfiles/common/iptables b/config/rootfiles/common/iptables
> index b8bf748a5..559958b43 100644
> --- a/config/rootfiles/common/iptables
> +++ b/config/rootfiles/common/iptables
> @@ -86,7 +86,7 @@ lib/xtables/libxt_connlimit.so
> lib/xtables/libxt_connmark.so
> lib/xtables/libxt_conntrack.so
> lib/xtables/libxt_cpu.so
> -lib/xtables/libxt_dccp.so
> +#lib/xtables/libxt_dccp.so
> lib/xtables/libxt_devgroup.so
> lib/xtables/libxt_dscp.so
> lib/xtables/libxt_ecn.so
next prev parent reply other threads:[~2022-03-19 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 15:32 [PATCH 1/2] iproute2: Do not ship /sbin/tipc Peter Müller
2022-03-19 15:32 ` [PATCH 2/2] iptables: Do not ship libxt_ddcp.so Peter Müller
2022-03-19 21:54 ` Adolf Belka [this message]
2022-03-21 8:49 ` Michael Tremer
2022-03-19 21:52 ` [PATCH 1/2] iproute2: Do not ship /sbin/tipc Adolf Belka
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=fdc15e28-4cca-9b7e-6e08-a1a28182180b@ipfire.org \
--to=adolf.belka@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