From: "Gomonovych, Vasyl (Nokia - PL/Wroclaw)" <vasyl.gomonovych@nokia.com>
To: linux-sctp@vger.kernel.org
Subject: RE: NO TCB to Destory
Date: Thu, 18 Jun 2015 15:17:59 +0000 [thread overview]
Message-ID: <32A0AE6061CD66428E852409F01D958A0117C6F2@DEMUMBX005.nsn-intra.net> (raw)
In-Reply-To: <CAFXGft+hN7KOqGVWqa1xn0dKNJNarc65YYYFiLnSn7CMYarLHA@mail.gmail.com>
Hello.
I do not know which version you use.
But I observe similar issue and in my case
it was problem with sk_ack_backlog
sctp-Fix-sk_ack_backlog-wrap-around-problem.patch
With best regards Vasyl.
________________________________________
From: linux-sctp-owner@vger.kernel.org [linux-sctp-owner@vger.kernel.org] on behalf of ext Daniel Borkmann [daniel@iogearbox.net]
Sent: Thursday, June 18, 2015 4:30 PM
To: Sun Paul
Cc: linux-sctp@vger.kernel.org
Subject: Re: NO TCB to Destory
On 06/18/2015 12:20 PM, Sun Paul wrote:
> Hi
>
> I suffered a case on a SCTP connection.
>
> HOST A sends INIT chunk to HOST B
> HOST B returns INIT_ACK chunk back to HOST A
> HOST A sends COOKIE_ECHO chunk to HOST B
> HOST B then send ABORT chunk with T-bit set to 1.
>
> Any idea on why ABORT chunk is sent out?
Do you have a reliable, minimal reproducer?
--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-18 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 10:20 NO TCB to Destory Sun Paul
2015-06-18 12:57 ` Marcelo Ricardo Leitner
2015-06-18 14:30 ` Daniel Borkmann
2015-06-18 15:17 ` Gomonovych, Vasyl (Nokia - PL/Wroclaw) [this message]
2015-06-18 17:52 ` Sun Paul
2015-06-18 18:02 ` Sun Paul
2015-06-18 19:08 ` Daniel Borkmann
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=32A0AE6061CD66428E852409F01D958A0117C6F2@DEMUMBX005.nsn-intra.net \
--to=vasyl.gomonovych@nokia.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: 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.