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

mappings lost if another SDK starts up on same ports #9

Open
tzarebczan opened this issue Mar 8, 2019 · 0 comments
Open

mappings lost if another SDK starts up on same ports #9

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

Comments

@tzarebczan
Copy link
Contributor

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.
@tzarebczan tzarebczan added the type: bug Existing functionality is wrong or broken label Mar 8, 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
2 participants
@tzarebczan @jackrobison