[scrlk]

I've been considering MikroTik recently (specifically the RB5009 series). Main downside I've read about so far is that the UI/UX is a bit rough.

[cyberax]

I don't get all the Mikrotik UI hate. It's not winning any beauty contests, but it's straightforward and it works well.

I've been using their devices for years, and I haven't had any problems setting them up.

[favorited]

There are some really terrible UI choices in SwOS, like not labeling rows of checkboxes so users need to hover over each one with their mouse to see a tooltip.

[cyberax]

Send them a bug report, they'll likely fix it. I'm not joking, they're not using Webfig often, so sometimes they can overlook these kinds of minor issues.

[lbotos]

I have a mikrotik https://mikrotik.com/product/hap_ac3 that I bought as a sort of test and it's been working fine for my needs. the webUI isn't the best, but wiki docs were pretty straightforward and I've been decently happy.

[bastard_op]

You think the UI is rough, try the cli.

[lillecarl]

There's a learning curve indeed, but it's also essentially just a thin wrapper around nftables (read iptables) so you learn about Linux networking by using them

[bastard_op]

I've been using unix and linux since the 90's and linux full-time on every system of mine, and Tik's still seemed entirely counterintuitive to me. I'd rather just deal with iptables and linux directly without the wonky cli.

[doubled112]

I actually found the Mikrotik CLI easy to learn because it and the GUI are basically 1:1.

For example:

/ip/firewall/filter add

is in the UI under the sidebar IP -> Firewall, then the Filter tab, then click add. The parameters are named the same in both too.

[sonicanatidae]

I prefer the cli for Mikrotik, but that's true for most firewall, routers, etc.

YMMV.