SCTP INITs failing :Incorrect CRC32C,should be
"Kumar, Vivek (NSN - IN/Bangalore)" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
Hello, We have a scenario in which we have a server running linux kernel 2.6.28-7 on a MIPS64 architecture machine. The client on the other hand is an X86 machine. The issue being observed here now is that the When the client sends and INIT message the server discards the packet as the packet shows "Incorrect CRC32C,should be 0x98bfedc6". If we disable the CRC checking at the server side though it proceeds one step further,i.e.,the server now responds back with an INIT ACK (ignoring the checksum) but the client now discards the packet giving the same reason,i.e.,"Incorrect CRC32C,should be " I have attached a capture file illustrating the same. Any comments/suggestions would be really helpful. <<capture.txt>> Thanks in advance. Regards, Vivek Kumar Ph: +918043633849 _______________________________________________ Sigtran mailing list [email protected] https://www.ietf.org/mailman/listinfo/sigtran
capture.txt
(text/plain, 1.1 KB)
Stream Control Transmission Protocol, Src Port: m3ua (2905), Dst Port: m3ua (2905)
Source port: 2905
Destination port: 2905
Verification tag: 0x00000000
Checksum: 0x23d5c84a [incorrect CRC32C, should be 0x98bfedc6]
INIT chunk (Outbound streams: 2, inbound streams: 3)
Chunk type: INIT (1)
0... .... = Bit: Stop processing of the packet
.0.. .... = Bit: Do not report
Chunk flags: 0x00
Chunk length: 28
Initiate tag: 0x34ac35c8
Advertised receiver window credit (a_rwnd): 500000
Number of outbound streams: 2
Number of inbound streams: 3
Initial TSN: 0
Supported address types parameter (Supported types: IPv4)
Parameter type: Supported address types (0x000c)
0... .... .... .... = Bit: Stop processing of chunk
.0.. .... .... .... = Bit: Do not report
Parameter length: 6
Supported address type: IPv4 address (5)
Parameter padding: 0000
[Malformed Packet: SCTP]