--
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> On Behalf Of Vlad Yasevich
> Sent: Wednesday, April 11, 2007 9:45 AM
> To: Isaula Oscar-QOI000
> Cc: netdev@vger.kernel.org; [EMAIL PROTECTED]
> Subject: Re: [SCTP] Initialization collision problem
>
> Hi Oscar
>
&
[mailto:[EMAIL PROTECTED]
> On Behalf Of Vlad Yasevich
> Sent: Wednesday, April 11, 2007 9:45 AM
> To: Isaula Oscar-QOI000
> Cc: netdev@vger.kernel.org; [EMAIL PROTECTED]
> Subject: Re: [SCTP] Initialization collision problem
>
> Hi Oscar
>
> Isaula Oscar-QOI000 w
: Isaula Oscar-QOI000
Cc: netdev@vger.kernel.org; [EMAIL PROTECTED]
Subject: Re: [SCTP] Initialization collision problem
Hi Oscar
Isaula Oscar-QOI000 wrote:
> I ran into a problem where LKSCTP is reporting a SCTM_COMM_UP
> indication to the User application but is giving back a value o
Hi Oscar
Isaula Oscar-QOI000 wrote:
> I ran into a problem where LKSCTP is reporting a SCTM_COMM_UP indication
> to the User application but is giving back a value of zero for the
> assoc_id.
>
> Attached are the SCTP debugs for the period in question.
>
> A couple of things that I would like to
[For SCTP questions, please use netdev or lksctp-developers list]
Hi Oscar
Isaula Oscar-QOI000 wrote:
> I ran into a problem where LKSCTP is reporting a SCTM_COMM_UP indication
> to the User application but is giving back a value of zero for the
> assoc_id.
>
> Attached are the SCTP debugs for t
I ran into a problem where LKSCTP is reporting a SCTM_COMM_UP indication
to the User application but is giving back a value of zero for the
assoc_id.
Attached are the SCTP debugs for the period in question.
A couple of things that I would like to note about my setup. One is that
I'm running Kerne
