Re: TCP info spamming the logs and dmesg

From: Eygene Ryabinkin <rea-fbsd_at_codelabs.ru>
Date: Thu, 16 Aug 2007 20:41:33 +0400
Andre, good day.

Thu, Aug 16, 2007 at 08:34:05PM +0400, Eygene Ryabinkin wrote:
> Thu, Aug 16, 2007 at 11:14:08AM -0400, Mike Jakubik wrote:
> > I recently did an update on my -CURRENT system, and i am now seeing a lot
> > of TCP messages from the kernel which are spamming my dmesg and
> > /var/log/messages.
> > 
> > ---
> > TCP: [217.81.3.76]:2978 to [99.244.15.156]:80; syncache_timer: Response
> > timeout, retransmitting (1) SYN|ACK
> > TCP: [58.254.32.40]:6926 to [99.244.15.156]:21; syncache_timer:
> > Retransmits exhausted, giving up and removing syncache entry
> > TCP: [58.254.32.40]:4342 to [99.244.15.156]:21; syncache_timer: Response
> > timeout, retransmitting (3) SYN|ACK
> > TCP: [209.47.38.69]:17523 to [99.244.15.156]:80 tcpflags 0x4<RST>;
> > syncache_chkrst: Spurious RST without matching syncache entry (possibly
> > syncookie only), segment ignored
> > ---
> > 
> > Is there any way to disable these, or have them log to a separate log?

I had seen about four such questions for the last two weeks, so maybe
it is time to patch tcp(4) manpage?  The following is the very rough
patch for it:
--- tcp.4.orig	2007-08-16 20:35:06.000000000 +0400
+++ tcp.4	2007-08-16 20:37:33.000000000 +0400
_at__at_ -259,6 +259,11 _at__at_
 Maximum
 .Tn TCP
 receive window.
+.It Va log_debug
+Enable (1) or disable (0)
+.Tn TCP
+stack debugging messages.
+Default is 1, i.e., the logging is enabled.
 .It Va log_in_vain
 Log any connection attempts to ports where there is not a socket
 accepting connections.
-- 
Eygene
Received on Thu Aug 16 2007 - 14:41:39 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:16 UTC