text stringlengths 9 408 |
|---|
• The discussion of termpad.com mentions it as a hosted version of the software, with options for self-hosting and database-free operation |
• TinyPin is discussed as an alternative to Pinterest, providing a minimalistic image collection board that can be self-hosted in a container |
• OpenSense stores data in a data directory and has a simple setup process |
• OpenSense 21.1 (Marvelous Meerkat) was released, featuring new firewall rules and improved traffic graphs |
• Comparison to pfSense's addition of WireGuard support |
• Discussion of the speaker's frustration with getting WireGuard working on OpenSense |
• Consideration of switching from OpenSense to ViOS or other alternatives due to the difficulty with WireGuard |
• Discussion of WireGuard and its use with Linux servers |
• Introduction to the Linux server WireGuard container, which simplifies setup and configuration |
• Demonstration of using Docker Compose with the WireGuard container |
• Mention of John Muchovesch's blog post on routing specific containers through the WireGuard container |
• Promotion of Linode as a cloud hosting provider, offering fast network connections and competitive pricing compared to AWS and Google |
• The host discusses the benefits of using Linode as an independent cloud provider |
• Accusations are made that the show is similar to the Raspberry Pi and RV Home Assistant podcast |
• The host shares their experience with running Home Assistant on a Raspberry Pi 4 |
• They discuss the limitations of using a USB-to-SATA converter for storage |
• A previous setup involving Intel GVT-G pass-through and virtual GPUs did not work out as expected, resulting in kernel panics and hung processes |
• Discussion of running Plex on a server with QuickSync |
• Using Proxmox to run Docker containers and LXCs, but not managing them directly due to limitations |
• Preference for minimizing host reboots by keeping the host clean and using VMs |
• Alternative setup options, including installing Docker directly on the host or considering different hardware configurations |
• Use of Intel GVTG technology in a previous server configuration that proved unreliable |
• Plans to repurpose an HP290 as a Windows box with Pi KVM for server use |
• Discussion of a Homelab setup using Dual Xeons and 128GB RAM, but considering underutilization for specific tasks |
• Potential use of smaller hardware, such as Raspberry Pis, for certain tasks and the trade-offs between performance and cost |
• Discussion around scaling down Pis and scaling up Pi usage |
• Comparison between Raspberry Pi and Odroid devices, with the speaker preferring x86 boxes for home hosting due to compatibility and flexibility |
• Challenges of using ARM devices in production, including limitations and edge cases |
• Importance of implementation and ecosystem in determining a device's effectiveness |
• Advertisement for A Cloud Guru's Linux networking and troubleshooting course |
• Discussion around backing up Home Assistant through a Google Drive plugin |
• Google Drive backup add-on for Home Assistant |
• Automatic snapshot management and configuration options |
• Integration with Duplicati for system-level backups |
• Comparison of using Git to manage config files vs. existing setup |
• Discussion of the cost and complexity of rewriting code versus incremental changes |
• The concept of "if it ain't broke, don't fix it" and its application in software development |
• Technical debt as an investment vs. a necessary evil |
• The importance of learning from past mistakes and building on existing code |
• The potential need to restart or reboot projects due to complexity and scope creep |
• Self-hosting projects and the trade-offs between feature set, complexity, and deployment ease |
[0.00 --> 3.98] Coming up on the show today, Alex shocks me with his latest project. Seriously. |
[4.24 --> 8.52] Then he lays down some quick fire picks. So get your notepad ready. |
[8.78 --> 13.54] And then we'll discuss what's going on with OpenSense's WireGuard setup. I'm Chris. |
[13.84 --> 19.86] I'm Alex. And this is self-hosted. No, wait, the RV and Home Assistant podcast, episode 38. |
[21.14 --> 24.84] Thought I'd open today's show with a quick shout out to the self-hosted subreddit. |
[24.94 --> 28.58] We had some love from you guys this week. Hello. Hello. Hi, if you're listening. |
[28.58 --> 30.20] Hey there. How's it going? |
[30.48 --> 34.40] It was pretty cool. Like someone tagged me in one of the threads who is on our Discord. |
[34.68 --> 38.12] And I don't know, it's just cool to see community come together like that. |
[38.22 --> 45.10] And we aren't like an official partner with the subreddit or anything, but I reached out to one of the mods or, well, they reached out to me. |
[45.12 --> 49.98] And we had a chat about a few things. We might have them on one of the shows in future. |
[50.02 --> 54.36] And it's sort of got my mind thinking about how we can involve the community a bit more. |
[54.36 --> 65.78] And, you know, getting random people on to talk about their setups and sort of figure out what containers people are running, how much storage they actually have, what the hardware underneath is. |
[65.88 --> 71.86] You know, maybe we could have a little 10, 15 minute segment every now and again with community members, like a community spotlight section. |
[72.28 --> 78.72] And you know what will end up happening is we'll get all these ideas from each other and we'll then all go off and build projects and get excited to do different stuff. |
[78.88 --> 79.38] That'd be awesome. |
[79.38 --> 82.48] People often accuse me of making them spend money. Well, it's not my fault. |
[84.32 --> 85.98] I can attest to that, actually. |
[88.06 --> 89.94] Yeah, I feel like that has definitely been the case. |
[90.04 --> 94.18] I mean, the thing is, is I love just getting ideas from the community in general. |
[94.28 --> 98.38] We get people that email into the show, but like you were saying, also over on Reddit, there's some great ideas. |
[98.50 --> 102.16] And our Discord, that's another spot where I see people kicking around stuff. |
[102.16 --> 109.34] And often either, either tried something and it, and then tell us about it or are thinking about trying something and want our advice. |
[109.42 --> 111.00] That kind of stuff goes down in there all the time as well. |
[111.44 --> 114.70] My favorite stuff to read about is, well, there's two things. |
[114.84 --> 116.52] One is the stuff that works really well. |
[116.52 --> 128.56] But the other thing is things, you know, all the stuff that people try and then abandon, for whatever reason, that's more often more interesting because that's what takes the time. |
[128.76 --> 132.26] That's what eats my time is trying stuff and failing and trying stuff and failing. |
[132.42 --> 136.30] And if I can community crowdsource that stuff, I'm in. |
[136.30 --> 136.74] Absolutely. |
[138.02 --> 139.76] There's always many ways to learn. |
[139.88 --> 144.90] Like our friends over at A Cloud Guru, they are the leader in learning for the cloud, Linux, and other modern tech skills. |
[145.36 --> 148.12] They have hundreds of courses, thousands of hands-on labs. |
[148.24 --> 151.94] You can get certified, you can get hired, you can get learning at acloudguru.com. |
[152.56 --> 156.94] Now, I've been doing a lot of travel the last few weeks back and forth to the hospital. |
[157.68 --> 160.36] And I've been needing to use a lot of hotspot data. |
[160.36 --> 162.94] And I came across, this was on Hack 5, I think, actually. |
[162.94 --> 177.22] Yeah, I came across just a really interesting little hack, little tip for anybody looking to do, you know, phone tethering and try and bypass the limits that people have that Verizon or AT&T and people like that set. |
[177.38 --> 178.20] Now you got my attention. |
[178.48 --> 181.26] Yeah, I'm sure I do, given that your house is on wheels. |
[181.74 --> 185.68] So the thing you can do is set something called a TTL, time to live parameter. |
[186.00 --> 192.22] And this is apparently how the phone providers recognize whether you're on a laptop or a phone. |
[192.22 --> 195.28] That seems too easy, too good to be true. |
[195.34 --> 206.00] But I can confirm, having been streaming Netflix over 4G, 5G for the last month, that I went from it being unwatchable to being usable. |
[206.26 --> 207.08] So it does work. |
[207.14 --> 209.16] And there's a link in the show notes to a Reddit thread about this. |
[209.50 --> 210.18] This is fantastic. |
[210.84 --> 213.68] I absolutely have struggled with this. |
[214.26 --> 215.90] I've experimented with this myself. |
[215.90 --> 222.32] So by checking the TTL of the IP packets, they seem to be able to suss out the type of device that it is. |
[222.78 --> 227.20] But you can tweak that yourself, which is what this guide walks you through. |
[227.86 --> 228.96] And there's other ways, too. |
[229.50 --> 239.16] I have found WireGuard to be an extremely successful way to get around carrier bandwidth shaping, which is really what's happening here is they're looking at your IP traffic, right? |
[239.16 --> 243.50] And they can say, okay, well, you're going to YouTube on port 443 or whatever it is. |
[243.52 --> 246.10] They can actually look at the traffic because it's all running over their gear. |
[246.76 --> 248.74] They have complete access to your traffic. |
[248.74 --> 257.60] And they have systems in place that will automatically force, and in some cases, in a really brute sort of lowbrow way. |
[258.02 --> 270.66] One of the ways AT&T will do this is they will just make YouTube smack up against a wall and try all of the different bit rates until YouTube, the servers, finally select a low enough bit rate. |
[270.84 --> 274.20] And then AT&T will allow the YouTube traffic to pass. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.