text stringlengths 9 408 |
|---|
[541.66 --> 543.62] The QA has for sure been declining. |
[543.78 --> 553.50] You know, there's been several firmware upgrades for the actual APs themselves, as well as the controller software that have nuked people's databases and history and stuff like that. |
[553.50 --> 560.24] I wonder if maybe just some original people left the company a while ago and it's been in decline or if their prioritization has changed. |
[560.34 --> 561.38] But where do you go to? |
[561.46 --> 562.54] Like, what do you change to? |
[562.80 --> 565.60] Well, I actually asked Jim on Twitter what he thought. |
[565.74 --> 568.28] And he's been recommending there's a bunch of TP-Link devices. |
[569.12 --> 572.44] And Tom from Lawrence Systems just got a bunch in to review on YouTube. |
[572.66 --> 577.16] So if you're interested in some Ubiquity alternatives, they are out there. |
[577.78 --> 579.98] But I'll tell you what worries me the most about this breach. |
[579.98 --> 586.30] It's not necessarily that it happened because, unfortunately, these things are going to happen at some point to every company. |
[586.84 --> 589.88] What matters more is how a company responds. |
[590.96 --> 594.90] And Ubiquity tried to basically cover this up. |
[595.36 --> 597.28] They didn't deny, I suppose is more accurate. |
[597.46 --> 598.86] They didn't deny these claims. |
[598.86 --> 610.42] And it took them several days, more than a week, to admit responsibility and basically inform their user base that some of their stuff might be boned. |
[610.84 --> 610.94] Yeah. |
[611.10 --> 620.50] And on top of that, it seems like it's taken some insiders to come out and leak information to well-known people like Krebs to get the complete picture, which is disappointing. |
[620.50 --> 622.78] Yeah, I think you just hit the nail on the head there. |
[622.84 --> 623.40] It's disappointing. |
[624.14 --> 632.90] I mean, Ubiquity made their name through basically making people realize how crappy consumer-grade gear is. |
[633.56 --> 640.06] And, you know, they're providing Cisco-grade ideas and hardware for consumer-grade prices. |
[640.06 --> 645.98] But with these kinds of breaches and behavior as a company, I'm struggling. |
[646.22 --> 655.94] I mean, the access point that I'm looking at behind my monitor here, I first installed into a house that I lived three houses ago, six, seven years ago. |
[656.06 --> 657.24] And it's not Mr. Beat. |
[657.32 --> 658.06] It still works perfectly. |
[658.96 --> 661.04] It's had all the firmware updates and that kind of stuff. |
[661.42 --> 668.94] But there was that one issue with the controller a few months ago where I ended up having to completely rebuild my Unify controller because of poor software QA. |
[668.94 --> 671.56] It's critical infrastructure in my house. |
[671.78 --> 672.76] Okay, it's not a hotel. |
[673.04 --> 676.96] It's not a commercial setting where a lot of people do deploy Unify gear into. |
[677.58 --> 680.20] But if it happens to me, it's going to happen to those people as well. |
[680.44 --> 686.34] And it only takes one or two or three incidents before your brand name is completely trashed. |
[686.34 --> 708.34] And people are already talking about just going back to consumer-grade stuff like mesh networks like Aero and, you know, all these other, you know, not as technically accomplished solutions that have, you know, POE backhaul and stuff like that in favor of something that is possibly even more leaky ... |
[708.52 --> 708.86] I don't know. |
[708.86 --> 710.48] But what's the solution? |
[711.18 --> 714.52] I'm probably just going to wait and see how this turns out for the next six months. |
[714.80 --> 718.58] But my next AP will probably not be a Unify one. |
[719.00 --> 723.78] Wouldn't it be something if the community stepped forward and built something that we could flash again? |
[724.10 --> 724.64] Mesh networks? |
[725.30 --> 725.82] Be amazing. |
[726.14 --> 726.72] Oh, it'd be cool. |
[726.80 --> 727.22] I tell you what. |
[727.22 --> 739.30] If somehow we could open these devices up, these Unify devices we already have, and then put like a Tasmota style, completely divorcing ourselves of Unify, of Ubiquity, sorry. |
[740.26 --> 741.60] You know, own the hardware. |
[741.74 --> 743.24] I keep banging on about this, don't I? |
[743.30 --> 744.54] But own the hardware. |
[744.72 --> 746.50] It's not dependent on a cloud service then. |
[746.96 --> 748.94] It does seem like that is exactly what we need. |
[748.94 --> 759.58] It's something we could reflash and load a common OS on that has a common set of standards and interfaces and a web UI, like you used to do with the old Linksys routers. |
[759.64 --> 762.52] You know, those things are still being sold today, those old Linksys routers. |
[762.66 --> 763.88] Open WRT, yeah. |
[763.88 --> 770.62] We just need a newer version of that, something more powerful with different hardware options, essentially like the Ubiquity options. |
[770.96 --> 783.06] Because you're right, you need something for folks that want to run PoE and then, you know, plug an AP at the end of a barn somewhere or at the end of a building somewhere and they can only run one cable. |
[783.20 --> 784.76] Like, you've got to have something for that solution. |
[785.10 --> 793.66] I think your use case, too, where you've got several buildings and you want to manage all of the APs with one interface is also totally legitimate and extremely common. |
[793.88 --> 799.74] It's so useful when my dad rings me up and he's like, oh, my Wi-Fi is not working in the bedroom. |
[799.88 --> 804.32] I can go in and see the AP has dropped from gigabit down to megabit, for example. |
[804.52 --> 807.94] And I'm like, oh, we just need to reboot the AP and we're good to go. |
[808.26 --> 811.20] But there's a way to do that, Alex, you know, and get that central dashboard. |
[811.20 --> 816.22] I know you don't use it much, but something we should talk about at some point on the show, maybe, is Cockpit. |
[816.68 --> 823.16] One of the things I appreciate about Cockpit is they have come up with a way to allow you to manage multiple servers. |
[823.16 --> 830.16] You can go to one UI, though, log into one web server, and you can select all your servers and manage them. |
[830.58 --> 832.08] And it has to be set up in a special way. |
[832.16 --> 835.58] And there's some security precautions you have to take, but it's a very secure setup. |
[835.78 --> 837.96] And so maybe something like that could be done. |
[838.76 --> 839.08] I don't know. |
[839.10 --> 840.68] Maybe somebody out there in the community knows. |
[841.14 --> 841.22] Maybe. |
[841.22 --> 841.34] Maybe. |
[841.74 --> 854.64] So I found out this week that a device I purchased nearly two years ago on some Black Friday sale, you know, I bought it thinking, oh, yeah, this is going to solve all my problems with my fans. |
[854.64 --> 867.88] Because quite often when you buy a server-grade motherboard, the fan control headers are designed for server-grade fans, which spin at crazy high RPMs and draw crazy amounts of current and stuff like that. |
[868.48 --> 878.10] And so when you put a consumer-grade fan on one of these motherboards, it kind of ramps up and then ramps down and ramps up and ramps down because it's not getting enough of a signal to think it's got enough RPMs. |
[878.10 --> 880.02] Anyway, it's this whole thing. |
[880.36 --> 883.36] So I bought this device called the Corsair Commander Pro. |
[883.72 --> 892.56] It plugs into a USB header on the motherboard, controls LED lighting, it controls fans, and has some temperature probes attached to it. |
[893.30 --> 895.96] But the downside was this device was Windows only. |
[896.56 --> 903.46] To my surprise and absolute delight, six months ago, this device has been added to the Linux kernel. |
[903.46 --> 911.22] There's been a driver added to the Linux kernel, so you can now natively control fans via a USB header on Linux. |
[911.72 --> 912.88] I love it when that happens. |
[913.64 --> 915.32] And you're always surprised, like, my little thing? |
[915.58 --> 917.18] The little thing that I care about? |
[917.26 --> 917.80] That's coming? |
[918.18 --> 919.30] That's always the best feeling. |
[919.58 --> 921.40] So I wrote a small blog post about it. |
[921.50 --> 926.20] It doesn't require an awful lot of elbow grease to get set up. |
[926.46 --> 930.46] But you do need to have the 5.9 or later kernel. |
[930.46 --> 933.56] And then you need to make sure you've got LM sensors installed. |
[933.76 --> 938.18] And then there's a couple of other instructions in the blog post about how you configure the PWM profiles. |
[938.80 --> 941.74] And then once you've done that, you just enable the fan control service. |
[941.90 --> 946.66] I mean, I'm using a very tiny, tiny little Arch VM on my ESXi host. |
[947.42 --> 951.86] I think it's using 256 megs of RAM, for example, and 4 gigabytes of disk. |
[952.24 --> 955.44] Perfect use case for Arch because I don't want anything else. |
[955.44 --> 956.66] And I want a modern kernel. |
[957.58 --> 959.60] And that's exactly what Arch gives me there. |
[960.46 --> 963.08] Linode.com slash SSH. |
[963.18 --> 966.50] Go there to get $100.68 credit towards a new account. |
[966.70 --> 967.90] And, of course, you support the show. |
[967.98 --> 968.36] $100! |
[969.12 --> 970.04] And that's a lot. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.