[Lksctp-developers] SCTP_COMM_ LOST question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

We've been having this boggling SCTP_COMM_LOST occurring in our application.
And it's only occurring on some machine but we can't figure out what's going on.
The SCTP_COMM_LOST occurred ~2.192848s after init on alice side, and alice closed the socket(no abort sent to bob based on wireshark).
Alice didn't have any pending send or retransmission when SCTP_COMM_LOST was received.
Bob still unaware on the comm lost on alice, so when it sent a message to alice (data sent base on wireshark) at around ~14.043s after init,
Alice immediately responded an abort presumably because the socket was already closed.

How would we know what caused the SCTP_COMM_LOST on alice side?
System information is: Linux kiwi313 3.16.0-7-amd64 #1 SMP Debian 3.16.59-1 (2018-10-03) x86_64 GNU/Linux

Best Regards,
Prinz Buyo




[Index of Archives]     [Linux Networking Development]     [Linux OMAP]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux