this post was submitted on 27 Nov 2023
4 points (100.0% liked)

Self-Hosted Main

535 readers
2 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 2 years ago
MODERATORS
communick@selfhosted.forum
4
Is self-hosting with the default Comcast residential router possible?? (alien.top)
submitted 1 year ago by Kjlw69@alien.top to c/main@selfhosted.forum
10 comments fedilink hide all child comments
 

I've been putting off switching to a cable-modem I bought a few months back, because of Comcasts tech. support.

I've also been trying to self-host services with tailscale(VPN)-caddy(R.proxy)-Pi-hole, but have been having little success.

I don't want to directly expose the NT IP. like with DDNS. I also don't want to use CF tunnels, b/c they route through CF and could cut me off from my service if I stream too much of my media.

With the Comcast default router/gateway they don't let you set custom dhcp or dns or dynamically FWD dhcp or dns to other devices.

Is this why the Videos on-line explaining self-hosting always say do what is best for you; but I bought this PFsense or expensive Unify router for example??

Is self hosting with a default router even possible??

I have a DDWRT as my wifi router already, and a second one I can place behind a plain cable modem; which I get I will have to call customer support to get working. I plan to use the First DDWRT with wifi disabled as my DHCP server, and have DNS forwarded to a pi-hole.

Is this the best idea for getting my services working properly??

you are viewing a single comment's thread
view the rest of the comments
[–] qjkxbmwvz 1 points 1 year ago

I'm in the same boat. Others have suggested CF (which you said you don't want to use) and TailScale or similar.

I opted for a "roll your own" approach and just use a free VPS (w/static IP) and a WireGuard tunnel. The VPS port forwards to my home server. It all works great for me. If throughput is a real concern then an entry level/free VPS might not be enough for you, but it's completely fine for my use.

No DDNS or anything is required. You can reverse proxy instead of port forward if you prefer.

I like this solution (VPS+WireGuard) because it doesn't rely on any particular third party or proprietary products; basically any VPS will do, so I'm not tied to any product in particular.