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

Implementing Close DataChannel #20

Closed
mo3rfan opened this issue Mar 28, 2017 · 6 comments
Closed

Implementing Close DataChannel #20

mo3rfan opened this issue Mar 28, 2017 · 6 comments

Comments

@mo3rfan
Copy link
Contributor

mo3rfan commented Mar 28, 2017

I've noticed that Close() is a TODO at the moment.
To implement this, is it sufficient to use usrsctp_deregister_address() as it's done here?

@chadnickbok
Copy link
Owner

It should be, but that would be well worth a double-check when implementing.

Thanks for the reminder, I'll try to take a look at implementing this, or you're more than welcome to submit a PR :)

@mo3rfan
Copy link
Contributor Author

mo3rfan commented Mar 29, 2017

Ah okay, I'm looking at it too. I'm trying to ensure that the testclient program could terminate safely so I could then check for any memory leaks with valgrind.

@chadnickbok
Copy link
Owner

Perfect - one challenge I've had with Valgrind is that it gets super upset with OpenSSL. You can create ignore lists for a lot of the OpenSSL warnings that should help sort the signal from the noise.

@mo3rfan
Copy link
Contributor Author

mo3rfan commented Mar 30, 2017

Yep! I've seen that. Crypto functions in OpenSSL use uninitialized memory on purpose for the entropy. I've used suppression files for this before.

Anyway, here's my attempt at solving this. I'm trying to reset the stream using SCTP_RESET_STREAMS, but I get EINVAL (errno 22) when I do this. Any Ideas?

@mo3rfan
Copy link
Contributor Author

mo3rfan commented Apr 4, 2017

I think I got this working. Will send a PR soon once I do a bit of clean up :)

@mo3rfan
Copy link
Contributor Author

mo3rfan commented Apr 6, 2017

PR: #24

@mo3rfan mo3rfan closed this as completed Apr 6, 2017
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

2 participants