Chronological Thread 

< Chronological >      < Thread >

---

Hi,

this is known and the workaround is to disable the
OOTB handling.

The examples provided in sctplib/programs do this
when the -i option is used.

If you write your own code, do the following:

SCTP_getLibraryParameters(&params);
params.sendOotbAborts = 0;
SCTP_setLibraryParameters(&params);

See sctplib/programs/terminal.c for example.

Best regards
Michael


On Jul 16, 2004, at 3:56 AM, Alexander Litvin wrote:

Hi, all!

I'm new to sctplib (though not new to SCTP). Just wanted to do
some testing. So, I downloaded sctplib-1.0.1 on my FreeBSD 5.1,
compiled it, tried to run. And here's my problem.

I wrote a simple client and server applications, and tried to
run them on the same host. No luck.

Doing some GDB, I found that client receives INIT which it
sends to server (and, sure, server receives INIT ACK which it
sends to client).

Apparently, the nature of raw sockets is responsible for this:
as long as you just have raw socket on the machine and protocol
matches, the socket will receive all the packets for that protocol.

Maybe, I'm missing something here. So, before I start hacking around
it, could somebody enlighten me? I suppose this "feature" should not
be news to the experts here. Is it supposed to be like this? Or is
there some "magic" compile/runtime option to overcome this restriction?

TIA,
Alex

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

---

• [SCTP-Discussion] Single host, Alexander Litvin, 07/16/2004
  • Re: [SCTP-Discussion] Single host, Michael Tuexen, 07/16/2004
    • Re: [SCTP-Discussion] Single host, Andreas Jungmaier, 07/16/2004

---

Archive powered by MHonArc 2.6.19+.