text stringlengths 7 369 |
|---|
[2785.98 --> 2789.06] He'd like to hear your take on Pihole or AdGuard. |
[2789.06 --> 2793.66] He'd like to also hear about your three different locations you're using it because he's been |
[2793.66 --> 2798.46] looking at Pihole synced up using Gravity Sync over tail scale or something like that. |
[2798.82 --> 2801.30] And he thinks he can get some redundancy with this setup. |
[2801.94 --> 2807.38] And I think he's just, I personally think he's trying to be convinced to look at AdGuard. |
[2807.38 --> 2812.56] So I read this, each Pihole synced up, like you said, using Gravity. |
[2814.40 --> 2814.88] Why? |
[2815.56 --> 2818.02] I don't know what benefit that adds. |
[2818.14 --> 2820.34] I mean, I'll just say this. |
[2820.40 --> 2828.00] Like I set up the AdGuard home instance on my firewall on OpenSense here two, three years |
[2828.00 --> 2832.38] ago, and the lists automatically update and the version automatically updates. |
[2832.56 --> 2835.70] And that really is the last bit of thought I gave to it. |
[2835.70 --> 2838.36] These lists update remotely. |
[2838.90 --> 2842.32] They are, you know, published by third parties. |
[2842.50 --> 2844.16] I'm not really involved in that process. |
[2844.32 --> 2849.36] I mean, I suppose there is some kind of a security risk potentially with people spoofing |
[2849.36 --> 2852.12] DNS entries that way or what have you. |
[2852.22 --> 2855.46] But yeah, I suppose that's the risk you take, isn't it? |
[2856.22 --> 2861.82] So I would just say I don't really worry about syncing my DNS between three sites. |
[2861.82 --> 2864.54] And I certainly don't worry about redundancy of DNS locally. |
[2864.54 --> 2868.20] Because, you know, the setup's pretty simple. |
[2868.38 --> 2872.02] Like if the firewall is out, then the internet is out. |
[2872.52 --> 2874.58] And obviously my DNS with it. |
[2874.76 --> 2880.28] So if the DNS service crashes, then I'm going to notice that pretty quickly. |
[2880.28 --> 2882.52] And I can just go in and fix that if I need to. |
[2882.52 --> 2890.46] But again, if DNS locally is down, unless I've got some kind of IP only route to my other |
[2890.46 --> 2893.64] sites, then it's always DNS. |
[2894.14 --> 2897.62] So it's, you know, it's a bit of a chicken and egg problem. |
[2897.62 --> 2903.12] And I just like to keep things simple as possible, really, just by having everything local to |
[2903.12 --> 2903.68] each site. |
[2903.68 --> 2908.08] And then that way, if something goes down on that site, it's compartmentalized. |
[2908.24 --> 2909.56] The failure is compartmentalized. |
[2909.64 --> 2914.14] The blast radius is reduced to just my house or just my mom's house or whatever. |
[2914.32 --> 2916.38] And there's the performance element of it, too, really. |
[2917.00 --> 2924.06] You know, that's probably one of the top three reasons I run a DNS server on my LAN is I don't |
[2924.06 --> 2926.42] want to send my DNS requests all the way out to my ISP. |
[2926.42 --> 2928.50] That's that's tens of milliseconds. |
[2929.50 --> 2930.14] What's that? |
[2930.42 --> 2934.24] And honestly, the same argument applies to like Kubernetes and all that kind of stuff. |
[2934.34 --> 2941.18] Like, yes, I could run the wiki in my house on a Kubernetes cluster and have it highly available |
[2941.18 --> 2945.94] and redundant and have a pie on different UPSs at different ends of the house and stuff |
[2945.94 --> 2946.38] like that. |
[2946.48 --> 2949.38] But that's a lot of work in it. |
[2949.42 --> 2949.98] Let's be fair. |
[2950.10 --> 2950.72] Let's be honest. |
[2951.32 --> 2951.94] A little too far. |
[2952.24 --> 2952.82] Yeah, maybe. |
[2953.54 --> 2953.74] Yeah. |
[2953.74 --> 2953.86] Yeah. |
[2953.86 --> 2954.18] Yeah. |
[2954.58 --> 2960.38] I asked last week just to get people's general kind of temperature on OpenSense versus BF |
[2960.38 --> 2966.22] Sense and 412 Linux with 1010 sats boosted in said, hi, gents, regarding OpenSense. |
[2966.70 --> 2971.78] I've been running OpenSense on a Protect CTLI vault. |
[2972.64 --> 2973.80] Not familiar with that. |
[2974.14 --> 2974.58] Protectly. |
[2975.32 --> 2975.58] OK. |
[2976.04 --> 2980.34] You've been doing it for about two years, completed about a dozen minor upgrades, maybe |
[2980.34 --> 2983.78] two major upgrades, and each has proceeded without interest. |
[2983.98 --> 2984.34] Issue. |
[2984.64 --> 2990.14] I just completed the upgrade to 22.7, added AdGuard, and I've been very happy with the |
[2990.14 --> 2991.44] quality of the release. |
[2992.92 --> 2993.56] All right. |
[2994.04 --> 2994.80] All right. |
[2994.98 --> 2998.62] I'm going to have to start a campaign with Wes Payne, though, because he was very set |
[2998.62 --> 3002.94] on building a bare-bones Linux box for the studio to do the firewall. |
[3002.94 --> 3008.46] Well, this is pretty interesting, actually, because just this week I switched the subnet |
[3008.46 --> 3020.56] of my local house from 192.168.16 something to 10.something subnet because my remote family members, |
[3020.56 --> 3028.56] as I talked about in the last episode, have Starlink, have Sky routers, you know, BT all |
[3028.56 --> 3029.04] in the UK. |
[3029.54 --> 3036.04] And a lot of these routers don't give you the option to customize even the DHCP range. |
[3036.72 --> 3042.02] And so a lot of them pick 192.168.0 or 168.1. |
[3042.02 --> 3047.24] And I actually had that in my local range here because I thought, oh, well, arrogantly, like, |
[3047.50 --> 3051.22] I'm going to be able to take control of all these remote networks and change them to .16 |
[3051.22 --> 3054.60] or whatever, you know, to get around that. |
[3054.66 --> 3058.90] And it turned out, actually, that more often than not, when I'm remote, I don't have control |
[3058.90 --> 3059.66] over the network. |
[3059.66 --> 3064.52] And I have to deal with being on a subnet that overlaps with my local subnet here. |
[3065.42 --> 3074.16] And so by switching my subnet here to a different, totally different CIDR, I've been able to, |
[3074.52 --> 3079.10] I hope, I'll test this out over the next year or two, I guess, circumvent that issue. |
[3079.34 --> 3081.00] Now I'm using Tailscale everywhere. |
[3081.68 --> 3085.10] Otherwise, Tailscale just goes, well, there's two subnets here that are the same. |
[3085.16 --> 3086.60] I have no idea what to do with this traffic. |
[3086.60 --> 3087.54] So I'll just do nothing. |
[3087.86 --> 3089.06] I'll just do nothing with it. |
[3089.76 --> 3094.98] So coming to your point about OpenSense, the reason I mention it is because I was actually |
[3094.98 --> 3098.96] considering trying out something other than OpenSense. |
[3099.38 --> 3104.76] So maybe via OS, if you have any experience with that, I'd be really curious to hear that |
[3104.76 --> 3114.34] in the chat or via the contact forms or just creating a bog standard Linux VM with IP tables |
[3114.34 --> 3120.20] or whatever and just create the firewall rules that way myself because I'm getting a bit |
[3120.20 --> 3120.78] tired. |
[3121.62 --> 3125.48] It's only a small annoyance, but it's all the DHCP requests, right? |
[3125.52 --> 3130.06] The static leases that I've had to configure this week of clicking through the UI and not |
[3130.06 --> 3135.64] having things in an ansibilized, you know, infrastructure as code fashion. |
[3135.64 --> 3140.18] I would like to be able to just apply my config, have DNS mask and all that just taken care |
[3140.18 --> 3143.02] of and never think about it ever again. |
[3143.56 --> 3147.06] I'm so glad you touched on this because this was going to be where I go with this is it |
[3147.06 --> 3152.40] does seem like the kind of approach Wes wanted to go with would be better from an ansible |
[3152.40 --> 3153.32] management standpoint. |
[3153.88 --> 3154.06] Wow. |
[3154.14 --> 3155.80] You just dropped a lot on me. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.