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.

Sign up for GitHub

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

Jump to bottom

port mapping conflict in certain cases #3

Open
tzarebczan opened this issue Jan 16, 2019 · 0 comments
Open

port mapping conflict in certain cases #3

tzarebczan opened this issue Jan 16, 2019 · 0 comments
Labels
type: bug Existing functionality is wrong or broken

Comments

@tzarebczan
Copy link
Contributor

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.
@tzarebczan tzarebczan added the type: bug Existing functionality is wrong or broken label Jan 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug Existing functionality is wrong or broken
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tzarebczan