lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 1 May 2007 15:09:07 -0500
From:	"Isaula Oscar-QOI000" <>
To:	"Vlad Yasevich" <>,
Subject: RE: [SCTP] Initialization collision problem


I finally got test results for the changes you suggested. The original
issue is fixed and I have not detected any side effects.


-----Original Message-----
From: []
On Behalf Of Vlad Yasevich
Sent: Wednesday, April 11, 2007 9:45 AM
To: Isaula Oscar-QOI000
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

Can you give this patch a try and let me know if this fixes your issue?

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists