Exposing a port behind a carrier-grade NAT
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Am I able to use this tool to expose a port / service running behind a carrier-grade NAT?
For context, I am running Navidrome on my home server, however I am unable to use regular port forwarding due to my internet connection using CGNAT. So I've been trying to set up a Chisel server on Digital Ocean and a client on my home server, so that I can access Navidrome via Digital Ocean, but I am not having much luck.
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
The issue names no file, test, or entry point. Start by reproducing the described Chisel server on DigitalOcean and client on the home server, then verify whether Navidrome is reachable through the CGNAT setup. Done means documenting a confirmed supported configuration or a clear limitation.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100