From: Christian Kujau <lists@nerdbynature.de>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org, Dmitry Safonov <0x7f454c46@gmail.com>,
Francesco Ruggeri <fruggeri@arista.com>,
Salam Noureddine <noureddine@arista.com>,
Dmitry Safonov <dima@arista.com>,
David Ahern <dsahern@kernel.org>
Subject: syslog spam: TCP segment has incorrect auth options set
Date: Thu, 4 Jan 2024 11:55:44 +0100 (CET) [thread overview]
Message-ID: <f6b59324-1417-566f-a976-ff2402718a8d@nerdbynature.de> (raw)
Ever since commit 2717b5adea9e ("net/tcp: Add tcp_hash_fail() ratelimited
logs") the following is printed, in waves of small floods, to syslog:
kernel: TCP: TCP segment has incorrect auth options set for XX.20.239.12.54681->XX.XX.90.103.80 [S]
This host is connected to the open internet and serves as a small HTTP and
SSH login server, not much traffic is happening here. So I'd assume these
messages to be the result of random internet scans and/or fingerprinting
attempts or the like. While not really a concern, these messages are
flooding the dmesg buffer over time :-(
Is there a way to adjust the severity of these messages?
* In include/net/tcp.h this gets logged with tcp_hash_fail(), which is
* defined in include/net/tcp_ao.h and calls net_info_ratelimited(), which
* is in turn defined in include/linux/net.h and calls pr_info().
Can e.g. net_dbg_ratelimited be used instead?
Thanks,
Christian.
--
BOFH excuse #78:
Yes, yes, its called a design limitation
next reply other threads:[~2024-01-04 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 10:55 Christian Kujau [this message]
2024-01-04 13:49 ` Dmitry Safonov
2024-01-04 16:03 ` Christian Kujau
2024-01-07 19:27 ` Christian Kujau
2024-01-08 18:51 ` Dmitry Safonov
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=f6b59324-1417-566f-a976-ff2402718a8d@nerdbynature.de \
--to=lists@nerdbynature.de \
--cc=0x7f454c46@gmail.com \
--cc=dima@arista.com \
--cc=dsahern@kernel.org \
--cc=fruggeri@arista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noureddine@arista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®