On 8 Oct 2020, at 16:33, Ilya Maximets wrote:
On 9/17/20 10:41 AM, Eelco Chaudron wrote:
Currently, userspace conntrack only tracks TCP, UDP, and ICMP, and
all
other IP protocols are discarded, and the +inv state is returned.
This
is not in line with the kernel conntrack. Where if no L4
On 9/17/20 10:41 AM, Eelco Chaudron wrote:
> Currently, userspace conntrack only tracks TCP, UDP, and ICMP, and all
> other IP protocols are discarded, and the +inv state is returned. This
> is not in line with the kernel conntrack. Where if no L4 information can
> be extracted it's treated as
Eelco Chaudron writes:
> Currently, userspace conntrack only tracks TCP, UDP, and ICMP, and all
> other IP protocols are discarded, and the +inv state is returned. This
> is not in line with the kernel conntrack. Where if no L4 information can
> be extracted it's treated as generic L3. The
On Thu, Sep 17, 2020 at 04:41:33AM -0400, Eelco Chaudron wrote:
> Currently, userspace conntrack only tracks TCP, UDP, and ICMP, and all
> other IP protocols are discarded, and the +inv state is returned. This
> is not in line with the kernel conntrack. Where if no L4 information can
> be
Currently, userspace conntrack only tracks TCP, UDP, and ICMP, and all
other IP protocols are discarded, and the +inv state is returned. This
is not in line with the kernel conntrack. Where if no L4 information can
be extracted it's treated as generic L3. The change below mimics the
behavior of
