Selfhosted

40137 readers

627 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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Spectrum Community WiFi (lemmy.world)

submitted 1 year ago by tgrowl@lemmy.world to c/selfhosted@lemmy.world

11 comments fedilink hide all child comments

Hi All,

Xpost from c/networking@lemmy.world

So since Reddit is out for me, I’m turning here to see if anyone has some insight or can comment on this. Anything you’ve got would be great!

Long and short, I made a quick decision and am now living in a “Spectrum Community” - whereby tenants are charged a fixed rate for Internet and TV and connect to a “mesh” network via captive portal where MAC addresses must be registered to the tennants. Everyone shares the same network, sorta, but it’s got that feature where no one can sniff each other (unless MAC addresses are registered to your name).

There’s some debate on posts regarding this, whether connecting your own gateway will cause an issue, but I would like to connect my own gateway / router. Now, I’d also like to port forward, as I run my own mail server, etc… which need this and a public IP address I can register with my domain in order for all the fun stuff to work.

I doubt I can connect the gateway / router and port forward as if the community were offering a “communal modem”, so the question becomes:

Can I defeat this “double NAT” by routing all traffic from MY gateway through a VPS? Then, can I tie my domain / proxy service to the public IP address of this VPS to make all my services work?

Other services I run: PiHole Unbound DNS resolving Emby Wireguard (for mobile access to PiHole) And other web based services

Again, thanks. Hopefully someone reads this and knows what I’m talking about. I believe in Lemmy.

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

[–] tgrowl@lemmy.world 1 points 1 year ago (1 children)

So I think I'm running into this problem a bit now. The reverse proxy and everything TCP and HTTPS works. The mail server I'm still trying to figure out. I'm using Wireguard to tunnel, do you know how to "bridge" that up to the VPS so that ports I need open to listen for incoming SMTP are also being listened on on the VPS?

[–] Oisteink@feddit.nl 1 points 1 year ago

WireGuard don’t do bridge. But smtp is tcp on port 25 and can go though proxy.

Note: you’ll need a ptr record for your VPS IP, not all providers allow this. You’ll also need to make sure your vps provider don’t block port 25. (like digital ocean)

What’s your current setup? VPS with reverse proxy and WireGuard to your home server/network?

I tend to use haproxy and would just add a tcp frontend on port 25 and have the backend point to my home-server WireGuard IP and the port I run my smtp server. Or the local ip - if your lan subnet is in the allow section of what config on the VPs side