First login?
Lost password?
 
 
sctp-discussion AT lists.franken.de 
SCTP Discussions

Text archives Help


[SCTP-Discussion] Multi-homing support


Chronological Thread 
  • From: Mohsin Zaidi <mohsinrzaidi AT yahoo.co.uk>
  • To: SCTP discussion <discussion AT sctp.de>
  • Subject: [SCTP-Discussion] Multi-homing support
  • Date: Tue Apr 25 08:22:01 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=oSrsT+3slk/6cBHnN3RXyCGpt4WgZLWFHTyexiQo98efNmF9+/s0nnVC570rwN55MZb1sILDpmwqWQkptyZDW8gP4IsgGoc0AUJxnSB3oDfrms4Tr58R1aHZvv+srSZo5HObwaHs7qVcAOMRDq5E4aIerVoSHDL7vtT03fAnzU0= ;
  • List-id: SCTP Discussions <discussion.sctp.de>
Hi.

I'd like to know whether multi-homing is supported by either the user mode or kernel SCTP implementations. I prepared a two-NIC-each client and (echo) server setup (using socketapi) for both implementations but the packets just didn't get received by the server if I tore down the primary path (ie. pulled the plug out).

Since sctplib can display great execution trace info (a BIG thanks to its developers for that), I've observed that heartbeat messages do get across to the server over the alternate path but no data does. Once the primary path was re-enabled, data started flowing over it as if nothing had happened.

Am I missing something here?

Here are the commands I used:

./sctpterminal -local=192.168.55.11 -local=192.168.210.11 192.168.55.13:7 192.168.210.13:7 -chunklength=100 -nopckt=1000000

and

./sctpmultiserver -local=192.168.55.13 -local=192.168.210.13

I set up the NICs as point-to-point with their counterparts on the other system (eg. 192.168.55.11 p2p with 192.168.55.13) and checked their connectivities before beginning.

Thanks in advance.

Yahoo! 360° NEW – Your one place to blog, create, publish & share!

24 FIFA World Cup tickets to be won with Yahoo! Mail. Learn more

Archive powered by MHonArc 2.6.19+.

Top of page