[Lksctp-developers] Lksctp Multihoming issues!!

[Rao, K. (EXT-I. - FI) <kou...@ns...>]

Hi Guys,
 
Below is the library version used on our system to test SCTP between two components..
 
For 32 bit machine..
 
001A-$ /sbin/modinfo sctp
filename:       /lib/modules/2.6.21.7-hrt1-WR2.0aq_standard/kernel/net/sctp/sctp
.ko
license:        GPL
description:    Support for the SCTP protocol (RFC2960)
author:         Linux Kernel SCTP developers <lks...@li...urceforg <mailto:lks...@li...urceforg> 
e.net>
alias:          net-pf-10-proto-132
alias:          net-pf-2-proto-132
depends:        
vermagic:       2.6.21.7-hrt1-WR2.0aq_standard SMP mod_unload PENTIUM4 
 
For 64 bit machine..
 
001A-$ /sbin/modinfo sctp
filename:       /lib/modules/2.6.34.6-WR4.0.0.0_standard/kernel/net/sctp/sctp.ko
license:        GPL
description:    Support for the SCTP protocol (RFC2960)
author:         Linux Kernel SCTP developers <lks...@li...urceforg <mailto:lks...@li...urceforg> 
e.net>
alias:          net-pf-10-proto-132
alias:          net-pf-2-proto-132
depends:        libcrc32c
vermagic:       2.6.34.6-WR4.0.0.0_standard SMP preempt mod_unload 
parm:           no_checksums:Disable checksums computing and verification (bool)
 
 
The component we are building is predominantly a SCTP client and wont accept SCTP connections, instead initiates one. and we use One to One style connection setup and an individual socket to identify each connection.
 
Problem Statement: Symmetric Multihoming between Sctp Client and Server doesn't work. 
Testing methodology used: Cable pulling technique used for Primary path. -- Connection breaks down without switching to secondary path.
INIT payload: INIT chunk from SCTP client carries both Primary and Secondary IP's in it and INIT_ACK from SCTP server carries both Primary and Secondary IP's of itself back to Client.
Heartbeat status: HEART_BEAT messages flows between Primary IP of Client to Primary IP of Server and vice versa but not between Secondary IP of Client and Server.
                         Practically Secondary IP in Client and Server is inactive from the start.
 
API's Used to enable Multihoming at client side: sctp_bindx to bind to more than one IP and sctp_connectx to connect to more than one Dest IP.
                                                                SetSock_opt to REUSE_ADDR, prepare INIT message, SCTP_PEER_ADDR_PARAMS -- to set HeartBeat intervals and spp_pathmaxrxt value, SCTP_ASSOCINFO -- to set sasoc_asocmaxrxt value.
 
 
Question: Is there something I am missing in the code which gives raise to failure of Multihoming or else should I have to change few things in the code to make multihoming work.
                Is this a common issue noticed in this version? If so which version has this solved?
 
Note: If you guys need anymore info on this please do let me know, I will be glad to share it further.
 
Cheers, 
Koushik Rao