86
Self Hosting for Privacy - Importance of Owning your own Modem/Router?
(self.selfhosted)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Mar 2026
86 points (100.0% liked)
Selfhosted
61475 readers
570 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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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 3 years ago
MODERATORS
The only thing they can realistically harcode is the DNS server their router's DHCP provides.
Just configure devices to not use that setting, also use DoH or DoT (which you should do anyway, not just to circumvent your router's settings).
I haven’t used such a router in decades, I just know from doing IT support at friends homes. These people have no clue how to get around these DNS filters.
But not thanks to the virtue of some effective blocking but just a lack of knowledge of the average user...
I have used several of those cheap routers over the years. And they simply can't block you from using encrypted DNS (unless they want to create giant blocklists and want to play wack-a-mole with DNS servers...).
So all they usually do is very low tech like ignoring the DNS you set in the router configuration and reroute it (or not providing such configuration in the first place). But they can effectively ony do so with unencrypted DNS.
With encrypted DNS they could at best try to block the default port used by DNSoverTLS but that still leaves DoH. And they can't block that because it's just regular encrypted HTTPS traffic (with the DNS quesry inside).
Iirc even Windows allows easy configuration of DoH nowadays (and for much longer if you were ready to edit the registry) where you can simply chose between unencrypted, DoH only or encryption preferred if available.