As in the others that I _won't_ buy (which is what I meant)?
I wouldn't buy Netgear, Asus, D-Link again. My ISP gave me Eero and I've never connected it, far too much Amazon crap going on there (but I have to keep it if I want the ISP to provide support).
Gl.iNet has been OK for the price but re-flash it with vanilla OpenWRT because their OS has some dubious phone home stuff (or did last time I looked at it).
Honestly, in terms of routers, I'm never likely to use something off-the-shelf again a decent box with Intel NICs that can run OPNSense and preferably run Coreboot (or similar). If I did go with something COTS (Commercial Off The Shelf), I'd look at Mikrotik.
I'm not a massive fan of Ubiquiti but I have their APs and I've had a bunch of their EdgeMAX switches (sadly discontinued when some of their best devs left), and their APs have been solid for me for the best part of a decade.
The advantage of using dedicated components is that each can be chosen according to your requirements.
> As in the others that I _won't_ buy (which is what I meant)?
Correct. Sorry, worded the question a bit too ambiguously :)
What kind of trouble did you have with ASUS and D-Link? Security or the lack of configuration options? Haven't bought them in a while, but I remember them being somewhat decent.
I'm quite frequently in the market for a simple home router/AP for friends and family, and they'd rather have something simpler and cheaper, so that rules out Mikrotik (which I would normally go for). Would love to hear some stories about the issues you've had with all kinds of off the shelf stuff if you have the time.
On the other end I can recommend FritzBox. Rock solid and has a lot more bells and whistles than I expected, like wireguard support, NAS-like access by attaching USB storage, and more graphs than I know what to do with. It's the happiest I've been with an electronic purchase in a long time.
I tried out quite a few products and brands. I've settled on opnsense running on a spare x86 based machine with an intel x550 T2 NIC that I got off of ebay. My only regret is not making this switch earlier.
The UI was tidy and nearly perfect, now it's all over the place: weird paddings, different border radiuses even within a single element, clashing background colors, and boy, do I love rainbow gradients everywhere.
Update: for those unhappy with the changes, you can roll them back for now:
Thanks for the config. To their credit the UI change is instant. I double clicked a few times to find out why the old UI looks better.
The old UI has less visual noise (at least dark mode on Windows). The new theme has random highlights and high-contrast lines everywhere that draw attention to the browser UI. I want the browser to fade into the background not stand out.
You can browse the Themes to try to find one you like better. But yeah it'd be nice if one of the default built-in themes was super plain. Closest they have available by default is a grayscale gradient ("Ash").
Then separate UI updates from security updates. No need for them to be bundled. Gradients and insane padding pushing people to not update make them inherently less secure!
It's possible to stick to an ESR release to avoid feature updates in the past, but recently, Mozilla has started bundling feature updates into bugfixes.
I absolutely despise when people commit their personal ignore patterns. My opinion is that the code in the repository shouldn't know anything about personal environments. The exception is when the entire team benefits from having their common ignore patterns in the repo - in this scenario, the environment details are no longer personal and it doesn't make much sense to not commit them. In any other situation, people are perfectly capable of ignoring their crap on their own and shouldn't pollute the repo. Glad .git/info/exclude is getting more exposure.
It depends on whether the pattern is general enough to potentially be useful for others. If it is, then by all means add it to .gitignore. If on the other hand it's specific to the user, e.g. '2026_report.docx', then no, it should not be added.
> I absolutely despise when people commit their personal ignore patterns.
Beyond things not being neatly compartmentalized, what is the problem? The only risk I see is that you'll have a file you forgot to commit because it happened to match one of those patterns.
Having strong opinions on stuff like this is not healthy.
- I've been able to notify the clients that we are going to have to take urgent action;
- Had some time to figure out what actually happened;
- Set up monitoring to know when the fix is out;
- Managed to compile the new binaries the moment they became available.
reply