All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: No indication from kernel after'Max.Init.Retransmits' retries
Date: Thu, 28 May 2009 14:15:41 +0000	[thread overview]
Message-ID: <4A1E9C8D.5030104@hp.com> (raw)
In-Reply-To: <JBECLENKLBCKAAKFGAJOAEJPGGAA.barryn@adax.com>

Barry Nagelberg wrote:
> Hi,
> 
> I am running M3UA over lksctp using the following versions:
> 
> Redhat EL 4 Update 5
> Kernel version : 2.6.9-55.ELsmp #1 SMP
> 32Bits
> 

Issues with RedHat kernels should be reported to RedHat.

> This corresponds to http://tools.ietf.org/html/draft-ietf-tsvwg-sctpsocket-07.
> 
> When my M3UA ASP (client) tries to connect to a peer that isn't running, and after my client sends the SCTP INIT msg
> 'Max.Init.Retransmits' times, I expect to receive an error indication from the kernel, as per the following section from
> RFC 4960:
> 
> <snip>
> 4. SCTP Association State Diagram
> 
> .....
> 
>    2) If the T1-init timer expires, the endpoint MUST retransmit INIT
>       and re-start the T1-init timer without changing state.  This MUST
>       be repeated up to 'Max.Init.Retransmits' times.  After that, the
>       endpoint MUST abort the initialization process and report the
>       error to SCTP user.
> <snip>
> 
> Before I bind to the socket and issue the connect call, I am subscribing to all of the event notifications in the
> sctp_event_subscribe structure listed in section 7.3 of the sctpsocket draft:
> 
>    struct sctp_event_subscribe{
>        u_int8_t sctp_data_io_event;
>        u_int8_t sctp_association_event;
>        u_int8_t sctp_address_event;
>        u_int8_t sctp_send_failure_event;
>        u_int8_t sctp_peer_error_event;
>        u_int8_t sctp_shutdown_event;
>        u_int8_t sctp_partial_delivery_event;
>        u_int8_t sctp_adaption_layer_event;
>    };
> 
> However I don't receive any event from the kernel after 'Max.Init.Retransmits' retries. In a normal successful
> association startup or takedown I _do_ receive an event.
> 
> This seems to be a defect in lksctp. Has this been pointed out before? Has this been fixed in a subsequent version?
> 

I am sure this has been fixed.  2.6.9 kernel is very old.

-vlad
> Thanks for any assistance,
> Barry Nagelberg
> 
> --
> 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
> 


      reply	other threads:[~2009-05-28 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 12:31 No indication from kernel after'Max.Init.Retransmits' retries Barry Nagelberg
2009-05-28 14:15 ` Vlad Yasevich [this message]

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=4A1E9C8D.5030104@hp.com \
    --to=vladislav.yasevich@hp.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.