From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Rafael David Tinoco <rafaeldtinoco@ubuntu.com>
Cc: Florian Westphal <fw@strlen.de>,
netfilter@vger.kernel.org,
Ken-ichirou MATSUZAWA <chamaken@gmail.com>
Subject: Re: NFULNL_CFG_F_CONNTRACK and IPv6
Date: Wed, 13 Jan 2021 18:50:54 +0100 [thread overview]
Message-ID: <20210113175054.GA10377@salvia> (raw)
In-Reply-To: <9d1e1f00-9198-4632-897f-dabb22d6e4d4@www.fastmail.com>
On Wed, Jan 13, 2021 at 10:25:23AM -0300, Rafael David Tinoco wrote:
> On Tue, Jan 12, 2021, at 6:33 PM, Rafael David Tinoco wrote:
> > > > which kernel are you running Florian?
> > >
> > > 5.10.5 stable. I can check Fedora tomorrow, I don't have classic
> > > iptables there at the moment.
> > >
> >
> > NM Florian,
> >
> > My code was returning -1 on a callback function, disabling the polling
> > for the netlink socket file descriptor. I had it fixed:
> >
> > TCPv6 [ 0] src = fe80::5054:ff:fecc:767d (port=1024) to dst =
> > fe80::5054:ff:fecc:767d (port=22) (confirmed)
> > table: raw, chain: PREROUTING, type: rule, position: 1
> >
> > and it is working fine now.
> >
>
> Too soon, *definitely* conntrack data tied to trace ulog netlink is intermittent. Trying to discover... I'll probably have to trace kernel to figure out why its not being included...
>
> log received (prefix="TRACE: raw:OUTPUT:policy:3 " hw=0x86dd hook=3 mark=0)
> <log><when><hour>2</hour><min>05</min><sec>01</sec><wday>4</wday><day>13</day><month>1</month><year>2021</year></when><prefix>TRACE: raw:OUTPUT:policy:3 </prefix><hook>3</hook><hw><proto>86dd</proto></hw><outdev>12</outdev></log> (ret=229)
> log received (prefix="TRACE: raw:OUTPUT:policy:3 " hw=0x86dd hook=3 mark=0)
> <log><when><hour>2</hour><min>05</min><sec>01</sec><wday>4</wday><day>13</day><month>1</month><year>2021</year></when><prefix>TRACE: raw:OUTPUT:policy:3 </prefix><hook>3</hook><hw><proto>86dd</proto></hw><outdev>12</outdev></log> (ret=229)
> log received (prefix="TRACE: raw:OUTPUT:policy:3 " hw=0x86dd hook=3 mark=0)
> <log><when><hour>2</hour><min>05</min><sec>01</sec><wday>4</wday><day>13</day><month>1</month><year>2021</year></when><prefix>TRACE: raw:OUTPUT:policy:3 </prefix><hook>3</hook><hw><proto>86dd</proto></hw><outdev>12</outdev></log> (ret=229)
There is no conntrack information yet in the raw table.
next prev parent reply other threads:[~2021-01-13 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:14 NFULNL_CFG_F_CONNTRACK and IPv6 Rafael David Tinoco
2021-01-12 16:57 ` Florian Westphal
2021-01-12 17:30 ` Rafael David Tinoco
2021-01-12 17:41 ` Florian Westphal
2021-01-12 18:01 ` Rafael David Tinoco
2021-01-12 18:17 ` Rafael David Tinoco
2021-01-12 18:36 ` Florian Westphal
2021-01-12 18:54 ` Rafael David Tinoco
2021-01-12 19:26 ` Florian Westphal
2021-01-12 21:33 ` Rafael David Tinoco
2021-01-13 13:25 ` Rafael David Tinoco
2021-01-13 17:50 ` Pablo Neira Ayuso [this message]
2021-01-13 21:07 ` Rafael David Tinoco
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=20210113175054.GA10377@salvia \
--to=pablo@netfilter.org \
--cc=chamaken@gmail.com \
--cc=fw@strlen.de \
--cc=netfilter@vger.kernel.org \
--cc=rafaeldtinoco@ubuntu.com \
/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.