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

Seems like glitches in the code #22

Open
ravenrani opened this issue Sep 12, 2024 · 0 comments
Open

Seems like glitches in the code #22

ravenrani opened this issue Sep 12, 2024 · 0 comments

Comments

@ravenrani
Copy link

ravenrani commented Sep 12, 2024

[1] It seems like the DatagramSockets are not being closed properly.
I tried fixing some issues, by adding reusable address, and finally with socket.close
However some Address already in use issues are still happening.
[2] There are timeouts while receiving the STUN answer, not sure why those happen, but they are finished with unknown
[3] I am not sure how the ports are being picked, I believe it should have been done by the webrtc candidates selection or similar.
It seems that different codes trying to mimic the same thing are using different default ports, os I am not sure.
[4] It seems like part of the algorithm to distinct between nat-types is supposed to be using at least 2 different STUN servers

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

1 participant