docker-wireguard VS wstunnel

It’s probably better to just use the wireguard docker container setup instructions now: https://github.com/linuxserver/docker-wireguard?tab=readme-o...

I'm running linuxserver/docker-wireguard in Docker via docker-compose. It works great and I can access anything on my LAN via IP or DNS from my phone.

I'm trying to set up a Wireguard VPN server on an 2020 M1 Mac Mini running Fedora Asahi server through Docker.

You can add one to the docker compose file and then route other containers (especially qbittorrent) through it by setting network-mode. Read about it here: https://github.com/linuxserver/docker-wireguard

I checked /etc/sysctl.conf on the pi itself, and all lines are commented. Same on the docker container when I exec -it into it. https://github.com/linuxserver/docker-wireguard is the container I use

FWIW there is https://github.com/linuxserver/docker-wireguard/tree/alpine, which does just that really. It's a little more complicated because it still supports all the peer config envs, etc. but it's much smaller than the normal image because it doesn't have support for compiling and enabling the kernel module.

- I am using the linuxserver wireguard docker container: https://github.com/linuxserver/docker-wireguard

- deploy a VPN (I suggest that you have a look to docker WireGuard which I personnaly use)

Shameless plug, there is also wstunnel (i am its author) https://github.com/erebe/wstunnel/, hope you enjoy.

If you want to tunnel UDP (WireGuard) or TCP (SSH) over WebSocket protocol, check out https://github.com/erebe/wstunnel

While working in an environment where VPN connections were pretty much all blocked⁰ a friend of mine had success using https://guacamole.apache.org/ to access a remote machine¹. Not quite the same as a direct VPN connection but worth a try if nothing else functions, it looks enough like normal HTTPS traffic that he got away with it.

To keep your wireguard setup more as-is, you could try https://kirill888.github.io/notes/wireguard-via-websocket/ to tunnel that via a web server. In fact https://github.com/erebe/wstunnel which that uses could be used just as well with any other UDP based VPN.

I once tinkered with https://github.com/yarrick/iodine and successfully connected to resources over the wireless on a train, bypassing its traffic capture and sign-up requirement, so that might be an option, though I think fully blocking external DNS is more common now so this is less likely to work²³.

--

[0] practically only HTTP(S) permitted, not even SSH, DPI in use that detected just using SSH or OpenVPN over port 443

[1] NOTE: be careful breaching restrictions like this, you are at risk of an insta-sacking if discovered, or worse if operating in some securiry environments!

[2] and the latency when it does work is significant!

[3] and that much traffic over port 53 might get noticed by the heuristics of data exfiltration scanner, encouraging sysadmins to notice and implement a way to block it

You can try with this project, https://github.com/erebe/wstunnel.

There are projects out there (like this) which run wireguard traffic through websocket.

There are tools to tunnel all your traffic over websockets kind of like a VPN, for example: https://github.com/erebe/wstunnel This would be an easy way to get access to web content blocked by corporate policy, expose internal services to the outside world, or even exfiltrate a bunch of internal data somewhere else.