<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Flowtable: Flows exiting OFFLOAD State being assigned value of nf_conntrack_tcp_timeout_unacknowledged"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1743#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Flowtable: Flows exiting OFFLOAD State being assigned value of nf_conntrack_tcp_timeout_unacknowledged"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1743">bug 1743</a>
from <span class="vcard"><a class="email" href="mailto:tim@muppetz.com" title="Tim Harman <tim@muppetz.com>"> <span class="fn">Tim Harman</span></a>
</span></b>
<pre>I have recently moved ISPs.
My old ISP required PPPoE, my new ISP doesn't (uses DHCP)
Since moving to my new ISP, I have been 100% unable to reproduce this problem.
My easy-to-reproduce test before I have tried 100 times and I can't reproduce
it.
I wonder if the issue that I was encountering was related to this fix I see in
6.6.29, and moving away from PPPoE has stopped the problem from appearing?
---- begin ----
ommit 4ed82dd368ad883dc4284292937b882f044e625d
Author: Pablo Neira Ayuso <<a href="mailto:pablo@netfilter.org">pablo@netfilter.org</a>>
Date: Thu Apr 11 00:09:00 2024 +0200
netfilter: flowtable: incorrect pppoe tuple
[ Upstream commit 6db5dc7b351b9569940cd1cf445e237c42cd6d27 ]
pppoe traffic reaching ingress path does not match the flowtable entry
because the pppoe header is expected to be at the network header offset.
This bug causes a mismatch in the flow table lookup, so pppoe packets
enter the classical forwarding path.
--- end ----</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>