Working with native SCTP about usrsctp HOT 10 CLOSED

Haven't saw this:

If UDP encapsulation is not necessary, the UDP port has to be set to 0.

from usrsctp.

Is there any example program working directly with SCTP?

from usrsctp.

Sure:

• programs/client
• programs/daytime_server
• programs/discard_server
• programs/echo_server
• programs/http_client
• programs/tsctp

from usrsctp.

@gedOHub which OS are you using?

To make sure: You are running the samples as root when using native SCTP?

from usrsctp.

Yes, running as administrator (Windows 10). Still trying to figure out how lib works :)

from usrsctp.

For example, why echo_server without parameters opens UDP 9899 port? Uses UDP encapsulation?

from usrsctp.

Because he is told to do so! 😀
See echo_server.c and usrsctp_init()

Have you tried to use the http_client? It's a handy example to get familiar with the usrsctp usage on client side.

To disable the verbose debug output, simply uncomment the usrsctp_sysctl_set_sctp_debug_on(SCTP_DEBUG_ALL); line here

You can test it with and without UDP-encapsulation against a small test system we are running
./http_client 212.201.121.100 80 0 9899 9899 with udp encaps
./http_client 212.201.121.100 80 native/raw sctp - run as admin
Running native SCTP may fail because of middleboxes and NATs.

Generally it is recommended that you don't run the server and a client on the same machine to avoid problems. Especially for debugging with Wireshark it's highly recommended to use two machines / VMs.

from usrsctp.

I need to run native SCTP for experment. So, to run native SCTP I need to usrsctp_init with first argument 0?

from usrsctp.

No, it is not required to set the first argument 0.
Setting the first argument simply adds the UDP-encpas functionality - the raw SCTP remains active.
For RAW SCTP you have to run SCTP as an administrator level.

from usrsctp.

After deep examination of http_client and your comments now it is clear how lib works. Thank you!!

from usrsctp.