You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Can you tell me, which setup you used. Which examples did you start?
What did you do on the client and on the server side. What does your property list look like?
Am 10.01.2018 um 16:16 schrieb Naeem Khademi ***@***.***>:
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
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#422 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADsEgwrEeJuj-iJbCXchh1yxIiFQbO_ks5tJNROgaJpZM4RZPoa>.
*****************************************
Dr. Irene Rüngeler
Fachbereich Elektrotechnik und Informatik
Labor für Netzwerkprogrammierung, Datenbanklabor
Fachhochschule Münster
- University of Applied Sciences -
Stegerwaldstraße 39, Raum E130a
48565 Steinfurt
Tel: +49 2551 962-561
Fax: +49 2551 962-563
EMail: [email protected]
If the multihoming property is set SCTP (on Ubuntu 16.04) connection fails with
To reproduce using
tneat
:Start a server:
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:BTW, using an MPTCP kernel I get a different error
The text was updated successfully, but these errors were encountered: