If a create permission message is sent and some of the addresses fail (wrong address family, forbidden destination, etc.), permissions for addresses listed earlier in the request are installed despite the error response.
What steps will reproduce the problem? 1. Start the turn server forbidding some peer addresses. 2. Send a CREATE-PERMISSION message with one allowed peer address followed by a forbidden peer addrss. 3. Note the 403 response to CREATE-PERMISSION. 4. Send a packet from the allowed peer address.
What is the expected output? What do you see instead? Packet should not be routed (since CREATE-PERMISSION failed). Instead it is allowed.
What version of the product are you using? On what operating system? Current trunk.
Please provide any additional information below. I confess to diagnosing this problem from code inspection, not actually testing it.
Comment #1
Posted on Feb 8, 2014 by Happy Giraffe(No comment was entered for this change.)
Comment #2
Posted on Feb 8, 2014 by Happy GiraffeThe issue is fixed in SVN, will be a part of 3.2.2.6 build.
Comment #3
Posted on Feb 9, 2014 by Happy GiraffeFixed in 3.2.2.6
Status: Fixed
Labels:
Type-Defect
Priority-Medium