Windows | Cannot use loop back address to connect to locally started Server

[Aderinom]

For some reason my own code and the example programs only work when utilizing the init_no_thread implementation of ursctp.
Attached are the logs from usrsctp and a capture with Wireshark.

I've tested with:

Working Config

st_client.exe 0.0.0.0 9900 127.0.0.1 9899 7
echo_server.exe 9899 9900

Result : Connection gets established

Not Working Config

client.exe 127.0.0.1 7 0 9900 9899
echo_server.exe 9899 9900

Result :

• Init is send and received
• Init_ack is send but seems to be dropped or ignored.

I've had the same results when I rewrote my own code to use the normal implementation of usrsctp.

Attached are logs and network captures from each config.
Current commit : f7368e6

usrsctp_bug.zip

[Aderinom]

From the Manual:

If client and server are started on the same machine, the loopback address 127.0.0.1 can be used for Unix-like OSs and the local address on Windows.

So problem was that I was using 127.0.0.1, using my IPaddress to connect worked.
Still - is there a reason that you can't use the loopback address for usrsctp?

[tuexen]

From the Manual:

If client and server are started on the same machine, the loopback address 127.0.0.1 can be used for Unix-like OSs and the local address on Windows.

So problem was that I was using 127.0.0.1, using my IPaddress to connect worked. Still - is there a reason that you can't use the loopback address for usrsctp?

I don't think usrsctp is doing any specific here. I guess, 127.0.0.1 is kind of special on Windows? I have no experience with WIndows, so I can't tell. Maybe @weinrank knows...