Simple/noserver proxy for IPs on a local network
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
I have a bunch of VMs running on my network and have a WireGuard server acting as a gateway into my network. Each VM has a unique IP and I'd like to forward TCP/UDP traffic to them from the wg server.
UDP PORT 3000 -> 192.168.1.3:3000
TCP PORT 3000 -> 192.168.1.3:3000
UDP PORT 4453 -> 192.168.1.3:445
TCP PORT 4453 -> 192.168.1.3:445
TCP PORT 2203 -> 192.168.1.3:22
TCP PORT 2204 -> 192.168.1.4:22
// etc
From what I can tell, chisel requires a chisel server running on the destination in order for the client to forward traffic from it.
Does Chisel have the capability to "simply" forward traffic to local IP/ports without needing chisel server running at the destination?
chisel forward --protocol UDP --target 192.168.1.3:3000 --listen 0.0.0.0:3000
chisel forward --udp -t 192.168.1.3:3000 -l 0.0.0.0:3000
From there I can create a bash script that maps all the ports appropriately
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 the existing chisel client/server forwarding behavior and the proposed chisel forward commands. Determine whether forwarding TCP and UDP traffic to local IP:port targets without a destination chisel server is supported; done would be a clear capability answer or an agreed implementation scope for the mappings shown.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100