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

[Bug] The wrong way to determine the port restricted NAT or restricted NAT #14

Open
hmgle opened this issue Apr 29, 2015 · 1 comment
Open

Comments

@hmgle
Copy link

hmgle commented Apr 29, 2015

When we do Test3 to determine the client is behind a restricted or port restricted NAT, this line:

ret = stun_test(s, changedIP, port, source_ip, source_port, changePortRequest)

will request stun server sends a response from addr(changedIP:changedPort). As we have just send a request:

ret = stun_test(s, changedIP, changedPort, source_ip, source_port)

both RestricNAT and RestricPortNAT will receive the response. So we alway get typ = RestricNAT even if behind a port restricted NAT.

hmgle added a commit to hmgle/pystun that referenced this issue Apr 29, 2015
@YF-Tung
Copy link

YF-Tung commented Nov 9, 2016

@hmgle is right.
@jtriley please fix this issue, please.
Out team was misled by this result for several days.

konradkonrad pushed a commit to konradkonrad/pystun that referenced this issue Apr 3, 2017
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
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