4 ms·
It is interesting to do a search of HN for past references to "Ubiquiti". Whenever the topic of routers came up, many comments followed that recommended them a
by 1vuio0pswjnm7 6y ago
It is interesting to do a search of HN for past references to "Ubiquiti". Whenever the topic of routers came up, many comments followed that recommended them above any alternatives. Commenters seemed proud to tell the world they were using Ubiquiti, as if the "HN concensus" for home routers was to choose Ubiquiti.
It seemed to me Ubiquiti would never allow customers the option to install their own OS (e.g., BSD) or boot from external media containing a non-Ubiquiti OS, without sacrificing the benefits of hardware specs that were likely deciding factors in selecting the Ubiquiti hardware above existing alternatives. The intent was clearly to have Ubiquiti retain control over the hardware after purchase. The customer effectively remained tied to Ubiquiti forever, so if the company started serving ads, using AWS unnecessarily, etc., there's no way to opt out. Customer is compelled to accept all updates.
Specs are important, but maybe not as important as control.
Reliance on third parties necessarily increases potential risk. Unnecessary use of third parties is, IMO, poor decision-making. This is of course rampant in "tech" and, IMO, marks a triumph of the salesforce for those third parties over common sense, possibly assisted by network effects. Further, I dislike products where there is a heavy focus on opaque "updates". Again, many customers have been trained to believe that not updating is always the wrong decision. (Meanwhile they have no idea what is in each update.)
As stated in one of the blog post comments:
"It is even worse: Ubiquiti forced all users to use cloud-based authentification even for accessing your controller software on a local network with a local client. This was not even properly communicated but deployed by one of the regular maintenance updates."
- myrandomcomment 6y agoI do not understand this comment. Ubiquiti sells turn key HW and there never was any hint that this was HW you could roll you own on. I could buy APs that I could install OpenWRT. I could setup an OpenBSD firewall. I could run my own DNS. I have done all this in the past. The point is I do not want to anymore. I have better things to do with my time. So as a turn key solution that is "prosumer" their kit works and I think you will find that is why most people here have recommend it. You can disable the Cloud connection and I posted how in this thread. People on HN are tech savvy enough I sort that part. The fact of the matter is they had a bad security breach and they have a cloud connected platform. Ops. That sucks. But the reality is that market forces have pretty much tied evaluations to cloud connections and telemetry gathered from it. That is the part that REALLY sucks. I do not blame them for trying to make money. I am angry if they were less then truthful in the details of the breach and I am sure both the SEC and the court of public option with punish them. For my part, I have no plans to replace the 4 switches in my house with boxes running SONiC nor the 4 APs with OpenWRT or my firewall with OpenBSD because I just really do not care to have to maintain it, and if I drop dead tomorrow my wife can likely sort the UniFi stuff (as I have documentation on the setup) but there is no way could she sort the roll you own.
- tjoff 6y ago"It is even worse: Ubiquiti forced all users to use cloud-based authentification even for accessing your controller software on a local network with a local client. This was not even properly communicated but deployed by one of the regular maintenance updates." Uh? that is demonstrably not true. Any more details?
- Cpoll 6y agoNo opinion myself, but someone did mention something to this effect in a different thread: https://news.ycombinator.com/item?id=26638671 https://news.ycombinator.com/item?id=26638671
- tjoff 6y agoThread only seems to handle about the cloud key, which is hardly everyone. I self-host and don't have the issue. But shady as f*ck and kind of sets the tone.
- KirillPanov 6y ago> It seemed to me Ubiquiti would never allow customers the option to install their own OS I run plain-vanilla Debian on all my Ubiquiti boxes, six or seven of them at this point. debootstrap --arch=mips Octeons are awesome. Ubiquiti hardware is the bomb. I hear their software is junk, but I wouldn't know anything about that, I always erase it right after unboxing the device.
- collinmanderson 6y agoI'd like to hear more about your setup, because I'm tempted to try something similar. How do you actually bootstrap it? How do you configure it? Just a bunch of iptables rules? How do you configure the WiFi? What packages do you install?
- KirillPanov 6y agoIt is literally just plain vanilla debian. See man debootstrap for details. Debootstrap is the tool that generates a "minimum bootable rootfs". You can use any existing debian install (even a non-mips architecture) to do the debootstrap. You will need to build your own kernel. Check the OpenWRT project for patches, although only a very very few Ubiquiti devices (USG-3 for example) need kernel patches. For other devices (EdgeRouter-4) the OpenWRT packages make things nicer, like getting the network device names to match what's printed on the front of the case. Put the kernel and rootfs on a USB stick, plug it into the router, attach the serial console (nice easy RJ45 jack on the front!) and boot. Once it's up you can migrate stuff to the internal soldered-down emmc. Octeons are awesome.