mappings lost if another SDK starts up on same ports
Open
Nobody has claimed this yet.
type: bug
- Dominant language
- Python
- Stars
- 26
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
If you are running an SDK with upnp and another SDK starts up and doesn't detect that properly, the ports are torn down somehow. This has happened to me a couple times but I don't have the exact scenario yet, but think it's a failure case when it doesn't detect the existing mappings.
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 failure with two SDK instances using UPnP on the same ports, since the issue reports no exact scenario. Trace the existing mapping detection and teardown behavior; done means an SDK starting afterward does not remove mappings created by the first SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100