Selfhosted

41398 readers

949 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

Wireguard over TCP (linuxserver docker) (self.selfhosted)

submitted 2 years ago by elghoto to c/selfhosted

13 comments fedilink hide all child comments

Hi,

I would like to use Wireguard over TCP. I'm trying to reach my server from a restrictive network and UDP is being blocked. TCP is not blocked in certain ports though, and I would like to open a VPN server that listen on those over TCP.

I'm using the wireguard Linuxserver docker image. Any suggestions?

Thanks.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago) (1 children)

As long as you're certain your wireguard server works from other networks.. You could use nginx as a proxy to have your server accept incoming traffic from UDP port 53 (DNS)... But, be careful!

I would strongly suggest you whitelist the restrictive network for use on UDP port 53. Is the WAN IP static on the restrictive network? Do you know the size of the WAN subnet? I'd try a quick test over UDP port 53 using nginx, then close it up. If it works, create your firewall rule to whitelist only the restrictive network and Bob's your aunt.

PS: If the restrictive network uses DPI (deep packet inspection) to verify they are real DNS queries on UDP 53, you can try putting DNSmuggle behind nginx. Do not have anything listen on localhost:53 as that may interfere with your local DNS at the server side. I don't know how well this will perform, but I'm assuming not amazing. DNSmuggle supports encrypted DNS, which should prevent the network(s) from hijacking your requests.

[–] elghoto 1 points 2 years ago

I'm 100% sure it works from other networks. UDP 123 is filtered by ISP. Someone mentioned some other low UDP port.