From: o.evistel@free.fr
To: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Cc: oaitamrane@users.sourceforge.net, linux-sctp@vger.kernel.org
Subject: Re: Linux SCTP associations failure handlig
Date: Fri, 8 Jul 2022 16:46:16 +0200 (CEST) [thread overview]
Message-ID: <120452829.384713217.1657291576463.JavaMail.zimbra@free.fr> (raw)
In-Reply-To: <YsbiDrG1PQ2Gng5T@t14s.localdomain>
Hi Marcelo
Thank you for your help.
Regards
Omar AIT AMRANE
==============================================================
----- Mail original -----
De: "Marcelo Ricardo Leitner" <marcelo.leitner@gmail.com>
À: "o" <o.evistel@free.fr>
Cc: oaitamrane@users.sourceforge.net, linux-sctp@vger.kernel.org
Envoyé: Jeudi 7 Juillet 2022 15:39:26
Objet: Re: Linux SCTP associations failure handlig
Hi oaitamrane,
On Wed, Jul 06, 2022 at 01:19:20PM -0000, oaitamrane@users.sourceforge.net wrote:
>
>
> Dear Marcelo
>
> I would like to know if there is a way after association failure (SCTP_COMM_LOST event treceived) to retrieve UNSENT to peers and UNACKNOWLEDGED by peers Data Chunks for retransmission over an alternate association?
> I am using RHEL8.4 and sockets are set in NON BLOCKING mode.
> I have set the sctp_event_subscribe structure as follows:
>
> memset(&sctp_events, 0, sizeof(sctp_events));
>
> sctp_events.sctp_data_io_event = 1;
> sctp_events.sctp_association_event = 1;
> sctp_events.sctp_address_event = 1;
> sctp_events.sctp_peer_error_event = 1;
> sctp_events.sctp_adaptation_layer_event = 1;
> sctp_events.sctp_shutdown_event = 1;
> sctp_events.sctp_partial_delivery_event = 1;
> sctp_events.sctp_send_failure_event_event = 1;
>
> ret = setsockopt(sock_fd, IPPROTO_SCTP, SCTP_EVENTS,
> &sctp_events, sizeof(sctp_events));
My understanding is that you should be getting it via
sctp_send_failure_event_event above, detailed in rfc6458#section-6.1.11.
When SCTP tears down an association, it marks the chunks in outqueue
as failed in __sctp_outq_teardown(), which then sctp_datamsg_destroy()
ends up picking up and sending notifications to the application.
I didn't check this on RHEL 8.4, though, but I believe it has support
for this RFC as well. If you have the event as above, it should be
there.
>
> Can you please tell me if you a member of the dev team who can help me.
+Cc linux-sctp here to have a broader reach. We don't really use
sourceforge anymore. :-)
Cheers,
Marcelo
>
> Regards
> Omar AIT AMRANE
>
> - - - - - - - - - - - - - - - - - - - - -
>
> This message was sent to you via the SourceForge web mail form.
> You may reply to this message directly, or at https://sourceforge.net/u/oaitamrane/profile/send_message
next prev parent reply other threads:[~2022-07-08 14:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6f6f11b5c30bce3d6e77d719ef75112dee75250d.profile@marceloleitner.u.sourceforge.net>
2022-07-07 13:39 ` Linux SCTP associations failure handlig Marcelo Ricardo Leitner
2022-07-08 14:46 ` o.evistel [this message]
2022-07-13 12:58 ` Linux SCTP performance question o.evistel
2022-07-15 18:48 ` Marcelo Ricardo Leitner
2022-07-18 11:54 ` o.evistel
2022-07-16 12:13 ` David Laight
2022-07-18 14:09 ` o.evistel
2022-07-18 14:44 ` David Laight
2022-07-18 14:46 ` David Laight
2024-02-09 10:05 ` Linux SCTP multihoming question o.evistel
2024-02-09 10:10 ` Andreas Fink
2024-02-09 11:01 ` o.evistel
[not found] ` <483A5123-AA38-48EC-8158-120DFFC1E5D8@list.fink.org>
2024-02-09 12:03 ` o.evistel
2024-02-10 17:03 ` David Laight
2024-02-10 17:09 ` Philipp Stanner
2024-02-10 17:34 ` David Laight
2024-02-10 17:48 ` Philipp Stanner
2024-02-10 18:02 ` David Laight
2024-02-10 18:37 ` Philipp Stanner
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=120452829.384713217.1657291576463.JavaMail.zimbra@free.fr \
--to=o.evistel@free.fr \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=oaitamrane@users.sourceforge.net \
/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.