From: Florian Westphal <fw@strlen.de>
To: folkert <folkert@vanheusden.com>
Cc: netdev@vger.kernel.org
Subject: Re: masquerading AFTER first packet
Date: Thu, 2 Sep 2021 18:26:12 +0200 [thread overview]
Message-ID: <20210902162612.GA23554@breakpoint.cc> (raw)
In-Reply-To: <20210901204204.GB3350910@belle.intranet.vanheusden.com>
folkert <folkert@vanheusden.com> wrote:
> Hi,
>
> I'm seeing something strange. I'm doing an snmpwalk on an snmp server of
> mine (behing DNAT) , and after the first response it goes into a timeout.
> I did a tcpdump and saw this:
>
> 1630528031.843264 IP 185.243.112.54.38377 > 37.34.63.177.161: GetNextRequest(23) .1.3.6.1
> 1630528031.843924 IP 37.34.63.177.161 > 185.243.112.54.38377: GetResponse(34) .1.3.6.1.2=0 <-- ok
> 1630528031.846950 IP 185.243.112.54.38377 > 37.34.63.177.161: GetNextRequest(24) .1.3.6.1.2
> 1630528031.847415 IP 192.168.4.2.161 > 185.243.112.54.38377: GetResponse(35) .1.3.6.1.2.1=0 <-- fail
> 1630528032.847649 IP 185.243.112.54.38377 > 37.34.63.177.161: GetNextRequest(24) .1.3.6.1.2
> 1630528032.848081 IP 192.168.4.2.161 > 185.243.112.54.38377: GetResponse(35) .1.3.6.1.2.1=0 <-- fail
Looks like a kernel bug, but you did not include kernel version.
Please also show 'ethtool -k' for in and out interfaces.
You might want to try and disable udp releated offload settings to see
if that helps.
e.g.
c3df39ac9b0e3747bf8233ea9ce4ed5ceb3199d3,
"udp: ipv4: manipulate network header of NATed UDP GRO fraglist"
which fixed a bug where only first packet of GRO'd udp train would
have nat applied, (was broken between 5.6 and 5.11)
Other explanation is that conntrack thinks only first packet is valid,
you can check this for example via
sysctl net.netfilter.nf_conntrack_acct=1
and then checking if 'conntrack -L' shows increasing packet/byte
counters or is stuck at '1'.
If the remaining packets are indeed invalid, try setting
sysctl net.netfilter.nf_conntrack_log_invalid=17
(17 == udp).
and see if that shows something relevant.
next prev parent reply other threads:[~2021-09-02 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 20:42 masquerading AFTER first packet folkert
2021-09-02 16:26 ` Florian Westphal [this message]
2021-09-02 17:48 ` folkert
2021-09-02 20:07 ` Florian Westphal
2021-09-02 20:54 ` folkert
2021-09-05 8:39 ` folkert
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=20210902162612.GA23554@breakpoint.cc \
--to=fw@strlen.de \
--cc=folkert@vanheusden.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 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).