Hi,
No, the original code looks correct. The address management code needs
to run regardless of whether SCTP_PCB_FLAGS_DO_ASCONF is enabled (or
whether the peer supports ASCONF or not). The newly added address is
put onto the restricted list to prevent the stack from using the new
address as a s
There's a corresponding change that is needed for pulling the auth info
out of the cookie for the other direction (i.e. server side
handling). I've
committed that into the SCTP project repo, and should also get in with
Randall's next commit.
--peter
On Jan 29, 2009, at 2:23 AM, Michael Tüxe
Yes it does except for the "multiple/bundled ASCONF" sub-feature
which is available as a separate patch.
If you have any questions, please let me or Randall Stewart
know. There is a minor patch that I've been meaning to get
to, but it probably will not impact you.
thanks,
--peter
sazzadur rahm
From the "NOTES" file in /usr/src/sys/conf:
# Note YOU MUST have both INET and INET6 defined.
# you don't have to enable V6, but SCTP is
# dual stacked and so far we have not teased apart
# the V6 and V4.. since an association can span
# both a V6 and V4 address at the SAME time :-)
This in
Can you verify that the version of the stack in Fedora 5 implements
the SCTP AUTH chunk? The FreeBSD stack will silently discard the
ADD-IP chunk if it's not wrapped with an AUTH chunk as per the RFC.
--peter
sazzadur rahman wrote:
Hello,
We are using SCTP client on Linux (Fedora 5) and SCTP s
I think this is because any bugs that are found are usually
communicated directly to us.
I think Randy has a better handle on how many people are using
this stack. I'm quite sure it is stable enough to go in to
-current.
While the SCTP API hasn't gone through last call, it's fairly
stable and we h
SUZUKI Shinsuke wrote:
On Fri, 22 Oct 2004 19:58:32 -0500
[EMAIL PROTECTED](Peter Lei) said:
While the SCTP API hasn't gone through last call, it's fairly
stable and we have both "converted" many applications from TCP
to SCTP using the sockets API, as well as had portabil
.78.114" );
>> int iRet = connect(s, (struct sockaddr *)&farAddr, sizeof
>> farAddr);
>>
>> //sctp_bindx
>> struct sockaddr_in my2ndAddr;
>> memset(&my2ndAddr, 0, sizeof my2ndAddr);
>> my2ndAddr.sin_len = sizeof my2
