Disable NAT port mapping when not applicable
Open
Nobody has claimed this yet.
kind/enhancement
status/in-progress
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
Cases:
* [x] Public IP. Q: Are we also relying on our NAT code to configure network firewalls (even when a NAT isn't present)?
* [x] localhost.
* [ ] Port forwarding in place. Detecting this could be difficult.
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 locating the NAT port-mapping implementation and tracing how it handles public IPs, localhost, and existing port forwarding. Clarify whether NAT code also configures firewalls, then define completion as disabling mapping when it is not applicable and documenting or implementing the port-forwarding case.
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
- Needs clarification
- Newbie friendliness
- 28/100