Chronological Thread 

< Chronological >      < Thread >

---

I am refamiliarizing myself with sctplib by reading and running the
sample programs. I am getting some unexpected behaviour as
described below. Why should I need to specify a remote port number
as described below?

I cannot use the chat program at all. echo_server always sends
ABORTS with 0 causes.

Any suggestions?

mike


Test1:

1. on 192.168.1.4 logged in as root, run
"/pre14/sctplib/programs/discard_server -V -s 192.168.1.4
2. on 192.168.1.3 logged in as root, run
"pre14/sctplib/programs/terminal -V -s 192.168.1.3 -d 192.168.1.4;
using Ethereal observe 192.168.1.4 sending ABORT
1 : Communication lost (status 1)
sctp_receiveUnsent: not yet implemented.
sctp_receiveUnacked: not yet implemented.

Test2:

1. on 192.168.1.4 logged in as root, run
"/pre14/sctplib/programs/discard_server -V -s 192.168.1.4
2. on 192.168.1.3 logged in as root, run
"pre13/sctplib/terminal/terminal -V -s 192.168.1.3 -d 192.168.1.4;
using Ethereal observe 192.168.1.4 sending INIT_ACK
register done, instance = 1
getAssoc/setAssoc done !
Associate done !
register callback done
1 : Communication up (1 paths)
1 : Communication up (1 In-Streams, 10 Out-Streams)
3. typing at 192.168.1.3 generates the following message at
192.168.1.4
1 : Data arrived (5 bytes on stream 0, ordered)

Note: found that remote port in Test1 was 7 (default value) and that
port 9 was used in Test2

Test3:

1. Ran Test1 and added -r 9 to the terminal program options; results
were similar to Test2

---

• [SCTP-Discussion] Sample programs, Michael Mueller, 11/19/2001

---

Archive powered by MHonArc 2.6.19+.