Received-SPF: pass (google.com: domain of linux-kernel+bounces-16902-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Thu, 4 Jan 2024 17:03:57 +0100 (CET)
From: Christian Kujau <lists@nerdbynature.de>
To: Dmitry Safonov <dima@arista.com>
cc: netdev@vger.kernel.org, Dmitry Safonov <0x7f454c46@gmail.com>, 
    Francesco Ruggeri <fruggeri@arista.com>, 
    Salam Noureddine <noureddine@arista.com>, David Ahern <dsahern@kernel.org>, 
    linux-kernel@vger.kernel.org
Subject: Re: syslog spam: TCP segment has incorrect auth options set
In-Reply-To: <fe1752a6-9866-45e6-b011-92a242304fce@arista.com>
Message-ID: <491b1b19-f719-1aa6-7757-ba4168228bbd@nerdbynature.de>
References: <f6b59324-1417-566f-a976-ff2402718a8d@nerdbynature.de> <fe1752a6-9866-45e6-b011-92a242304fce@arista.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Thu, 4 Jan 2024, Dmitry Safonov wrote:
> Yeah, I guess it's possible to down the severity of these logs, but may
> be unexpected by admins: TCP-MD5 messages existed for long time and
> there may be userspace that expects them (i.e. in arista there are tests
> that look for these specific messages - those would be easy to fix, but
> there may be others outside this company).

Understood, thanks for explaining that.

> While thinking on the origin of your issue, it seems that the logs
> produced by either TCP-MD5 or TCP-AO are desired by a user when they
> add/use the authentication. Could you try this and see if that solves
> the issue for you?

Thanks for preparing that patch so quickly, did not expect that :-)

I've applied this on top of 6.7.0-rc8 and will report back if I see those 
messages again in the next days.

Thank you!
Christian.
-- 
BOFH excuse #127:

Sticky bits on disk.