From: Jeremy Sowden <jeremy@azazel.net>
To: Florian Westphal <fw@strlen.de>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: ulogd2 patch ping
Date: Tue, 1 Aug 2023 09:13:24 +0100 [thread overview]
Message-ID: <20230801081324.GJ84273@celephais.dreamlands> (raw)
In-Reply-To: <20230731221513.GA32288@breakpoint.cc>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On 2023-08-01, at 00:15:13 +0200, Florian Westphal wrote:
> Florian Westphal <fw@strlen.de> wrote:
> > I'll apply it on Friday in case noone objects until then.
>
> Just for completeness: I did not apply it due to the unanswered
> question from Pablo.
Thanks, Florian. I had hoped to have reponded over the week-end, but I
was busier than I expected and didn't pick this up again till yesterday
evening. Answers should be forthcoming soon.
> Also, don't we risk ambiguity here, or is there a guarantee that
> kernel never emits mapped addresses?
It would indeed mean that real ipv4-in-ipv6 addresses would be output in
ipv4 format. It's been several months, so I can't quite remember my
thinking, but I probably inclined towards regarding the ambiguity as
benign. I have spotted a problem with the existing patch, however, so
another version will definitely be needed, and I can look at eliminating
the ambiguity at the same time.
J.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-08-01 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 19:11 ulogd2 patch ping Jeremy Sowden
2023-07-26 7:28 ` Pablo Neira Ayuso
2023-08-02 10:40 ` Jeremy Sowden
2023-07-26 14:35 ` Florian Westphal
2023-07-31 22:15 ` Florian Westphal
2023-08-01 8:13 ` Jeremy Sowden [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=20230801081324.GJ84273@celephais.dreamlands \
--to=jeremy@azazel.net \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).