> On 12 Jan 2017, at 10:51, David Laight <David.Laight@xxxxxxxxxx> wrote: > > From: Sun Paul [mailto:paulrbk@xxxxxxxxx] >> Sent: 12 January 2017 09:31 >> Let me clear the understanding. below is the flow. >> >> 1. Client sends to Linux Router: 192.168.206.83 -> 192.168.206.56, >> 2. Linux router sends to SERVER where the source IP is unchanged: >> 192.168.206.83 -> 192.168.206.66 >> >> My question here is why SERVER cannot response this INIT chunk? > > Probably because the IP addresses embedded in the SCTP packet > don't match the ones in the IP header. I don't know if it matters on the linux implementation, but it shouldn't. An SCTP endpoint should consider the source address of the packet containing the INIT chunk and all the addresses listed in the INIT chunk as valid peer addresses. Could we get a .pcap file of the packet containing the INIT chunk captured at the server? I would expect an INIT-ACK or and ABORT. If that is not sent, the checksum was wrong or some kind of packet filtering is active on the server... Best regards Michael > > David > > N‹§ēæėrļ›yúčšØbēXŽķĮ§vØ^–)Þš{.nĮ+‰·ĨŠ{ąąËiŠ{ayš ʇڙë,jĒfĢĒ·hš‹āzđ ŪwĨĒļ Ē·Ķj:+v‰ĻŠwčjØmķŸĸūŦ‘ęįzZ+ƒųšŽŠÝĒj"ú! -- 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
