Simple/noserver proxy for IPs on a local network

[alshdavid]

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

[jpillora]

No but I believe socat do it

…

On Wed, 29 Jan 2025 at 5:41 pm, David Alsh ***@***.***> wrote: 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. UDP PORT 3000 -> 192.168.1.3:3000 TCP PORT 3000 -> 192.168.1.3:3000 UDP PORT 8080 -> 192.168.1.3:445 TCP PORT 8080 -> 192.168.1.3:445 // 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? chisel forward --protocol UDP --target 192.168.1.3:3000 --listen 0.0.0.0:3000 — Reply to this email directly, view it on GitHub <#547>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE2X427FHQZOJIIX3IEPPL2NBZZ5AVCNFSM6AAAAABWCDX3GWVHI2DSMVQWIX3LMV43ASLTON2WKOZSHAYTOMZXG4YTANA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>