[erlang-questions] gen_sctp: What delays SACK?

Oliver Korpilla Oliver.Korpilla@REDACTED
Tue Nov 13 18:01:17 CET 2018

Hello, Jesper.

The problem I see that the C++ side just fails to send more messages back but I'm stumped why.

It _looks_ like it fails to respond to my protocol requests for some reason.

But does it really? Or is something blocking/buffering/delaying/missing in the stack? And which side causes it?

I'm very very stumped. Because I've seen the tcpdump in Wireshark and C++ stops sending. It just stops. (If I had more trust in my SCTP knowledge I would _assume_ there's some sort of deadlock on the C++ side.)

Thank you very much,

Gesendet: Dienstag, 13. November 2018 um 15:51 Uhr
Von: "Jesper Louis Andersen" <jesper.louis.andersen@REDACTED>
An: "Oliver Korpilla" <Oliver.Korpilla@REDACTED>
Cc: "Erlang (E-mail)" <erlang-questions@REDACTED>
Betreff: Re: [erlang-questions] gen_sctp: What delays SACK?

Use tcpdump(1) on the flow and look for who is adding the latency. Usual rule of protocol debugging is to start at the lowest level and verify each level as you go up. Because then you have an audit trail of the events that happened which can inform you at a higher level.

On Tue, Nov 13, 2018 at 10:15 AM Oliver Korpilla <Oliver.Korpilla@REDACTED[mailto:Oliver.Korpilla@REDACTED]> wrote:Hello.

We're using an elixir application as a sort of protocol tester. It communicated with the system-under-test over SCTP as a transport.

We're observing delay and unsent messages and due to the nature of the SCTP protocol we're not sure which side causes the issue.

The BEAM side has the NO_DELAY option set and pumps a burst of messages but then waits for responses (so it will not burst indefinitely, it burst once and then respond).

The C++ application has the DELAYED_SACK option set - we tried with both sack_freq 1 (which supposedly disables the algorithm) and higher (the default in our system).

(We also increased the receive window on both sides to ensure that senders would not block.)

But we're stumped. The C++ side is not responding at some point. When we did an actual target test once and we saw SCTP messages sent from system-under-test just stop when analyzing the tcpdump of the interfaces - C++ application has not emitted something on the wire and respectively nothing is received.

Our latest area of inquiry is to find out if maybe the elixir part is simply not getting scheduled - but can this impact for example SACK latency? Who acknowledges a message - the SCTP stack by itself or the application? And will the protocol block the sender until SACK?

I'm sorry for asking such vague questions but SCTP know-how is spread thin in our outfit and we're not the experts...

Thank you,
erlang-questions mailing list

More information about the erlang-questions mailing list