Conceptually, it’s fairly easy to understand - nftables, relayd, likely some firewall application.
However, is it as simple as configuring the WAN port as the WiFi interface and leaving it at that? Note that I’m not bothered about double NAT since I won’t be opening any ports, and the main router cannot be touched.
I do want my own SSIDs, my VLANs, control over the firewall etc. Basically, my own network space. If anyone has done this/has an idea of the problems I might run into, please do comment!
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
3 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.
[Thread #585 for this sub, first seen 10th Mar 2024, 07:45] [FAQ] [Full list] [Contact] [Source code]