All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@tnetconsulting.net>
To: lartc@vger.kernel.org
Subject: Re: Connection tracking debugging?!
Date: Tue, 25 May 2021 17:55:33 +0000	[thread overview]
Message-ID: <e73467d1-0427-1cb5-4ea0-d86bfd35e8d4@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20210525103639.GF3214@sv.lnf.it>

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

On 5/25/21 4:36 AM, Marco Gaiarin wrote:
> How can i 'debug' this issue? Thanks.

I'd check the output of dmesg to see if you're exhausting the state 
table.  If you are, you'll see all sorts of messages from the kernel. 
At least I did when I ran into this years ago.  Adding memory addressed 
the problem then.

Short of that low hanging fruit I'd start with packet captures so that 
you can watch the traffic flow.  I occasionally see invalid traffic 
after the flow should have been closed.

It looks like your client may be sending TCP Reset packets.  This could 
be directly related to how different systems terminate a TCP connection. 
  --  Even if the clients agree, they may be doing something different 
than the connection tracker helper expects, thus causing a subsequent 
packet to be considered invalid after a shorter shutdown.



-- 
Grant. . . .
unix || die


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4013 bytes --]

  reply	other threads:[~2021-05-25 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 10:36 Connection tracking debugging?! Marco Gaiarin
2021-05-25 17:55 ` Grant Taylor [this message]
2021-06-04 15:23 ` Marco Gaiarin

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=e73467d1-0427-1cb5-4ea0-d86bfd35e8d4@spamtrap.tnetconsulting.net \
    --to=gtaylor@tnetconsulting.net \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.