SCTP Discussions

Text archives Help


[SCTP-Discussion] Random (?) Init-ACKs


Chronological Thread 
  • From: "Samuel R. Baskinger" <samuel AT udel.edu>
  • To: discussion AT sctp.de
  • Subject: [SCTP-Discussion] Random (?) Init-ACKs
  • Date: Sat Apr 27 05:02:02 2002
  • List-id: SCTP Discussions <discussion.sctp.de>
  • Mmdf-warning: Parse error in original version of preceding line at mail.eecis.udel.edu

Hi all,

I've been doing some playing with the pre17 package, specifically
watching traffic from the localcom program to the echo_server program and
back over the local interface.
Today I witnessed two INIT-ACKs come out of the server in reply to
my client's one INIT. The two INIT-ACKs had seperate initial TSNs and
inittags.
I saw something similar on an earlier session where an INIT-ACK
came out of the server during the association shutdown. Again, seperate
initial TSN and inittag. Even the Cookie contains the correct inittag for
that PDU.
I've been poking around in the mailing list archives to see if
anyone else saw this, but haven't found anything yet. The specifics of
the associations are below. Note that only one localcom program was
active at any given time. :-) The "-n 20" localcom instance was only run
once and was the instance with the two INIT-ACKs during association
setup.

Thanks for any pointers/helps!

Traffic was being watched with tcpdump and Ethereal.
System was an Out-of-the-box Redhat 7.2 (though this was observed on a
Debian Potatoe system with one of the 2.4 kernels (between 2.4.10 and
17)).
The command lines used:
./localcom -l 10 -n 1 -u -e 1
./localcom -l 10 -n 20 -u -e 1
./echo_server -i

Sam





Archive powered by MHonArc 2.6.19+.

Top of page