From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Isaula Oscar-QOI000 <Oscar.Isaula@motorola.com>
Cc: netdev@vger.kernel.org
Subject: Re: [SCTP] Initialization collision problem
Date: Tue, 01 May 2007 16:18:57 -0400 [thread overview]
Message-ID: <4637A0B1.20900@hp.com> (raw)
In-Reply-To: <5F14EEE91CB6694A86535A0A028D9C55016AEDF2@tx14exm60.ds.mot.com>
Isaula Oscar-QOI000 wrote:
> Vlad,
>
> I finally got test results for the changes you suggested. The original
> issue is fixed and I have not detected any side effects.
Thanks.
-vlad
>
> Thanks,
> Oscar
>
> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org]
> On Behalf Of Vlad Yasevich
> Sent: Wednesday, April 11, 2007 9:45 AM
> To: Isaula Oscar-QOI000
> Cc: netdev@vger.kernel.org; linux-kernel@vger.kernel.org
> 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 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 Kernel version 2.6.10 (I know is old but I can't move
>
>> to a newer version due to custom drivers). The second thing is that
>> the link between the two SCTP node is a very noisy and some messages
>> are getting lost (i.e. the INIT_ACK from the peer in this particular
> case).
>
> Can you give this patch a try and let me know if this fixes your issue?
>
> Thanks
> -vlad
>
next prev parent reply other threads:[~2007-05-01 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 14:35 [SCTP] Initialization collision problem Isaula Oscar-QOI000
2007-04-04 15:44 ` Vlad Yasevich
2007-04-11 14:45 ` Vlad Yasevich
2007-05-01 20:09 ` Isaula Oscar-QOI000
2007-05-01 20:18 ` Vlad Yasevich [this message]
2007-05-03 14:52 ` Isaula Oscar-QOI000
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=4637A0B1.20900@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=Oscar.Isaula@motorola.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).