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

JSTUN is failing when other components are successful like pynat, pystun3 #23

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

Comments

@ravenrani
Copy link

I am trying to understand the procedure and the failures, because they seem the same.
one issue I've already identified and solved is the issue with the test2 and on, there is a trial to open a new UDPsocket for receiving while the sending socket was not closed.
I am not sure if the binded address in the client of the STUN request- with ip & port change was supposed to be the same,
but of course it will not work.
In the pynat & pystun3 implementations it doesn't work this way, the same socket is being used.

I haven't figured out yet why one is working and the other doesn't, or what is the cause for different identification of the NAT type for the same home router I have in different times.

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