Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCTP fails when multihoming is enabled #422

Open
bozakov opened this issue Jan 10, 2018 · 2 comments
Open

SCTP fails when multihoming is enabled #422

bozakov opened this issue Jan 10, 2018 · 2 comments
Assignees

Comments

@bozakov
Copy link
Member

bozakov commented Jan 10, 2018

If the multihoming property is set SCTP (on Ubuntu 16.04) connection fails with

[   0.494709][DBG] Failed to create he socket (family:2, type:1, prodocol:132)

To reproduce using tneat:
Start a server:

./tneat -p 8888

On the client node create a property file test.prop containing the properties { "transport": { "value": "SCTP", "precedence": 1}, "multihoming": { "value": true, "precedence": 2} }. Then run:

./tneat 172.23.10.2 -p 8888 -P ./test.prop -v2 -n 100

BTW, using an MPTCP kernel I get a different error

[   0.849131][ERR] Failed to bindx fd XXX socket to IP. Error: Invalid argument
@naeemk
Copy link
Contributor

naeemk commented Jan 10, 2018

On MacOS (HighSierra 10.13.2) I get the same error as with the one mentioned about Ubuntu 16.04 on the client side. However on the server side, I get this error:

[ 0.003066][ERR] nt_listen_via_kernel: opening listening socket failed - Protocol not supported

Even though I have installed the usrsctp-neat and usrsctp support flag is enabled in CMakeList.txt.

On Ubuntu 16.04 LTS, with a similar setup as above, I get this error though:

usrsctp_sendv: No such file or directory

@ruengeler
Copy link
Contributor

ruengeler commented Jan 11, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants