Selfhosted
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!
view the rest of the comments
In this scenario you could just get your own firewall to serve as an NAT gateway and connect its WAN port to the LAN side of your ISP’s gateway. You’d then have your own LAN you can do whatever you want on. The ISP’s device would provide the WAN IP to your gateway via DHCP, but that DHCP wouldn’t work through your gateway. You’d just make sure your new internal LAN(s) subnet is different from the one that exists between your firewall and your ISP’s gateway. The only problems this would cause in your scenario are because there’s now double the NAT going on, but if you’re already dealing with CGNAT then you’d already have those same problems.
Outbound traffic should all work just fine, and your ISP’s device would no longer have access to your LAN.