74
submitted 3 months ago* (last edited 3 months ago) by UberMentch@lemmy.world to c/selfhosted@lemmy.world

My Linksys router died this morning - fortunately, I had a spare Netgear one laying around, but manually replacing all DHCP reservations (security cameras, user devices, network devices, specific IoT devices) and port forwarding options was a tedious pain. I needed a quick solution; my job is remote, so I factory reset the Netgear (I wasn't sure what settings were already on it) and applied the most important settings to get the job done.

I'm looking for recommendations for either a more mature setup, backup solution, or another solution. Currently, my internet is provided from an AT&T ONT, which has almost everything disabled (DHCP included), and was passing through to my Linksys router. This acted as the router and DHCP server, and provided a direct connection to an 8-port switch, which split off into devices, 2 more routers acting as access points (one for the other side of the house, one for the separated garage, DHCP disabled on both).

If going the route of a backup solution, is it feasible to install OpenWRT on all of my devices, with the expectation that I can do some sort of automated backups of all settings and configurations, and restore in case of a router dying?

If going the route of a smarter solution, I'm not sure what to consider, so I'd love to hear some input. I think having so many devices using DHCP reservations might not be the way to go, but it's the best way I've been able to provide organization and structure to my growing collection of network devices.

If going with a more mature setup, I'm not sure what to consider for a fair ballpark budget / group of devices for a home network. I've been eyeing the Ubiquiti Cloud Gateway + 3 APs for a while (to replace my current 1 router / 2 routers-in-AP-mode setup), but am wondering if the selfhosted community has any better recommendations.

I'm happy to provide more information - I understand that selfhosting / home network setup is not a one-size-fits-all.

Edit: Forgot to mention! Another minor gripe I have is that my current 1 router / 2 routers-as-AP solution isn't meshed, so my devices have to be aware of all 3 networks as I walk across my property. It's a pain that I know can be solved with buying dedicated access points (...right?), but I'd like to know other's experiences with this, either with OpenWRT, or other network solutions!

Edit 2: Thanks for the suggestions and discussion everybody, I appreciate hearing everybody's recommendations and different approaches. I think I'm leaning towards the Ubiquiti UCG Ultra and a few Ubiquiti APs, they seem to cover my needs well. If in a few years that bites me in the ass, I think my next choices will be Mikrotik, OPNsense, or OpenWRT.

you are viewing a single comment's thread
view the rest of the comments
[-] fubarx@lemmy.ml 5 points 3 months ago* (last edited 3 months ago)

I have a closet full of old routers (including Linksys), extenders, and switches to be able to handle dead spots. They all sucked. Then I heard about mesh routers when they first came out. Tried two, saw that they worked well, and got a third one. A few months later, a new ISP showed up in our neighborhood with unmetered Gig fiber and I happily drop-kicked Comcast to the curb. It was gratifying that the fiber connection came with a single mesh device of the same brand I already had. Since then, I've upgraded to the next-gen routers, and gotten a few smaller 'wall-wart' units for extending the range outdoors.

I don't really have to fuss with configurations like I had to before. It's amazing how much of a time drain it was to go screw around with settings when a new device came in that didn't work, or to replace a router when one died. I haven't had to do anything in years. Every once in a while, I go set up a DHCP reservation but that's it. The firmware updates auto-install while everyone's asleep and I get pretty decent bandwidth in places I had constant dropoffs. When I switched out the actual routers to the new gen, the whole thing took 10m and the whole network was down for maybe 2m while the new ones booted up. No end devices had to be modified or restarted.

Where the fiber comes in, there's a single router node, with two Ethernet ports. One goes to the fiber ONT, the other to a 10-port gig switch where it feeds the rest of wired setups. Elsewhere, the farthest mesh unit has no incoming physical connection, but a small wired switch connected to other wired devices near there. I didn't have to make any router configuration settings to make this work. Just plugged it all in. Common devices go on the main network, and janky IOT devices (and visitors) go on the guest network.

For external access for self-hosting, you can take a domain name and set up a free Cloudflare tunnel to access your in-home services remotely. Pay Cloudflare a fee and you get extra rules-based access control. The router also has a premium service where it comes with a family bundle of security software. One other thing I like is that the mobile app sends a notification whenever a new device joins the network, so if I see one I don't recognize, I can block them. Hasn't happened yet, but if it does, I'll know to go rotate the wifi passwords.

Anyway, highly recommend mesh routers. I happened to get Eeros (before they were acquired) but there are a few other brands around. Some people don't like that Amazon bought eero, but they appear to be left to run as an independent outfit. It has been pretty solid so far.

~~P.S. A friend with a more complicated setup than mine got Ubiquitis. It's anecdotal, but he recently asked about switching away and I told him pretty much what I've written here. YMMV.~~

Edit: checked back with friend. He said he was very happy with his Ubiquiti gear. I mixed up his review from years ago with another friend's networking setup.

[-] UberMentch@lemmy.world 1 points 3 months ago

Sounds like we have similar experiences, I'm definitely looking at mesh. I'm tired of having multiple networks across the house! I'm definitely looking at separating IoT and guests to their own VLAN, which I understand Ubiquiti devices are really good at facilitating. Having notifications for new devices is a really nice feature that I never really thought about. Would definitely be nice to have tracking for that

[-] sugar_in_your_tea@sh.itjust.works 1 points 3 months ago

But Ubiquiti can absolutely work in mesh mode, what exactly is your friend looking to solve?

I personally have a Mikrotik router (just router, no wifi) and one Ubiquiti AP, which gives really good coverage in my house. I'm going to be getting faster speeds soon (city is rolling out muni fiber), so I'll want something better than my current AC AP since the 5MHz band doesn't cover my whole area and technically can't saturate gigabit (I might try out 10 gbit, but I'd need a new router). So I'm thinking of running a bunch of cable and getting two U6 Lite APs and then switching to wired for our desktops. I could probably even keep using my AC AP, and just put the U6 where people will more likely get closer to the max (probably downstairs where we play games).

My main concern with a mesh setup is that, while it's easy to set up, there would be added latency from going through repeaters and whatnot vs two APs with a direct line to the router working off the same SSID. Running cable kinda sucks, but the total cost seems about the same between a mesh setup and a dedicated AP setup.

[-] fubarx@lemmy.ml 2 points 3 months ago

Thanks. After your note I went back and re-checked with my friend. I mixed up his comments with those from another friend with a different setup. Updated my original comment.

this post was submitted on 14 Aug 2024
74 points (96.2% liked)

Selfhosted

40183 readers
384 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS