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
Do you even need relayd? I think relayd is for extending the existing NAT, i.e. a wireless bridge operation. At least that's how I utilized it in a previous setup. If you want to have your own NAT, I think it's enough to just connect to the upstream wireless network as a client. Not sure if you have to designate the wireless interface as WAN or not.
How would you do this? What would be the steps you take to create a double NAT + Firewall + DHCP server with the OpenWRT router behind the main router?
I think you basically need to do this. I see it mentions the wifi interface becoming WAN too.
Thank you!
Depends if you want to assign IP addresses or not. If you don't, you just want your own section of the same lan, I.e.all your devices connected to your router but let dhcp pass through then you can just set itnup as an extender
He mentioned that he wants to create Second level Nat, that will require new IP addresses and DHCP in the subnet