Cloak VS wstunnel

You can try cloak? It is meant to circumvent these types of bans.

Already saw this Cloak Underlying proxy configuration guides but could not understand how to do it with outline server.

does this might help you ? https://github.com/cbeuw/Cloak

>it's not clear that Cloak does anything novel when compared to existing systems.

I'm not an expert on censorship-circumvention utilities but I found this comment when browsing the Cloak source repository that may partially answer your question:

https://github.com/cbeuw/Cloak/issues/169#issuecomment-12574...

>, and how do you prevent the censoring regime from finding and blocking them?

The tools like Cloak try to work on the principle "collateral freedom" which hides censored data inside of "internet services that are too big block" : https://en.wikipedia.org/wiki/Collateral_freedom

And the effectiveness of that strategy depends on the hackability of those internet services as they can sometimes change the rules which close the loopholes of "collateral freedom" : https://en.wikipedia.org/wiki/Domain_fronting#Disabling

I recommend https://github.com/cbeuw/Cloak which is designed for this use case.

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.