Can we set the same to 0? If so, how??
Policy on that sysctl won't let you set the sack timeout below 1, as a timeout of 0 is nonsense, and would cause the sack timer to run near constantly.
SACK is selective ack, zero does not make any sense so don't know if system will allow it or not say system allows then you will receive the SACK for every message which will increase the message exchange between src and destination.
But setting it to zero will defy the purpose of SCTP ideally set it to 50ms or more.
It is found that IP X haven't replied heartbeat Ack to IP A but our client will not try another path B->Y. Would you advise how B->Y path can be enable?
lksctp client IP info: Primary IP: A Secondary IP: B
Server primary IP: X Server secondary IP: Y
I want to understand in which cases SCTP abort occurs and how it is get resolved ?
