chisel + docker container cannot get reverse tunnel traffic
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hi, Im using chisel reverse UDP tunnel for wireguard which the wireguard server is a docker container
this is the container info:
47dd02e0a49b ghcr.io/wg-easy/wg-easy "docker-entrypoint.s…" About an hour ago Up About an hour (healthy) 0.0.0.0:22355->22355/udp, :::22355->22355/udp, 0.0.0.0:51821->51821/tcp, :::51821->51821/tcp wg-easy
22355 port is for wg server, 51821 port is for wg ui
when i establish chisel tunnel over udpwith port 2096 (in both servers) and set config tunnel to 22355, the wg docker container cannot get the reverse tunnel traffic
but same works with chisel reverse udp tunnel and wg installed without docker container
also same works with normal nginx udp tunnel and wg docker container
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 reproducing the reverse UDP tunnel with chisel port 2096 forwarding to the wg-easy Docker container's UDP port 22355. Compare it with the working non-Docker WireGuard setup and nginx UDP tunnel, and inspect whether traffic reaches the container; done means the Docker-hosted WireGuard server receives reverse-tunnel traffic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100