Summary: | SCTP aborts connections when primary is affected by packetloss but secondary path is clean | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Frans Slothouber <frans.slothouber> | ||||||
Component: | kern | Assignee: | Michael Tuexen <tuexen> | ||||||
Status: | Closed FIXED | ||||||||
Severity: | Affects Only Me | CC: | tuexen | ||||||
Priority: | --- | ||||||||
Version: | 9.3-RELEASE | ||||||||
Hardware: | Any | ||||||||
OS: | Any | ||||||||
Attachments: |
|
Description
Frans Slothouber
2015-01-15 12:08:18 UTC
Hi Frans, thank you very much for the report. I have a clarification question: When you introduced the packet loss, did this only affect the packets in one direction, or did it apply the packets in both directions. Best regards Michael (In reply to Michael Tuexen from comment #1) Hoi Michael, Packets are affected in both directions (but this happens on only one of the paths). Best regards, Frans OK. And each side sends a message once a second, independently. It is not one side sending a packet a second and the other reflects it on reception. Best regards Michael (In reply to Michael Tuexen from comment #3) Correct; they both send messages independently of each other. The only thing each sides does with the with the message is log that it was received and when. Each side sends a message every second, with a few mili second variation. Ahh, OK. That should allow me to reproduce and analyse the problem. Might take some time, but I'll come back. Thanks for your help so far. Best regards Michael Created attachment 154841 [details]
server used for testing
Created attachment 154842 [details]
client used for testing
OK, the logic to choose the destination address for SACK chunks was sub-optimal. Randy and myself worked on a fix which is checked in as https://svnweb.freebsd.org/changeset/base/280714 Thanks for reporting the issue! Best regards Michael |