[Feature request] Support for a port range instead of a single port
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to have support for a port range instead of a single port
f.e.
chisel_windows_amd64.exe client 0.0.0.0:12000-12199 R:127.0.0.1:13000-13199
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
No files or tests are named. Start by locating the client command parsing and port-forward handling, then determine how the example's local and remote ranges should be represented and validated. Done means the shown range command works with coverage for valid and invalid ranges.
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