Selfhosted

40693 readers

790 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

VPN blocked, how can i tunnel my VPS to home network? (lemdro.id)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/selfhosted

44 comments fedilink hide all child comments

I live in a country where wireguard, openvpn and other vpn protocols have been blocked. Tailscale and Cloudflare Tunnels don't wok either. I do have a public ip and my router supports DMZ and port forwarding. For security concerns I'm not willing to forward ports. Is there any other method to use my VPS to forward traffic to my home server?

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

[–] zikk_transport2 6 points 1 year ago (1 children)

Some time ago I've done a "public IP implementation" on my VPS when I was on mobile network (no public IP).

Basically set up IPSec/Wireguard on VPS and connect your router to it. Then setup EoIP over VPN between VPS and your router. Then add EoIP tunnel to your LAN's bridge in your router.

Then setup all ports forwarding (using iptables) from your VPS to your router on LAN, so if you connect to your VPS using tcp80, it will be simply forwarded (NAT'ed) to your router. Except tcp22, for SSH to your VPS obviously...

And now you have yet another public IP lol.

This is not something you asked, but might give you some ideas.

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

So that setup effectively gives you an all-ports available connection (except 22) from your mobile device and anything that connects through it, like a laptop? The exit node would be the VPS.

Could I skip the home router and EoIP+VPN directly between mobile and VPS, for instance?

I am in a situation (restrictive firewall on ethernet/wifi, prefer personal mobile connection but it's cgnat or something equally crap) this could be very useful for me.

[–] zikk_transport2 2 points 1 year ago

Technically like this:

Anyone -tcp80-> vps -tcp80-> router -tcp80-> homeserver.

Exit of homeserver-originated traffic would be your router, not vps. Unless you specify custom routes in your router, then yeah, might be possible.

Also you don't need EoIP tunnel at all, since it's all in Layer4.