port mapping conflict in certain cases
Open
Nobody has claimed this yet.
type: bug
- Dominant language
- Python
- Stars
- 26
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I have 4 PCs on my network - 1 of them is configured to use 3335 as the TCP port via the daemon config. First PC grabs 3333. Next PC grabs 3334. Third PC tries to grab 3335, which is already used, and fails to map on 3336 because of the port conflict.
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 daemon configuration with four PCs, using TCP port 3335 and the observed 3333/3334 allocation sequence. Trace the port-mapping logic and verify that when 3335 is occupied, the third PC continues to the next available port such as 3336 instead of failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100