From: Florian Westphal <fw@strlen.de>
To: namniart@gmail.com
Cc: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Subject: Re: Duplicate invocation of NF_INET_POST_ROUTING rule for outbound multicast?
Date: Sat, 2 Nov 2024 17:12:17 +0100 [thread overview]
Message-ID: <20241102161217.GA13003@breakpoint.cc> (raw)
In-Reply-To: <0A676E07-BD16-492A-8C10-4FC541525F73@gmail.com>
namniart@gmail.com <namniart@gmail.com> wrote:
> Thanks for the quick reply; I will work through our build process and try to get that tested in the next few days.
>
> I was thinking the fix for this might be more substantial; call NF_HOOK without a callback at the top of ip_mc_output to determine the fate of the packet,
The NF_QUEUE verdict can delegate this decision to a userspace process,
if this happened its too late to do the clone.
So this would work only if we had a way to remove support for NF_QUEUE
for multicast packets. I don't think this can be done after two
decades.
prev parent reply other threads:[~2024-11-02 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 7:23 Duplicate invocation of NF_INET_POST_ROUTING rule for outbound multicast? Austin Hendrix
2024-10-31 21:52 ` Florian Westphal
2024-11-01 1:59 ` namniart
2024-11-02 16:12 ` Florian Westphal [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=20241102161217.GA13003@breakpoint.cc \
--to=fw@strlen.de \
--cc=namniart@gmail.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.