Chronological Thread 

< Chronological >      < Thread >

---

Hi,

the answer to your question is simple: it is a bug.

As I said before, the code is mainly untested, so it is very likely that
you will encounter bugs. That is what you did.

As I said in the previous mails, I strongly suggest that you wait
for pre20 which will have tested support of PRSCTP. pre19 has only
been tested with lifetime = -1, which means do not use USCTP.

Best regards
Michael

On Wednesday, Dec 11, 2002, at 04:37 Europe/Berlin, Oon Heok Kee wrote:

Hi,

I'm using sctplib pre19, with socketapi-1.0.0. I'm trying to use the unreliable sctp portion, by assigning
sinfo_timetolive=(unsigned int)5;

A generic case is:

sender receiver
TSN(5)|------------>|
|<------------|SACK(2)
|<------------|SACK(4)
FWD_TSN(5)|------------>|
|<------------|SACK(5)

When something like this happens, data just stops flowing. Sometimes, receiver sends SACK(5) twice, with no indication of dup TSNs or gaps. HEARTBEATs are then sent. Basically, as long as a SACK with the same TSN follows the FORWARD TSN, data stops flowing.

When I set
sinfo_timetolive=(unsigned int)-1;
things seem to work fine.

Hope my illustration is clear. And can someone enlighten me on what's wrong? Thanks!!! :)



Oon, Heok Kee



_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail

_______________________________________________
discussion mailing list
discussion AT sctp.de
http://www.sctp.de/mailman/listinfo/discussion

---

• [SCTP-Discussion] Forward TSN, then stopped..., Oon Heok Kee, 12/11/2002
  • Re: [SCTP-Discussion] Forward TSN, then stopped..., Michael Tüxen, 12/11/2002
  • Re: [SCTP-Discussion] Forward TSN, then stopped..., Andreas Jungmaier, 12/11/2002

---

Archive powered by MHonArc 2.6.19+.