text stringlengths 9 408 |
|---|
[1348.46 --> 1351.84] We basically got our RV lady Joops parked. |
[1352.12 --> 1353.64] We got her hooked up to power. |
[1353.86 --> 1355.44] And then I jumped in the car. |
[1355.82 --> 1357.20] I ran down to the studio. |
[1357.28 --> 1358.56] I'm like, what's going on? |
[1358.58 --> 1359.72] And I think, you know, I don't know, Alex. |
[1359.76 --> 1363.92] It's like maybe it's the ex-server admin in me from years past. |
[1363.92 --> 1368.16] But just knowing that my server's down drove me nuts. |
[1368.20 --> 1380.48] Even though, like, I had taken steps to replicate the essential functionality, just knowing it was down and not knowing what state it was in and was in some weird state where the fans were blasting or what, you know? |
[1380.48 --> 1383.44] And so I very much wanted to solve it. |
[1383.54 --> 1385.40] And I clearly have to get rid of it. |
[1385.64 --> 1387.14] And I think I have a plan. |
[1387.28 --> 1389.20] I'm still waiting to put all the pieces together. |
[1389.34 --> 1395.64] But I feel like in the next month or two, I'm probably going to build or buy a new server and go through this whole process. |
[1395.64 --> 1400.54] And then I got to ask myself, like, do I want to put Arch back on there? |
[1400.66 --> 1402.88] Do I want to do Proxmox like you're doing? |
[1403.70 --> 1406.82] Do I want to put WireGuard on a separate machine? |
[1406.82 --> 1410.12] So that way, when my server goes down, I can still get into the network. |
[1410.48 --> 1411.88] A lot of things to think about. |
[1411.96 --> 1413.26] So I'm just starting that process. |
[1413.84 --> 1414.58] What went wrong with it? |
[1414.94 --> 1416.82] There was a power outage at the studio. |
[1417.16 --> 1418.38] So there's two power supplies. |
[1419.10 --> 1422.50] And one is plugged into a UPS and one is plugged into the wall. |
[1422.56 --> 1425.58] And there's a funky old tech debt reason why. |
[1426.28 --> 1432.46] And I think when the power went out, it got in some sort of funky state where one power supply was down, but the other one stayed on for a while. |
[1432.46 --> 1435.82] But then eventually the UPS ran out of power and it shut off. |
[1436.50 --> 1437.80] Or maybe it didn't shut off. |
[1437.92 --> 1439.52] I'm not exactly sure because I wasn't here. |
[1439.52 --> 1442.52] But when I got back, it was frozen. |
[1442.76 --> 1451.14] The system was locked up and it was just a constant beep, an air message, just a solid air message, like a hardware air. |
[1451.46 --> 1453.36] And there was a red light on the front of the chassis. |
[1453.48 --> 1454.18] It's a super micro. |
[1454.92 --> 1457.12] And when I turned it off, the beep persisted. |
[1457.24 --> 1462.92] So I actually physically unplugged the power supplies and then I plugged them back in and then booted it back up. |
[1463.56 --> 1464.48] And it's been fine. |
[1464.48 --> 1466.52] And I just think it's dying, slow death. |
[1466.72 --> 1472.62] And so it has been unreliable for about five to almost six months now. |
[1472.82 --> 1477.54] And so I think this is just part of a old server's slow death. |
[1478.28 --> 1484.10] You know, what's funny is we were talking to Matt last episode about high availability and redundancy and all that kind of thing. |
[1484.10 --> 1490.44] And it's interesting, you know, you have dual power supplies in there, presumably for that exact reason. |
[1490.44 --> 1492.56] And yet you suspect that might be the issue. |
[1492.88 --> 1493.38] Who knows? |
[1493.78 --> 1500.32] We don't really have like great like intel or information from the system logs because everything that was happening was external to the box. |
[1500.32 --> 1504.12] But yeah, that's going to be a project for sure. |
[1504.48 --> 1505.88] And so you mentioned WireGuard. |
[1506.12 --> 1510.32] I'm going to walk you through what I've been doing in a minute with WireGuard and TailScale. |
[1510.52 --> 1513.00] But before I do, what are you planning on doing? |
[1513.14 --> 1516.56] Or suppose I should ask, what do you do for a firewall at the studio now? |
[1516.56 --> 1519.30] We have a Comcast business router that's the firewall. |
[1519.50 --> 1520.18] It's nothing special. |
[1520.60 --> 1526.06] I have thought in the past about replacing it with like a PFSense box or something like that. |
[1526.06 --> 1530.94] However, as time has gone on, I've really found it fairly acceptable. |
[1531.66 --> 1533.00] So I haven't replaced it yet. |
[1533.50 --> 1539.30] You know, the only thing I would say is go ahead and do OpenSense or PFSense for a little bit. |
[1540.06 --> 1549.96] There is a community plugins repository maintained by the same guy, I think, that writes the WireGuard plugin for OpenSense that lets you put AdGuard home directly on the firewall as well. |
[1550.54 --> 1551.88] So that's what I've been doing for the last few weeks. |
[1551.88 --> 1556.96] So I've been running AdGuard home on the same box as OpenSense as the primary DNS server. |
[1557.06 --> 1562.66] So I've disabled Unbound on OpenSense and I'm now just using AdGuard home and it works fine for me. |
[1563.04 --> 1572.72] But the real advantage, the real advantage is I've got my DNS, my DHCP and my VPN endpoints all on the same box. |
[1572.82 --> 1579.66] Now, I suppose you could argue it's a very large single point of failure, but it's actually incredibly convenient. |
[1579.66 --> 1581.88] Oh, for sure. And you don't need 100 boxes. |
[1582.32 --> 1586.10] I'm a little done running a separate Raspberry Pi that has Pi Hole. |
[1586.20 --> 1587.54] I love it. I think Pi Hole is great. |
[1587.66 --> 1589.70] I actually like it a little better than AdGuard myself. |
[1590.26 --> 1598.66] However, it's drawing power and I just don't need three Raspberry Pis running 24-7 when I'm running off a battery. |
[1599.16 --> 1601.66] And I would much prefer to consolidate that down here. |
[1601.72 --> 1604.84] Now, at the studio, power is not as much of a consideration. |
[1605.38 --> 1608.16] It's then just more about functionality and flexibility. |
[1608.56 --> 1609.40] Stability, surely. |
[1609.40 --> 1611.40] And stability, and stability for sure. |
[1611.54 --> 1615.12] I have been thinking about moving WireGuard off on its own device. |
[1615.70 --> 1623.64] And if I did do an OpenSense box, and it'd be pretty nice to have AdGuard on there too, and then also do WireGuard, I'd be checking a few boxes. |
[1624.16 --> 1625.54] So I think I may consider it. |
[1625.92 --> 1629.14] I was actually originally planning to set up a Raspberry Pi. |
[1629.70 --> 1636.38] And I was even thinking of trying to come up with some sort of failover capability for the Raspberry Pis to do WireGuard, which I think would be particularly tricky. |
[1636.38 --> 1637.10] All right. |
[1637.14 --> 1640.28] Well, here's another idea for you to bounce around your noodle. |
[1640.28 --> 1643.78] I've been looking at something called TailScale for the last few weeks. |
[1643.88 --> 1650.50] Now, this is born out of a requirement to run on a Synology box, which, as I'm sure you know, are quite restrictive. |
[1650.84 --> 1655.66] And they're not full Linux, but they're sort of kind of Linux, and they sort of kind of do some things. |
[1655.66 --> 1661.98] And anyway, it's a bit of a mess, to be honest, as a Linux guy to try and come and make this system do what I want. |
[1663.08 --> 1670.98] They run Docker, so I can run, you know, Minio to do autorestick backups, all that kind of stuff to Synology remotely. |
[1671.30 --> 1675.48] But that's no good if I can't connect to the damn thing over some kind of a secure tunnel. |
[1675.48 --> 1683.44] So I've been taking a look at something called TailScale, and this project is absolutely awesome. |
[1684.44 --> 1689.56] It has clients for Mac, Windows, Android, iOS, Linux, you name it. |
[1690.14 --> 1701.48] And this thing, I got further in about 10 minutes connecting up all of my different devices and servers than I had in, I don't know, a year plus of trying to futz around with WireGuard configs. |
[1701.48 --> 1708.66] And this thing lets you advertise different routes and different subnets, just with one simple command on the command line. |
[1709.10 --> 1716.06] So, for example, I'm sat in Raleigh, and I want to connect to a host that's in my dad's network in England. |
[1716.88 --> 1723.28] I don't have a direct connection from my laptop to that host, but what I can do is I can bounce the traffic through my UK server, |
[1723.56 --> 1727.94] which routes through the TailScale network using something they call Magic DNS. |
[1727.94 --> 1730.18] And then it pops out the other side. |
[1730.48 --> 1737.78] The remote server then goes, oh, yeah, you've allowed access to 192.168.whatever the subnet is in that LAN. |
[1738.56 --> 1745.18] And it lets the traffic out from my local laptop to the device on the network in the remote side. |
[1745.40 --> 1749.20] I can also then advertise what's called an exit node. |
[1749.20 --> 1755.28] If I want to route my traffic over the internet to come out in England rather than the US, for example, for iPlayer, |
[1756.30 --> 1760.62] I can just, with a click of one button in the TailScale client on my laptop, |
[1761.04 --> 1763.62] change between the different endpoints that I'm exiting at. |
[1764.20 --> 1767.04] It's really, really simple and really slick. |
[1767.12 --> 1767.80] You should give it a look. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.