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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
Thank you, a short reset worked!
But how do I set up the routing correctly on the WireGuard router? What should the Target Address and Gateway be if my LAN is under 192.168.8.0/24, and my mobile client with the WireGuard client has a client IP of 10.0.0.2/24?
So you have a single mobile device connecting via wg, correct? Not a second network?
If so the only configuration you should need on the router are firewall rules to allow forwarding from wg to lan. I am guessing that's what the second step in the GL-iNet help accomplishes. That's what I would recommend trying.
If I was doing this on "normal" OpenWRT I would create a firewall zone wg, and allow traffic to/from it and lan.
On the client device you should be good to go without changes if AllowedIPs is set to 0.0.0.0/, ::/0 (sending all traffic through wg).
thanks a lot