-
Notifications
You must be signed in to change notification settings - Fork 154
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
[Bug] The wrong way to determine the port restricted NAT or restricted NAT #14
Comments
hmgle
added a commit
to hmgle/pystun
that referenced
this issue
Apr 29, 2015
…t used addr with changeport flag
konradkonrad
pushed a commit
to konradkonrad/pystun
that referenced
this issue
Apr 3, 2017
…t used addr with changeport flag
konradkonrad
added a commit
to konradkonrad/pystun
that referenced
this issue
Apr 3, 2017
fix jtriley#14: in test3, the client should send Request from the last used …
konradkonrad
pushed a commit
to konradkonrad/pystun
that referenced
this issue
Apr 18, 2017
…t used addr with changeport flag
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we do Test3 to determine the client is behind a restricted or port restricted NAT, this line:
will request stun server sends a response from addr(changedIP:changedPort). As we have just send a request:
both RestricNAT and RestricPortNAT will receive the response. So we alway get
typ = RestricNAT
even if behind a port restricted NAT.The text was updated successfully, but these errors were encountered: