The only thing is they're definitely not designed for regular consumers, you at least need familiarity with Linux networking.
The only thing is they're definitely not designed for regular consumers, you at least need familiarity with Linux networking.
Ubiquity gear is structured the same way: It, too, absolutely runs Linux, and it uses a custom userland.
One of these userlands is friendlier than the other, but they're both still Linux.
It's a tale as old as the hills, or at least as old as the OG Linksys WRT54G -- which was my own first foray into owning dedicated routing hardware ~20 years ago (which was -- guess what -- Linux with a custom userland). (Previous to that, I used Linux with the userland of my choosing on my desktop PC.)
From that point I found the CLI to be relatively discoverable as a way to configure the devices.
I like RouterOS well enough, though.
So I installed openwrt. They're actually pretty well supported by openwrt (except for the newer 10g switches)
You mean an RFC1918 for etherboot? I have a "few" of these devices and this simply doesn't make any sense in any context.
I've since wiped the firmware/license keys so no idea.
Mikrotik has had quickset (a single page configuration for home use) for 8+ years, Android Home app for 3+ years
port forwarding? ofcourse how else can the kid have a minecraft server with friends
dynamic dns? then the friends don't need to search "what's my ip" every time
parental controls? to schedule how much time they can play minecraft...
I like Mikrotik but for anyone trying to go beyond the barebones default firewall/router/ap on the quickset page you need to be prepared to learn. i.e. To make a DHCP reservation, you go through the menus until you click IP, then you realise you don't click on DHCP client to set up a DHCP client you go into DHCP server and try to give a device a reservation which requires the step of making it static first then seperately setting it's IP.
The complaint basically boils down to: they have all the options there and available and the least common task is just as easy to do as the 2nd most common (after initial basic setup), and if a task touches multiple parts of the config you need to touch each of those parts. Great for someone who knows what they're doing but for a home user it would be great to have more quickset pages for the 2nd to 10th most common tasks (as intagible as that list is).
I tell people to jump into Ubiquiti's (ui.com) ecosystem which is much more accessible for power users who occasionally wrestle with concepts like wireless, VLANs, subnets, and traffic rules.