From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com> To: linux-sctp@vger.kernel.org Subject: Re: Heartbeat on closed SCTP sockets? Date: Mon, 05 Oct 2020 17:16:43 +0000 [thread overview] Message-ID: <20201005171643.GK70998@localhost.localdomain> (raw) In-Reply-To: <1FB70B30-857C-4CD9-A05C-4BA15F57B1D2@list.fink.org> Hi, On Mon, Oct 05, 2020 at 06:39:22PM +0200, Andreas Fink wrote: ... > What we now see in netstat --sctp is: > > we have a LISTEN on port 2010 > we have a association from port 2010 to the remote in status CLOSED > > in tcpdump we see packets coming in from the remote and heartbeat being acknowledged. However our application is not answering to these packets and the status of the application shows SCTP being down. > In other words, my application sees the association down. Netstat shows the association as being closed but the kernel seems to continue to entertain this association by continue to send heartbeat ACK and not sending ABORT. That's weird. If it is in CLOSED, then the stack should be handling it as an OOTB packet and trigger an Abort. > > We now kill the application > > What we now see in netstat --sctp is: > we no longer listen on port 2010 > we have a closed association from port 2010 to the remote. > > in tcpdump we however we STILL see packets coming in from the remote and heartbeat being acknowledged, even though no application is listening on this port and no userspace application is using that port. > We do not see any SHUTDOWN or INIT even if we restart the application. > > Can anyone explain how this can be? Please check the assoc status as well, via 'ss -a --sctp' and /proc/net/sctp/assocs . Maybe it got out of sync of the socket status. Marcelo
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com> To: Andreas Fink <afink@list.fink.org> Cc: linux-sctp@vger.kernel.org Subject: Re: Heartbeat on closed SCTP sockets? Date: Mon, 5 Oct 2020 14:16:43 -0300 [thread overview] Message-ID: <20201005171643.GK70998@localhost.localdomain> (raw) Message-ID: <20201005171643.C_XXajZUKAVbrXj1OmLW7bHJshZFzZQVNaOLoUoqKGc@z> (raw) In-Reply-To: <1FB70B30-857C-4CD9-A05C-4BA15F57B1D2@list.fink.org> Hi, On Mon, Oct 05, 2020 at 06:39:22PM +0200, Andreas Fink wrote: ... > What we now see in netstat --sctp is: > > we have a LISTEN on port 2010 > we have a association from port 2010 to the remote in status CLOSED > > in tcpdump we see packets coming in from the remote and heartbeat being acknowledged. However our application is not answering to these packets and the status of the application shows SCTP being down. > In other words, my application sees the association down. Netstat shows the association as being closed but the kernel seems to continue to entertain this association by continue to send heartbeat ACK and not sending ABORT. That's weird. If it is in CLOSED, then the stack should be handling it as an OOTB packet and trigger an Abort. > > We now kill the application > > What we now see in netstat --sctp is: > we no longer listen on port 2010 > we have a closed association from port 2010 to the remote. > > in tcpdump we however we STILL see packets coming in from the remote and heartbeat being acknowledged, even though no application is listening on this port and no userspace application is using that port. > We do not see any SHUTDOWN or INIT even if we restart the application. > > Can anyone explain how this can be? Please check the assoc status as well, via 'ss -a --sctp' and /proc/net/sctp/assocs . Maybe it got out of sync of the socket status. Marcelo
next prev parent reply other threads:[~2020-10-05 17:16 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-05 16:39 Heartbeat on closed SCTP sockets? Andreas Fink 2020-10-05 16:39 ` Andreas Fink 2020-10-05 17:16 ` Marcelo Ricardo Leitner [this message] 2020-10-05 17:16 ` Marcelo Ricardo Leitner 2020-10-06 13:31 ` Andreas Fink 2020-10-06 13:31 ` Andreas Fink 2020-10-08 6:40 ` Andreas Fink 2020-10-08 6:40 ` Andreas Fink 2020-10-08 8:13 ` David Laight 2020-10-08 8:13 ` David Laight 2020-10-08 9:08 ` Michael Tuexen 2020-10-08 9:08 ` Michael Tuexen 2020-10-08 10:57 ` Andreas Fink 2020-10-08 10:57 ` Andreas Fink 2020-10-08 11:02 ` Andreas Fink 2020-10-08 11:02 ` Andreas Fink
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=20201005171643.GK70998@localhost.localdomain \ --to=marcelo.leitner@gmail.com \ --cc=linux-sctp@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: linkBe 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).