top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Is there a concept of fail back in SCTP Multi Homing ?

+2 votes

Is there any concept of Fail back in SCTP Multi Homing ??

posted Dec 19, 2013 by Nithin Kp

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

RFC2960 specifically calls for the SCTP stack NOT to change the primary address. The reason behind this is that the application may have a preference for the primary path (e.g., cost, quality) and SCTP should follow application preference.

So in Summary SCTP stack supports the fail-back mechanism from the start though the behavior control ie control/disable of fail-back mechanism can very from vendor to vendor.

answer Dec 19, 2013 by Salil Agrawal
Similar Questions
+3 votes

When I read wiki , its written like this

As of 6 February 2010, multihoming in the next-generation Internet Protocol (IPv6) 
was not yet standardized

Is it supported now ?

+1 vote

Is there some simple mulithoming sample available? I found SCTP multistreaming sample, but not mulithoming.

+1 vote

I am trying to replicate heartbeat packets in a test env, because we believe one of our devices is having issues w/ these packets

We have enabled.

sysctl -w net.sctp.addip_enable=1
sysctl -w net.sctp.auth_enable=1 

Non-multihomed sctp traffic between an sctp_test client and server works.

But I cannot seem to figure out how to get sctp_test to generate heartbeat packets, which I believe multihoming is required.

How do I generate heartbeat packets and/or configure sctp_test to do multihoming?

+1 vote

Also if you can help me to, how can we identify the packets going in multiple streams from PCAP ?