Skip to content

port mapping conflict in certain cases #3

Description

@tzarebczan

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: bugExisting functionality is wrong or broken

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions