Same relay/listening ip address could be add for more than once, if they were't add continuously.
Open
Nobody has claimed this yet.
auto-migrated
Priority-Medium
Type-Defect
- Dominant language
- C
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
What steps will reproduce the problem?
1. run this command to start turn server, "10.0.0.12" is turn server's local ip
address:
./turnserver -E 10.0.0.12 -E 127.0.0.1 -E 10.0.0.12
2. Watch command output, about "Relay address to use".
What is the expected output? What do you see instead?
Expected output:
... ...
0: Relay address to use: 10.0.0.12
0: Relay address to use: 127.0.0.1
... ...
Real output:
... ...
0: Relay address to use: 10.0.0.12
0: Relay address to use: 127.0.0.1
0: Relay address to use: 10.0.0.12
... ...
What version of the product are you using? On what operating system?
Version Coturn-4.4.5.1 'Ardee West'
Please provide any additional information below.
Patch file in attached.
Original issue reported on code.google.com by huxinb...@gmail.com on 28 Apr 2015 at 3:34
Attachments:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the turnserver command shown and inspect the attached netengine.c.patch alongside the code that prints "Relay address to use". Done means repeated -E 10.0.0.12 input produces only one 10.0.0.12 relay address, while 127.0.0.1 remains listed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100