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

[FeatureRequest] Reason for rejected connection #684

Closed
maxsharabayko opened this issue May 10, 2019 · 1 comment · Fixed by #720
Closed

[FeatureRequest] Reason for rejected connection #684

maxsharabayko opened this issue May 10, 2019 · 1 comment · Fixed by #720
Labels
[core] Area: Changes in SRT library core
Milestone

Comments

@maxsharabayko
Copy link
Collaborator

maxsharabayko commented May 10, 2019

There needs to be a way to find out the reason for the connection being rejected.

Currently in blocking mode connect() returns -1, and the error code returned by srt_getlasterror() is Connection setup failure: connection rejected (code 1002). But the reason is unclear, as this is returned for several reasons.
In non-blocking mode the error after srt_epoll_wait() on the caller socket returns -1, is
Non-blocking call failure: transmission timed out (code 6003)
That does not give any clue either.

There is MN_SECURITY minor error code, but it is disabled for backward compatibility reasons.

For the listening socket would be good to have a way to notify about the failing connections. A socket option with a callback function pointer?

@maxsharabayko maxsharabayko added the [core] Area: Changes in SRT library core label May 10, 2019
@maxsharabayko maxsharabayko added this to the v.1.3.3 milestone May 10, 2019
@maxsharabayko maxsharabayko modified the milestones: v.1.3.3, v.1.3.4 Jun 4, 2019
@maxsharabayko
Copy link
Collaborator Author

PR #720

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[core] Area: Changes in SRT library core
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant