nat: deal with changing networks
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
Currently, the user has to call `DiscoverNAT` up-front. However, if the user changes networks, they'll have to call this again.
Instead, we should provide a standard `New()` constructor that calls `DiscoverNAT` in the background whenever port-mapping fails.
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 tracing the existing DiscoverNAT entry point and the port-mapping failure path. Determine how a standard New() constructor could trigger background rediscovery after network changes, then verify that port mapping recovers without requiring the user to call DiscoverNAT again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100