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:
- 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
The commercial VPN client part shouldn't affect your problem if I'm reading it correctly and you just want to access your LAN remotely. If you're hosting the Wireguard server on the router, you'll likely need a firewall rule for the port used by the wg server to allow inbound connections. And you need to configure
AllowedIPs
correctly on both server and client.Since you're using OpenWRT, you might try out Policy-based Routing which gives you a lot of control over this and also has some instructions for various server and client configs which may be helpful.
Also, if your ISP uses a CG-NAT you won't be able to do this without another publicly accessible device, although some ISPs will disable it if asked.
Silly question but how do I know if I'm behind a cgnat ?
If your public IP is in the
100.64.0.0/10
range, then you're behind a CG-NAT.