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
I have thought about that, the issue is I'd need to re-run all but 1 of my Ethernet cables to a place where I can put the Celeron box. Once I start messing around with VLANs this is probably what I'll do, but it's going to be a big project.
I'm definitely going to give Adguard Home a shot.
Any thoughts on the best solution for now, basically putting the firewall in between the router and modem? If I plug it into a LAN port on the router and set up DHCP so it is the new gateway, that should work, right? I really wish I could plug it into the WAN port but I don't think DHCP will traverse the WAN to LAN ports on the router.
Just to confirm, you don't have space next to your modem and/or router for the new Celeron box, correct?
I'm not sure how good of performance you would have if you run the firewall on the Celeron box connected to the LAN portion of your current router, but you could always give it a shot and if it doesn't work the way you'd like it to then you could try a different solution. From my understanding this setup would cause all traffic to go through your router at least 2x (even if it's only on layer 2 via the built-in switch.) it may not be that much of a drain though, I've never run a setup like that before
The best layout would be modem -> opnsense router -> Tplink device running in AP mode. From what you've said that doesn't sound feasible at this time. You might be able to utilize a bridge mode somehow, but at that point I'd be guessing since I don't remember much about the tplink consumer router capabilities
Sopuli seems to be down, so responding from a different account.
Yeah, it's actually that there isn't power for the Celeron box where all the other Ethernet currently is.
Just so I'm understanding, why would all traffic need to go to my router (do you mean the opnsense one or the tplink one) twice? Wouldn't it go Device -> Switch -> opnsense -> modem > internet? Or for my intranet communications, Device1 -> switch -> opnsense -> switch -> device2
OPNsense is a gateway/firewall/DHCP/router my network looks like this
optical to Ethernet conversion (the isp's things) -> opnsense box -> network switch -> all other device (including wifi APs)
all traffic gets routed thru the opnsense box as it is the gateway to my network, runs the ipv4 nat and DHCP server
router in their comment refers to the the one that actually touches the Internet