[Feature Request] Allow clients to be proxy endpoints
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Issue #8 mentions problems with reaching clients behind HTTP-only NAT/firewalls. Allowing a client to be a proxy endpoint would provide access to the client via the chisel server. For example, client A connects to client B via server:
[client A] <-> [server] <-> [client B] <-> ...
Possible API:
chisel server <server options>
#client B
chisel client --proxy B <client options> <server address>
#client A
chisel client <client options> <server address> B@3000
Where B@3000 is in the format <proxy name>@<chisel remote>
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 reviewing issue #8 and the proposed chisel server/client command flows. Trace the existing server and client entry points, then define how proxy naming and the B@3000 remote format should work end to end. Done means client B can be addressed through the server by client A as shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100