text stringlengths 9 408 |
|---|
[1987.24 --> 1988.36] And that's where VLANs come in. |
[1988.66 --> 1989.96] And that's the number one thing I do. |
[1990.58 --> 1993.64] My Wyze cameras, they're on separate VLAN and SSID. |
[1994.88 --> 2000.96] My EcoVac Smart Vacuum on its own SSID and its own VLAN. |
[2001.36 --> 2007.32] Because I want to segment anything on my network that is going to potentially open me up to attack. |
[2008.08 --> 2012.16] The other reason why I use VLANs is, again, as I mentioned, I have a home lab. |
[2012.64 --> 2013.94] I have all these services running. |
[2014.36 --> 2017.16] Sometimes I have multiple THCP that I'm testing, etc. |
[2017.56 --> 2020.42] I don't want that to conflict with my home network. |
[2020.96 --> 2022.24] So that's where VLANs come in. |
[2022.92 --> 2024.42] I use VLANs for DMZ. |
[2024.62 --> 2027.20] Things that I want to expose outside my network. |
[2027.90 --> 2029.04] VLANs are really about segmentation. |
[2030.74 --> 2034.12] Take what you need that needs to talk to each other and put it on its own VLAN. |
[2034.12 --> 2036.70] And that's the way that you should think about it. |
[2037.34 --> 2041.76] Somehow I've managed to avoid the temptation of VLANs this whole time. |
[2041.76 --> 2045.00] Because it requires a bit of extra hardware or a bit more advanced hardware. |
[2045.14 --> 2047.90] So you've got to have a couple of switches that support VLANs. |
[2048.18 --> 2053.74] And something to configure them at the router level as well. |
[2054.14 --> 2055.76] So it's not just a plug and play thing. |
[2055.80 --> 2057.80] You've got to have a bit more about you to do it. |
[2057.80 --> 2062.82] And I've just kind of swept that one under the carpet and just opened up a bigger subnet |
[2062.82 --> 2066.30] and put things in different subnets and just kind of prayed and hoped for the best, really. |
[2067.02 --> 2068.02] That's been my approach. |
[2069.02 --> 2075.04] I'm sure that most people who are running home labs, you know, they have Ubiquity, Microtech. |
[2075.76 --> 2078.20] You know, a lot of the equipment that we already have can do it. |
[2078.66 --> 2079.26] That's a good point. |
[2079.68 --> 2085.08] I think the biggest issue is that people look at VLANs and they're a little hesitant |
[2085.08 --> 2087.20] because they're afraid of what it can do. |
[2087.84 --> 2092.62] I can definitely tell you I've gotten VLANs wrong and I've made a mess of things. |
[2093.14 --> 2094.46] But that's what a home lab is for. |
[2094.88 --> 2095.62] Break some eggs, eh? |
[2096.70 --> 2097.14] All right. |
[2097.16 --> 2099.18] Well, thank you very much for joining us this week, Morgan. |
[2099.32 --> 2102.38] It was a very, very last minute that we had to call upon you. |
[2102.80 --> 2106.12] Because we generally record the night before the show goes out on the Friday morning. |
[2106.12 --> 2109.50] So we didn't have much time after Chris's laptop got flooded. |
[2110.22 --> 2114.84] And also a big thank you to our members over at selfhosted.show.sre. |
[2115.08 --> 2116.74] You can go over there and support the show. |
[2116.88 --> 2121.72] And obviously we do appreciate that because it goes straight into the JB coffers to support |
[2121.72 --> 2122.62] the network directly. |
[2122.62 --> 2125.14] So we don't have to have as many sponsors on the shows. |
[2125.80 --> 2127.92] Speaking of which, we have to thank A Cloud Guru. |
[2128.18 --> 2130.56] And you can find them just about anywhere on social media. |
[2130.72 --> 2135.64] They are slash A Cloud Guru on Facebook, YouTube, Twitter, just about everywhere. |
[2136.64 --> 2140.72] So for all the different ways to go and get in touch with us, you can go to selfhosted.show |
[2140.72 --> 2143.20] slash contact is the place to go to get in touch with us. |
[2143.20 --> 2145.42] And you can find me on Twitter at ironicbadger. |
[2146.10 --> 2148.94] And I don't have social media because I don't want to be cancelled. |
[2152.14 --> 2156.04] Oh, well, I know you troll people on Reddit on a regular basis, but you can also find the |
[2156.04 --> 2157.60] show at selfhosted.show. |
[2158.00 --> 2159.10] Thanks for listening, everybody. |
[2159.10 --> 2161.74] That was selfhosted.show slash 48. |
• Chris Fisher's laptop gets wet while driving |
• Water damages electronics and floods the RV |
• Cause of flood: laptop fell into sink, turned on faucet, and soaked basket of electronics |
• Damage to devices and RV |
• Chris spends 2 hours drying up the water damage |
• MacBook survives the incident despite being exposed to water |
• The host has a phone with a low battery and can't use it in water |
• Discusses feeling frustrated with devices having non-removable batteries |
• Introduces Orthalia, an open-source single sign-on service for managing multiple logins |
• Describes how Orthalia uses rules to determine which services to authenticate for |
• Explains that Orthalia supports two-factor authentication and can add 2FA to services without native support |
• Mentions the benefits of using a service like Orthalia for streamlined login management |
• Discusses the trade-offs between self-hosting and commercial services, with the host sharing his personal frustration with technical issues |
• Touches on the idea that there may be a balance between self-hosting and using commercial services. |
• Docker Hub tagging and updating Nextcloud major versions |
• Resolving a Nextcloud issue due to character encoding problems |
• Troubleshooting with container logs and MySQL command line |
• Deleting data types and tables in MySQL database |
• Upgrading to Nextcloud 22 and resolving issues |
• Backing up data after experiencing multiple hardware and software failures |
• Appreciating the value of cloud providers and their ability to mine user information |
• The importance of having control over digital services and data |
• The trade-off between using cloud services and self-hosting solutions |
• Benefits of hosting own wiki and other information in-house for proprietary purposes |
• Desire to feel a sense of control and confidence when managing personal projects |
• Growing market demand for self-hosted services and increased competition among companies offering this solution |
• Using manual window fans with smart plugs to automate temperature control |
• Discussion of rebuilding infrastructure and using Linode for cloud hosting |
• Linode's features and benefits, including automatic backup service and one-click deployment options |
• Use case example: Milwaukee Linux users group migrating from Zoom to Jitsi on Linode |
• Announcements about upcoming meetups in Denver and Salt Lake City |
• Introduction of a live tracker in the host's RV for meetup attendees |
• Own Tracks API integration with Home Assistant for real-time location tracking |
• Using MQTT for communication between devices and systems |
• Deprecation of commands in ValiTudo robot vacuum firmware update |
• Concerns about system updates and potential disruptions to infrastructure |
• Virtualization as a solution for safety net and backup capabilities |
• Hypervisors and containerization options (e.g. Proxmox) |
• New versions of ZFS (2.04), QEMU (6), and kernel (5.11) in Proxmox |
• Proxmox pushing updates to core systems, addressing Debian's reputation for being "old and crusty" |
• Recent ButterFS support and near-parity with ZFS in Proxmox |
• Importance of taking ButterFS seriously due to its adoption by large companies like Facebook |
• Combination of ButterFS and ZFS in Proxmox for reliable home servers |
• New feature in Proxmox 7: downloading ISOs from the web UI, including automatic verification via MD5 hash |
• Proxmox is open-source and free as in cost (both "free" and "beer") |
• Topics on Ansible exam and managing inventory |
• Nvidia Shield's recent update with ads at top of screen |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.