Dear Sir, The connection is broken so that no data is sending at this moment. While testing failover(force no heartbeat ack replied from the IP X), I find that IP A try to send the heartbeat to IP Y but no heartbeat ack finally. Can lksctp client try to send heartbeat from IP B to IP Y? As only connection between IP B and IP Y is valid at that time. Regards, Andrew On Wed, Nov 30, 2016 at 7:39 PM, Xin Long <lucien.xin@xxxxxxxxx> wrote: > On Wed, Nov 30, 2016 at 6:48 PM, tsoi andrew <tsoiandrew@xxxxxxxxx> wrote: >> Dear Sir, >> >> 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? > how about data sending, can it be sacked normally ? > > asking that, as transport error_count would be cleared in > sctp_check_transmitted(): > > /* 8.2. When an outstanding TSN is acknowledged, > * the endpoint shall clear the error counter of > * the destination transport address to which the > * DATA chunk was last sent. > * The association's overall error counter is > * also cleared. > */ > transport->error_count = 0; > transport->asoc->overall_error_count = 0; > > >> >> lksctp client IP info: >> Primary IP: A >> Secondary IP: B >> >> Server primary IP: X >> Server secondary IP: Y >> >> Regards, >> Andrew >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
