-
Notifications
You must be signed in to change notification settings - Fork 49
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
Rewrite extsctp on native sctp lib #25
base: master
Are you sure you want to change the base?
Conversation
a55a227
to
50ffc61
Compare
I added support for SCTP multihoming and it could be configure in channel args.
Client binding to 172.17.0.1 and 172.17.1.1 and connect to 172.17.0.2 and 172.17.1.2
You can connect without multihoming: just setup one ip per dest or source |
832ae69
to
77fdcc4
Compare
Parse multiple IPs from channels args like this: open-args="mode=client;dest=172.17.0.1:3868;dest=172.17.0.2:3868" Support server and client binding to multiple source ip like this: open-args="mode=server;source=172.17.1.1:3868;source=172.17.1.2"
77fdcc4
to
a62d4ce
Compare
Nice work @platinumthinker, I have implemented this and looking to use the multihoming feature :) |
@platinumthinker great work on this, managed to get multihoming working from within a docker container. |
Please don't merge this as is. The native lib commit is fine, at least to get it to build, but the multihoming commit causes a crash on Ubuntu 20.04, even if you're not using SCTP. I couldn't figure out why.
|
hehe (: wait another 5 year to change something else. |
I find that extsctp not available when SCTP enabled in kernel. I rewrited extsctp transport using native sctp lib