Thanks for your kind response The root cause of this problem is probably lksctp that is included in Linux 2.6.32-432. I found the lksctp that is included in Linux 2.6.32-504 is changed something related to checksum. When using virtual IP on bonding interface as our configuration, old lksctp did not set checksum value into their header. After installing kernel update that include new lksctp that this problem is patched, the checksum is successfully set. Thanks 2015. 5. 13., 오후 2:55, Michael Tuexen <Michael.Tuexen@xxxxxxxxxxxxxxxxx> 작성: > On 13 May 2015, at 04:14, Moohyoung KIM <emusal@xxxxxxxxx> wrote: > > Dear all, > > I am currently trying to make an association with otter vendor's system. but it is failed. > The engineer of peer side requests me to set checksum parameter into INIT Ack. message we sent. > > Q1. is it possible to differently set checksum value for each associations on linux-sctp? > Q2-1. If it is possible to set checksum separately, how to set the flag either use or not? > Q2-2. If it is NOT possible, we MUST turn the checksum feature on for whole association? how to do that? I am using lksctp-1.0.10-7 on Linux 2.6.32-432 (RHEL6). SCTP only uses CRC32c as the checksum and it is mandatory to use it. There is no "checksum parameter" for negotiating it. Does your peer still use the deprecated Adler32? It has been changed to CRC32c in https://tools.ietf.org/html/rfc3309 The updated SCTP specification https://tools.ietf.org/html/rfc4960 doesn't mention Adler32 anymore. Best regards Michael > > Thanks-- > 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
