News for hackers. Stuff that matters.
Re:How we solved our office Wi-Fi problems by dogecoinbase on Wednesday September 26, 2018 @07:47PM (#18081203)
_Thank you_. I'm constantly astonished to see folks extolling UBNT gear for anything other than WISP purposes (where it admittedly fits a price profile that's unmatchable). Read about the first ~10 months of the ES16-XG DAC support issues. Read about how EdgeRouters could never approach even 40% of line rate with fq_codel running. Read about how they lied about the future of the mFi line for 8+ months before abandoning it entirely. Not to mention the GPL stuff you note, the inconsistent and semi-nonfunctional PoE, and general lack of support or consistency.

At some level, you really do get what you pay for. They are great for people who want to set up a "homelab" without learning anything about actual networking, though.

Re:How we solved our office Wi-Fi problems by tacoman on Wednesday September 26, 2018 @08:12PM (#18081303)
Or $1000 switches that fail outside of warranty with no replacement power supplies available. https://community.ubnt.com/t5/UniFi-Routing-Switching/Failed...
Re:How we solved our office Wi-Fi problems by Serow225 on Wednesday September 26, 2018 @09:59PM (#18081650)
Whats the better alternative to fit the needs of a shoestring startup (say 5-10devs)?
Re:How we solved our office Wi-Fi problems by benjaminl on Wednesday September 26, 2018 @11:00PM (#18081848)
I have had good experience with MikroTik products. The are at a similar price point, but with a less refined interface but a lot more flexibility.
Re:How we solved our office Wi-Fi problems by jtl999 on Thursday September 27, 2018 @12:15AM (#18082086)
Mikrotik suffer from a gross amount of "Not invented here" reinventing existing open source protocols such as OpenVPN, a custom sshd and web server, and it shows with their amount of issues (how many years has it taken to add UDP to their OpenVPN server?). In some ways I think their no better then UBNT in some ways.

Tell you what. I used to have a Mikrotik CRS125 switch in my home office, and by default if you have a set of ports where one has no VLAN assigned, and the others have untagged VLAN assignmnets, any broadcast traffic on the untagged port(s) without a VLAN leaks to the ports with an untagged VLAN. This isn't well documented in the manual, and to fix it you either disable "Invalid VLAN Forwarding" (I think) and/or move said ports without a VLAN to a VLAN.

Re:How we solved our office Wi-Fi problems by ausjke on Friday September 28, 2018 @03:30PM (#18096333)
Many of Mikrotik can be loaded with debian or openwrt, its hardware is solid
Re:How we solved our office Wi-Fi problems by jtl999 on Friday September 28, 2018 @06:28PM (#18097585)
My CRS issue suggests otherwise (could just be CRS), but ignoring OpenVPN I haven't had many issues with RouterOS. It's good to have the option though.