WEBVTT 00:00:03.000 --> 00:00:04.000 bookend. 00:00:04.000 --> 00:00:19.000 Okay, this is the bookend for the recording. This is Wednesday the 13th of May, 2026. This is the monthly general meeting of SLUB, the St. Louis Unix users group our speak. 00:00:19.000 --> 00:00:36.000 main talk tonight is done by Lee Lamert, and he's going to talk to us about Pi-hole and how that's going to take care of those annoying ants. Our base presentation or tutorial presentation, Grant was going to be doing that for us. 00:00:36.000 --> 00:00:46.000 Uh, sounded like an interesting topic, but Grant has been detained at work on an emergency at work, and so he won't be here for the tutorial. 00:00:46.000 --> 00:00:51.000 So, at this point, we'll just be wigging it for a while. 00:00:51.000 --> 00:00:53.000 Who are we? 00:00:53.000 --> 00:01:03.000 About us, uh, we're the St. Louis Unix Us group. We're actually incorporated. We did that a few years ago, because the previous 2, 2 and a half. 00:01:03.000 --> 00:01:26.000 versions of the Unix user group went away, as so many user groups do because they didn't have any permanent structure, so… Uh, you can read the details there on the slides. By the way, you can also find this entire slide deck online. It's at slug.org slash. 00:01:26.000 --> 00:01:27.000 I don't know. There's a link on the page. That's all I remember. 00:01:27.000 --> 00:01:29.000 The meeting agenda? 00:01:29.000 --> 00:01:44.000 Link on the home page. So alrighty. The meeting order is here in this agenda, and what we usually do is open the meeting at 6, electronically open it, as they say. 00:01:44.000 --> 00:02:01.000 the base tutorial usually starts at 6.30, as I say, our speaker tonight has been unavoidably detained by work. Around 7 o'clock. We usually break to do announcements, introductions, that kind of thing. And then about 715. 00:02:01.000 --> 00:02:07.000 We get into our main topic. 00:02:07.000 --> 00:02:08.000 base topic. I'm sorry. Go ahead, stay ahead. 00:02:08.000 --> 00:02:14.000 Just show you. to show you remember what it is. A base topic is going to be… 00:02:14.000 --> 00:02:29.000 Uh, it's going to be of something. Simple that we can talk about in like a 15, maybe 30 minute time frame. Probably like a tutorial level, um. 00:02:29.000 --> 00:02:34.000 But just focus on one little thing that we can get out that fast. 00:02:34.000 --> 00:02:48.000 The middle, that's where we're going to do the, as I say, the introductions. If we have time, kind of a brief start Q&A. Um, and uh… And that's the gooey center of our meeting. 00:02:48.000 --> 00:02:58.000 Next. introductions already. Okay, introductions. Did we skip the slide? 00:02:58.000 --> 00:03:04.000 Why? Nobody knows who you are. If they're new. 00:03:04.000 --> 00:03:05.000 You say, I am, and you state your name. 00:03:05.000 --> 00:03:23.000 Okay, good. Okay. Yeah, I am Gary Meyer, and I'm MCing the meeting, also the president of the organization. I thought we skipped over slide 7, but I could be wrong. The other voice you hear there is Dan Reichert. He's our vice president, and he's also the man who gets. 00:03:23.000 --> 00:03:38.000 So much of the production work done amazingly at times. So a big thanks to Stan. Our treasurer is Lee Lamert. He'll also be our main speaker tonight. And he's also the one who's hosting the GIPSE meeting. 00:03:38.000 --> 00:04:00.000 I'm sorry, the Zooming. Uh, chat monitor. We usually ask for somebody to volunteer, just to keep an eye and read the chat things as they come up. And if somebody volunteers to do that, then, you know, if there's something important in chat that should be addressed right away. 00:04:00.000 --> 00:04:02.000 You know, you can get us to pause and answer something that's in chat. So anybody want to volunteer? 00:04:02.000 --> 00:04:10.000 And… 00:04:10.000 --> 00:04:16.000 or it's possible just to… point out something. It depends on what the speaker wants us to do. If there's something really significant in the chat, somebody, anybody is welcome to. 00:04:16.000 --> 00:04:22.000 Yeah. 00:04:22.000 --> 00:04:23.000 talk and… and… interrupt what's going on. 00:04:23.000 --> 00:04:31.000 Mm-hmm. Okay. 00:04:31.000 --> 00:04:32.000 and that's… 00:04:32.000 --> 00:04:39.000 We always need volunteers to speak, so… Topic Wrangler is something anybody can find other speakers and topics and. 00:04:39.000 --> 00:04:47.000 you know, we got a lot of suggested topics, but hardly anybody to volunteer to do the actual presentation. 00:04:47.000 --> 00:05:04.000 That's the old story of, you know, many, many hands make the work light. So if a few more people want to volunteer to help find some speakers, suggest some topics, it would be very much welcome. Also, public relations. Pr sending out the announcements. It it's. 00:05:04.000 --> 00:05:22.000 It's something you can almost do by rote, but it's something that, yeah, it takes a little bit of time. So it'd be nice if somebody wanted to volunteer to help out doing that and relieve some of the people who are. 00:05:22.000 --> 00:05:23.000 Jerry, it's Jonathan. 00:05:23.000 --> 00:05:25.000 doing the finding of the speakers. So. Yeah, Jonathan. 00:05:25.000 --> 00:05:29.000 And for all the other members, I can renew my contracts from… 00:05:29.000 --> 00:05:33.000 The, um, semi-bug and see if I can… 00:05:33.000 --> 00:05:37.000 scar up some people. 00:05:37.000 --> 00:05:38.000 So, would you want to hear from, um… 00:05:38.000 --> 00:05:41.000 Oh, that'd be fantastic. Good. Thank you. 00:05:41.000 --> 00:05:43.000 A guy who did, um… 00:05:43.000 --> 00:05:50.000 Risk. 00:05:50.000 --> 00:05:51.000 Yeah. 00:05:51.000 --> 00:05:52.000 Risk hardware architecture. Sure. Yeah. For sure. 00:05:52.000 --> 00:05:53.000 Yes. 00:05:53.000 --> 00:05:55.000 Hmm, hmm. 00:05:55.000 --> 00:06:10.000 Cross-platform stuff is always interesting, especially if it's down the line, it can… Can talk to Unix-based or BSD or Linux or similar things. Cross-platform is good. 00:06:10.000 --> 00:06:11.000 Because we look at it from the angle of, uh, does it work with Unix? 00:06:11.000 --> 00:06:15.000 Yeah. Mm-hmm. 00:06:15.000 --> 00:06:16.000 Um, Stan and others, and Lee, and uh… 00:06:16.000 --> 00:06:17.000 or a Unix system? 00:06:17.000 --> 00:06:19.000 Alright, sure. 00:06:19.000 --> 00:06:23.000 I'm speak… I'm asking the leadership, and Gary, 00:06:23.000 --> 00:06:31.000 What do you think of me getting hold of, um, Deb Goodkin of the FreeBSD Foundation on FreeBSD progress? 00:06:31.000 --> 00:06:37.000 Also good. Yeah. She was a lady we had speak about, what, a year and a half ago? 00:06:37.000 --> 00:06:39.000 Oh, man, it's 2 years ago. 00:06:39.000 --> 00:06:46.000 2 years. Okay. But yeah, she she was a good speaker then, and I'm sure she could give us the latest and greatest information. Yeah. 00:06:46.000 --> 00:06:50.000 I'll get in touch with Stan about the available dates. 00:06:50.000 --> 00:06:51.000 And do you mind if I subscribe to SteerCom? 00:06:51.000 --> 00:06:52.000 Great. 00:06:52.000 --> 00:06:56.000 Next. 00:06:56.000 --> 00:06:57.000 Okay. 00:06:57.000 --> 00:07:07.000 Nope, please do. Although, be advised, we're in the middle of moving everything to mailman 3. So the web web interface may or may not be usable. 00:07:07.000 --> 00:07:16.000 Okay. If you have problems, Jonathan, just drop me a text message or an email and I'll I'll get it straightened out to get you on. 00:07:16.000 --> 00:07:20.000 Okay, let me raise the volume on this thing. 00:07:20.000 --> 00:07:25.000 It's a lot of making sausage, Jonathan. It really is. 00:07:25.000 --> 00:07:28.000 Well, I can find speakers. I mean… 00:07:28.000 --> 00:07:29.000 I still have content. 00:07:29.000 --> 00:07:40.000 Yeah. I mean, I mean the steer com mailing list is a lot of sausage at this point, as Lee mentioned, we're in the middle of transitioning. 00:07:40.000 --> 00:07:41.000 Okay. 00:07:41.000 --> 00:07:42.000 Gary, do you have any… 00:07:42.000 --> 00:07:43.000 Henry, do you have anything? 00:07:43.000 --> 00:08:03.000 Announcements. Let's see. Our next SLUE meeting. Well, that's today, June the 13th. But the next one will be a month from now on June, I'm sorry, May the 13th today. June the 10th will be the next one. And then in July the 8th will be the one after that. 00:08:03.000 --> 00:08:04.000 Does that generally work out to be the second Wednesday of the month? 00:08:04.000 --> 00:08:12.000 That's our general monthly meeting. 00:08:12.000 --> 00:08:13.000 Okay. 00:08:13.000 --> 00:08:34.000 It does amazingly. Imagine that. We generally only move it if there's a major holiday or something like that, so… The next St. Louis Linux user group. It's usually 8 days after the general meeting that usually makes it the third Thursday of the month. Sometimes 8 days will push off to the 4th, but as you can. 00:08:34.000 --> 00:08:45.000 Look at the calendar, you'll understand how that happens. But anyway, so May the 21st, that will be next week. In other words, 8 days from now, and uh. 00:08:45.000 --> 00:08:56.000 We don't have the topic. finalized for that yet, so stay tuned and keep an eye out. We'll let you know as soon as we get the topic finalized. 00:08:56.000 --> 00:09:11.000 new Linux. Oh, we've talked about possibly having a talk on Susa Linux leap 16. So that that's a possible topic. So stay tuned. 00:09:11.000 --> 00:09:22.000 The new Linux meeting is the 4th Tuesday of the month. Next one of those will be May the 26th. You can see the other dates there. The net Slack meeting is the first Thursday of each month. 00:09:22.000 --> 00:09:24.000 And important dates. Go ahead. 00:09:24.000 --> 00:09:41.000 Oh, yes. I'm sorry. I was I was present for part of the Slack meeting last week, and… I thought… I thought, uh, Slug and Slack were the same thing for a little bit. Sorry. 00:09:41.000 --> 00:09:42.000 Now, uh… 00:09:42.000 --> 00:09:48.000 So the the the slack and the new Linux meeting. Both of those. 00:09:48.000 --> 00:10:08.000 hardly ever have any sort of a… topic set out in advance. It's basically whoever comes to the meeting, the people there, ask questions, propose conversations, and that's the way that goes together. The first two meetings there, the Sloop general meeting, the St. Louis Linux. 00:10:08.000 --> 00:10:19.000 user group. Those 2 are usually have a set topic with a prepared speaker and it's just a difference in organization. 00:10:19.000 --> 00:10:23.000 But you're certainly welcome. Come to any of them. 00:10:23.000 --> 00:10:24.000 Thank you. 00:10:24.000 --> 00:10:36.000 Those dates in bold. The first one October the 14th. That was the end of life for Windows 10, Microsoft Windows 10. 00:10:36.000 --> 00:10:51.000 The next date on there, October the 13th of this year is the end of the extended end of life for Windows 10. Basically, you have to pay money to Microsoft if you want them to keep it running. 00:10:51.000 --> 00:10:59.000 So… The, uh… 00:10:59.000 --> 00:11:00.000 Go. 00:11:00.000 --> 00:11:18.000 That… let me talk about the Missouri Radiation Exposure Compensation Act. The reason we've got that posted on here is when we… had face-to-face meetings, a lot of people in the area had come, and some of them moved away or whatever. There's not a lot of publicity that's been done about it, but people have lived in certain areas of St. Louis County and certain areas of St. Charles County. 00:11:18.000 --> 00:11:30.000 Where in areas that were affected by the Manhattan Project from World War II, anybody that lived in certain areas since 1949. 00:11:30.000 --> 00:11:45.000 Uh, if they lived in a certain area for 24 months, they may be able to apply for compensation for advanced. 00:11:45.000 --> 00:11:55.000 And there's a list, you know, if you go to that website, you can go a Google search for Missouri Radiation Exposure Compensation Act, and it's got all kinds of material on that. 00:11:55.000 --> 00:12:05.000 Uh, we wanted to let people that attended a lot of our meetings in the past, and they may have moved away, need to know about that. 00:12:05.000 --> 00:12:07.000 Next. 00:12:07.000 --> 00:12:22.000 Okay. Let's see. We haven't got it up and going yet. But, as we said, this is a volunteer organization. There's no single corporate backer, you know, not any big company backing it like Susa or. 00:12:22.000 --> 00:12:38.000 or Red Hat. Actually, Lee here, his company, Omnitech, where he's the lead scientist, he, his company is providing the hardware that we keep our web server, our mail systems. 00:12:38.000 --> 00:12:54.000 And so a lot of donation of both time and computer services there. Ken Johnson is picking up the tab for our meetup account, and a number of other people have just made. 00:12:54.000 --> 00:13:09.000 you know, ongoing contributions into the kettle of money. So we are going to put a place on our website where if somebody does feel like they'd like to make a financial contribution. 00:13:09.000 --> 00:13:26.000 It would be welcome, but it's not up and running yet, but you can probably expect to see it in a few months. And no, this is not a backwards way of saying, we expect you people to pay. No, we expect you people to come. And hopefully there'll be a few people who can provide. 00:13:26.000 --> 00:13:33.000 provide a little financial help. Call for any other announcements. 00:13:33.000 --> 00:13:51.000 anything, as I said, unfortunately, our our main speaker tonight, or not our main, but our basic tutorial speaker tonight was called away at work. And so that's why we're not doing the tutorial right now. 00:13:51.000 --> 00:14:06.000 Bye bye Windows 10. I imagine most of you have already heard Windows 10 is officially no longer with us. I mean, obviously, it still runs if you got it on your machine. But it's not being updated by Microsoft, and. 00:14:06.000 --> 00:14:15.000 There are ways of having that done. If you pay Microsoft Corporation for additional support, but it's no longer. 00:14:15.000 --> 00:14:17.000 Move along, move along, move along. 00:14:17.000 --> 00:14:29.000 Okay. There's other. There's places on that slide that tell you where you can look up stuff about that. There's another thing end of life workshop. 00:14:29.000 --> 00:14:30.000 So it's there on that slide. 00:14:30.000 --> 00:14:49.000 There's an organization called EndOf10.org. They they are. Their goal is to… provide… introductions to other Linux sites to transition to away from Microsoft Windows. 00:14:49.000 --> 00:15:06.000 Any other announcements? Besides the fact that this meeting is being recorded, because we only record the Slug and the St. Louis Linux meetings for their presentations and put them in our archives. 00:15:06.000 --> 00:15:17.000 Uh, anybody here can be recording. So that slide right there gives you an introduction to a number of things that in October of 22 I did a. 00:15:17.000 --> 00:15:28.000 a presentation on simple screen recorder, and there's a… You know, there's it's upon our archives. 00:15:28.000 --> 00:15:38.000 As I said, we have archived stuff. I don't know, you can get to it from our website. 00:15:38.000 --> 00:15:39.000 Carol. 00:15:39.000 --> 00:15:49.000 Uh, we have a calendar. www.sloob. Yeah. And that goes to… Where is this magic thing? 00:15:49.000 --> 00:15:53.000 Can you say what this is about in 10 seconds or less, Gary? 00:15:53.000 --> 00:16:09.000 Yeah, we started this originally just to show where our meetings were what date and time. And you'll notice there's 4 or 5 of them that are red. Well, those are the meetings that are basically hosted by this organization. So those are our meetings. 00:16:09.000 --> 00:16:24.000 And we figured, well, as long as we've got a calendar, the techy people are looking at. We started figuring, okay, we'll start posting other meetings in the St. Louis area that might be of interest as well as other. 00:16:24.000 --> 00:16:40.000 dates and history, possibly, or things. So, we started putting the other stuff on there. Uh, then when COVID hit, uh, so many meetings went to, uh, online. There were a lot of good technical meetings that were online, and so we. 00:16:40.000 --> 00:16:54.000 We added those as well. There's a way in that calendar where you can separate them out if you want to see one, but not the other. But that's left to the, uh, left to the reader to figure that out for himself. 00:16:54.000 --> 00:16:57.000 We've got mailing lists also. 00:16:57.000 --> 00:17:12.000 mailing lists of the announce mailing list. Very limited traffic. It's it's moderated and probably maybe 2, 3, sometimes 4. 00:17:12.000 --> 00:17:29.000 announce things come out a month. But it's that limited. It's usually announcements of our meetings. Discuss is a general discussion. It's open to anybody who wants to sign up for it, and anybody who signs up for it can submit. 00:17:29.000 --> 00:17:42.000 Questions, comments? So a lot more activity there. And as you guessed, sometimes you may get a response in 30 minutes. Sometimes you may get a response in 10 days. 00:17:42.000 --> 00:17:58.000 Or longer. Steering Committee. If you like sausage, seeing sausage being made, that's where you want to be, is on our steering committee. But that's where we plan how these meetings put together, who the speakers are going to be, how the organization is kept together. We promise to disinfect first. 00:17:58.000 --> 00:18:00.000 There we go. 00:18:00.000 --> 00:18:10.000 Yeah, it's catch the pigs, skin the pig or kill a pig, skin the pig, and uh… boil the meat, and then make sausage. 00:18:10.000 --> 00:18:27.000 That's it, that's it. The sysadmin list is basically a a kind of a closed list. We're not saying you don't don't join it, but it's specifically for the sysadmins who are keeping our computers running. 00:18:27.000 --> 00:18:28.000 Goodbye. 00:18:28.000 --> 00:18:34.000 And so, yeah, we don't necessarily want everybody to, in case we accidentally reveal a password or something. So. 00:18:34.000 --> 00:18:41.000 Since the administration questions can be asked on discuss. Not a problem there, you know. 00:18:41.000 --> 00:18:43.000 Yeah. 00:18:43.000 --> 00:18:50.000 But the sysadmin list is for those people that are actually doing the work behind the scenes. No. 00:18:50.000 --> 00:19:07.000 Okay, next slide. And those are sponsored meetings, as the gentleman is asking about was slack meeting. As I said, the difference is, is the first two there, the Linux meeting and the general meeting, we, uh. 00:19:07.000 --> 00:19:17.000 We have planned topics. The the slack meeting and the new Linux meeting. We don't. It's just whatever people want to talk about. So. 00:19:17.000 --> 00:19:26.000 Well, new Linux is for a beginner workshop, and the Slack meeting is a configuration workshop. People have problems with their hardware or software, and. 00:19:26.000 --> 00:19:37.000 We try to help fix problems. We had the last Slack meeting, the young lady came in and she was having trouble with her sound, and we actually. 00:19:37.000 --> 00:19:56.000 shoulder, uh, the two tools that could help her configuration, and it just wasn't that the thing was broken, it just wasn't configured completely. Some distros automatically pick up certain hardware, and when they drop in, the configuration just works. 00:19:56.000 --> 00:20:09.000 You know, but you don't have to always switch to a different distro to get something to work. You can do the, you know, a little bit of exploring, you can configure it to make it work. 00:20:09.000 --> 00:20:13.000 Okay, before we go on, Gary, what's the call for help? 00:20:13.000 --> 00:20:21.000 All for help. After our main presentation tonight, there'll be time to. 00:20:21.000 --> 00:20:32.000 You know, ask questions about anything, but here in the middle of the meeting, we also provide a little time to ask questions. That's for people who don't feel they can stay around that late. 00:20:32.000 --> 00:20:50.000 Or they're afraid maybe the people with the answers won't be around that late. Um, so, uh, we'll just set aside a little time right now before we start our main presentation. And, uh, anybody who wants to ask a question, uh, now would be a good time, or if you want to make a comment about, hey, I tried this this week. 00:20:50.000 --> 00:21:04.000 It didn't work, or I had to do this to get it to work. Now would be a time we can at least start those conversations. We may finish them after the presentation, but yeah, anybody want to talk about anything now? 00:21:04.000 --> 00:21:09.000 We'll be open for another 5 seconds to allow people to unmute themselves. 00:21:09.000 --> 00:21:16.000 5… 4… 3… 2… 1. 00:21:16.000 --> 00:21:33.000 Okay, the main presentation, of course, that's what everybody came for. So it usually is on a Unix topic, or at least some open standards product. So. 00:21:33.000 --> 00:21:42.000 Open source operating system, open source code. They say mostly just open standards of some kind. So that comes down to. 00:21:42.000 --> 00:21:57.000 Linux, BSD, Unix, any other form of Unix. Okay. The main presentation obviously goes longer than the tutorial, and it's going to get deeper and dirtier into how things work. 00:21:57.000 --> 00:22:17.000 And often focused on enterprise computing. But we try and keep it so the hobbyist can come in and and. 00:22:17.000 --> 00:22:18.000 Lucia. 00:22:18.000 --> 00:22:26.000 you can get the information or. poke us to provide better information for the hobbyists. Okay, the presenter usually sends notes, Pdfs, and we try and put those things in the archive. So go back and look at our old list of talks, and you might find videos. 00:22:26.000 --> 00:22:31.000 Sound recordings, slide decks, a lot of good stuff. 00:22:31.000 --> 00:22:49.000 And the presenter can ask, can decide. Would you like the comments as he talks, or does he want to wait specific times when he asks for questions? Anytime Lee just said anytime. So feel free to ask any questions as it happens. 00:22:49.000 --> 00:23:08.000 And with that. I guess it's time to start our main presentation. As I said, Lee Lamert has been a long time member of this organization. He's on the board of directors, and he's the treasurer of the organization, and he has been very gracious in. 00:23:08.000 --> 00:23:24.000 setting up his computers at work to have virtual systems on them, virtual machines which are used for our mail services, our records, our website, etc. So a big thanks to Lee, as always, and I'm going to turn it over to Lee. 00:23:24.000 --> 00:23:30.000 All right, Gary, thank you very much. The question was arose. 00:23:30.000 --> 00:23:32.000 Okay, you should. I see your slide. I just, you know, we can see it. 00:23:32.000 --> 00:23:37.000 Somebody had a question. 00:23:37.000 --> 00:23:42.000 Okay, thank you. The question came up. 00:23:42.000 --> 00:23:52.000 Last month about. Dns. And some I mentioned pihole at one of our meetings. 00:23:52.000 --> 00:23:56.000 And then the question after that was, well, what is it? 00:23:56.000 --> 00:24:01.000 The thing called a pie hole, which was what we'll talk about. 00:24:01.000 --> 00:24:08.000 is basically a DNS system. And again, we'll define all this as we get started here. 00:24:08.000 --> 00:24:14.000 that blocks ads. in a very efficient manner. 00:24:14.000 --> 00:24:20.000 And the one we're going to be talking about. 00:24:20.000 --> 00:24:28.000 He's running here on this system. It's called a pie hole because it was originally built. 00:24:28.000 --> 00:24:35.000 Kapoir Raspberry Pi. and basically you took that. 00:24:35.000 --> 00:24:44.000 credit card size computer, put it in a case, hooked it to the network, and installed a an image on it. 00:24:44.000 --> 00:25:04.000 that was called Pi Hole. It's a very… simple to build takes you few minutes to burn ISO or burn a chip, stick it in the computer. In fact, we've got. We use raspberry pies here in the shop all the time. 00:25:04.000 --> 00:25:10.000 for servers, email servers, Dns servers, things like that. 00:25:10.000 --> 00:25:17.000 Anyway, that's where pie hole came from. And it is a DNS black hole. 00:25:17.000 --> 00:25:24.000 And we're going to define that here as we get started. 00:25:24.000 --> 00:25:30.000 To start off with. 00:25:30.000 --> 00:25:38.000 Ad blocking. Everybody's seen ads personally. Every time I sit down at a Windows computer with. 00:25:38.000 --> 00:25:42.000 Edge or Chrome or whatever people think they like. 00:25:42.000 --> 00:25:50.000 You get ads all over the place. What are you going to do about them? 00:25:50.000 --> 00:25:57.000 Well, most people want. Some people want ads. Most people don't like them. 00:25:57.000 --> 00:26:06.000 for 20 years I've used Firefox. And my Firefox configuration includes things like ad block. 00:26:06.000 --> 00:26:10.000 no script. Oh. 00:26:10.000 --> 00:26:15.000 things things like that. Mary. 00:26:15.000 --> 00:26:19.000 If you need to block anybody, you can do it over here. 00:26:19.000 --> 00:26:25.000 So you can. You can block ads at the network level. 00:26:25.000 --> 00:26:33.000 You can block them in a browser. But that takes a reasonable level of management. 00:26:33.000 --> 00:26:38.000 for all the an option is Dns level filtering. 00:26:38.000 --> 00:26:44.000 Which means that when the request goes out to an advertising. 00:26:44.000 --> 00:26:49.000 to an average. do an advertising site. 00:26:49.000 --> 00:26:55.000 It just gets dropped. And again, we're going to talk about that. 00:26:55.000 --> 00:27:07.000 The other aspect of ads. is that they almost always include some sort of traceable information. 00:27:07.000 --> 00:27:11.000 You know, Google for 2020 some odd years, 25 years. 00:27:11.000 --> 00:27:18.000 Includes a… includes tracking information every time you use a Google search. 00:27:18.000 --> 00:27:21.000 Or every time you click on a link on a Google website. 00:27:21.000 --> 00:27:29.000 And so the next place you go. on the web knows where he came from. 00:27:29.000 --> 00:27:36.000 That's how Google makes money selling that tracking information. 00:27:36.000 --> 00:27:43.000 So blocking the ads is a good way to reduce that tracking, make it a lot more private. 00:27:43.000 --> 00:27:52.000 also speeds up browsing because you're downloading less. information. 00:27:52.000 --> 00:27:56.000 And if you do it at the network level. 00:27:56.000 --> 00:28:06.000 It works across any device on the network. because you don't have to do it on the network. 00:28:06.000 --> 00:28:08.000 I'm sorry, you don't have to do it on the device. 00:28:08.000 --> 00:28:14.000 So basically, we've talked about 3 different levels of ad blocking at this point. 00:28:14.000 --> 00:28:25.000 At the network level. the Dns level and at the machine level at a browser. 00:28:25.000 --> 00:28:34.000 Everybody knows what Dns is, I hope. The whole point of DNS is you need to take a name. 00:28:34.000 --> 00:28:41.000 and turn that name into an IP address that is usable on the net. 00:28:41.000 --> 00:28:45.000 to get to get to that source, that destination. 00:28:45.000 --> 00:28:55.000 It's used for web browsing, OS updates, streaming, mobile apps. 00:28:55.000 --> 00:29:06.000 Traditional ad blocking, then. A browser receives a page. The ads partially load. The browser extension attempts to remove them. 00:29:06.000 --> 00:29:11.000 The issue there is is browser-specific. You have to have an add-in. 00:29:11.000 --> 00:29:16.000 Again, I've been using Firefox for probably 25 years. 00:29:16.000 --> 00:29:21.000 And the extensions you get in Firefox do a pretty good job. 00:29:21.000 --> 00:29:27.000 With no script, I block all the Google tag services or Google syndication. 00:29:27.000 --> 00:29:36.000 with add block or you block origin, I think, is one of question. 00:29:36.000 --> 00:29:40.000 you know, those extensions will do a pretty good job. 00:29:40.000 --> 00:29:49.000 But they have to be installed and configured. in each browser you're using each device you're using. 00:29:49.000 --> 00:30:00.000 and they can be bypassed, and sometimes you have to bypass them to make the site function correctly. 00:30:00.000 --> 00:30:06.000 The pie hole is a DNS level filter. Where your browser? 00:30:06.000 --> 00:30:15.000 Submits a DNS request. and your machine is configured to use the pie hole. 00:30:15.000 --> 00:30:21.000 Dns system. to either allow that request. 00:30:21.000 --> 00:30:28.000 or block it. And when you block it. It's just thrown away. 00:30:28.000 --> 00:30:36.000 So what happens is, whenever the browser requests something that the pie hole recognizes as. 00:30:36.000 --> 00:30:42.000 A malicious site or a site to blacklist. It gets blocked. 00:30:42.000 --> 00:30:51.000 and the system never sees it. 00:30:51.000 --> 00:30:58.000 Okay, we talked about what Dns is. Basically, 10erexample.com into an IP address. 00:30:58.000 --> 00:31:10.000 and like a phone book. Ads. Then there are many levels, many components to add systems. 00:31:10.000 --> 00:31:17.000 An ad itself could just be, oh, hey, buy this product with our phone number happens to belong to the website. 00:31:17.000 --> 00:31:25.000 That's an ad from the website. Most commercial services nowadays, though, take that to the next level. 00:31:25.000 --> 00:31:43.000 where they sell ads to third parties. and then Google's claim to fame is those third parties that can say, we want you to present our ad to users that have an interest in this subject. 00:31:43.000 --> 00:31:55.000 So those servers will serve up an ad. There are analytic providers that will look at the data that is. 00:31:55.000 --> 00:32:01.000 track as that ad goes passing around the system. 00:32:01.000 --> 00:32:09.000 The tracking systems will. collect the data for that particular ad ID. 00:32:09.000 --> 00:32:15.000 and a lot of cases there are ad networks involved, primarily Google. They're the big boy in the room. 00:32:15.000 --> 00:32:24.000 because they've made trillions of dollars serving ads to companies that want to pay them for it. 00:32:24.000 --> 00:32:34.000 All those little aside, 20 years ago, when they were just really… getting big. They had this concept called Google Adwords. 00:32:34.000 --> 00:32:42.000 Well, I spent six months trying to find a way to pay Google. 00:32:42.000 --> 00:32:52.000 10 cents, 25 cents, whatever for any search that included the terms Linux and St. Louis or Linux and Missouri. 00:32:52.000 --> 00:32:59.000 I couldn't do it. They would not take my money. They would not take an offer. They would not give me a caution. 00:32:59.000 --> 00:33:10.000 which was extremely frustrating. But eventually I learned. Late a lot later on, that there were so few requests for those keywords. 00:33:10.000 --> 00:33:20.000 Google didn't want to bother with them. 00:33:20.000 --> 00:33:28.000 Some of the ads, Google syndication we mentioned double click news sites, Facebook scorecard research. 00:33:28.000 --> 00:33:37.000 There's a whole bunch of them that you see over the years. 00:33:37.000 --> 00:33:52.000 The basic concept of that Dns black hole. is to recognize the fact that this domain is not nice about ads and tracking. 00:33:52.000 --> 00:34:01.000 So they get blocked. It by blocking it, it means that when the Dns request is made. 00:34:01.000 --> 00:34:10.000 For tracker.example.com, nothing is returned. It's just discarded. 00:34:10.000 --> 00:34:20.000 A return is is sent. So the process doesn't hang, but the contents of that response is null. 00:34:20.000 --> 00:34:26.000 And of course, if there is no IP address returned for that name, the connection cannot be made. 00:34:26.000 --> 00:34:37.000 There's no ad download, no tracks or execution. Your IP address is not added into the tracker log for that ad site. 00:34:37.000 --> 00:34:44.000 Which means… It breaks. 00:34:44.000 --> 00:34:49.000 So the next question is, how do we implement that black hole? 00:34:49.000 --> 00:34:58.000 Well, one of them, which I mentioned earlier, was… I could grab a raspberry Pi off the shelf. 00:34:58.000 --> 00:35:03.000 build an image for it. put it on a micro SD card. 00:35:03.000 --> 00:35:07.000 drop it in the… Pi. 00:35:07.000 --> 00:35:12.000 Plug it in, you know, add power, plug it into the network. 00:35:12.000 --> 00:35:22.000 and assuming you set the Ips correctly, it would start working in about 45 seconds to a minute. 00:35:22.000 --> 00:35:30.000 Unfortunately, that presented a practical problem when I started thinking about this the presentation. 00:35:30.000 --> 00:35:34.000 Because you don't have a console on a pie. 00:35:34.000 --> 00:35:42.000 that you can easily share with a presentation. Yeah, you could SSH to it. 00:35:42.000 --> 00:35:51.000 But you can't walk through it. You can't see the gooey. So I decided to build it on my machine. 00:35:51.000 --> 00:36:05.000 So we can play with it. The admin page we're looking at here for the pie hole, which again is running on my workstation here. We'll see more about it here in a few minutes. 00:36:05.000 --> 00:36:17.000 is actually in a container. We've talked about containers a lot over the last, what, 10, 12 years? You know, way back when. 00:36:17.000 --> 00:36:23.000 Chuck and I, Chuck mostly did a whole series on how to run a container. 00:36:23.000 --> 00:36:37.000 I've been doing it a lot. There's actually some really sophisticated container environments like Kubernetes, which is the foundation for almost every mainstream application on the internet. 00:36:37.000 --> 00:36:44.000 You know, every major server is running Kubernetes. Because it's the only way you can do it. 00:36:44.000 --> 00:36:51.000 You have to have redundancy, you have to be able to load balance across different geographical layers areas. 00:36:51.000 --> 00:37:00.000 and at the simplest level, that is just a connection of 10, 15, 20, 50, 100 different containers. 00:37:00.000 --> 00:37:16.000 Each container. By the way. What's this? What's the simplest way to look look at a container? How do you? How do you tell if a container is running? 00:37:16.000 --> 00:37:25.000 Somebody give me a command. You may have to unmute. 00:37:25.000 --> 00:37:26.000 talk repeated. 00:37:26.000 --> 00:37:30.000 This way, you would run… you would run this on the on the Raspberry Pi, or is it something you… 00:37:30.000 --> 00:37:37.000 No, no, on my machine. I built a container for the pie hole. 00:37:37.000 --> 00:37:45.000 If you're running on a pie, it's native on the pie. And you have a command prompt. 00:37:45.000 --> 00:37:49.000 But since it's running on a container on my workstation here. 00:37:49.000 --> 00:37:54.000 Let me bump the font a bit for you guys. 00:37:54.000 --> 00:38:01.000 It is running in a container. And what runs containers? There's 2 ways to do it. 00:38:01.000 --> 00:38:04.000 I believe it's Docker PS is the command. 00:38:04.000 --> 00:38:10.000 You got it. Thank you. Docker Ps. 00:38:10.000 --> 00:38:15.000 shows me what containers are running on this system. 00:38:15.000 --> 00:38:25.000 In this case, I have an ID. I have an image that this container was built from. 00:38:25.000 --> 00:38:32.000 I here have the command. that started the container. 00:38:32.000 --> 00:38:38.000 This instance was created 3 hours ago. It's been up 3 h. It's healthy. 00:38:38.000 --> 00:38:46.000 and it shows the port bindings. 00:38:46.000 --> 00:38:53.000 port 53 is what? 00:38:53.000 --> 00:39:01.000 53 Tcp. and 53 Udp. What's what's Pcp ip port 53? 00:39:01.000 --> 00:39:02.000 Okay, nice. 00:39:02.000 --> 00:39:06.000 Dns. Thank you. 00:39:06.000 --> 00:39:09.000 Everybody knows what port 80 is, right? HTML. Which is. 00:39:09.000 --> 00:39:14.000 HTML. 00:39:14.000 --> 00:39:23.000 how you talk to it. This is, you know, you usually this is the admin console here on port 80. 00:39:23.000 --> 00:39:33.000 In fact… Let me shrink this… This is the actual URL to talk to it. 00:39:33.000 --> 00:39:44.000 Local host slash admin. Since the the pie hole binds to port 80 or is bound to port 80. 00:39:44.000 --> 00:39:49.000 You talk to it, you look at the admin page. 00:39:49.000 --> 00:39:54.000 by going to it with a container localhost slash admin. 00:39:54.000 --> 00:39:59.000 We'll see more details here in a few minutes when we talk, when we look at the compose file. 00:39:59.000 --> 00:40:01.000 This is Stan. I got a little question. Port 443, isn't that HTMS secure? 00:40:01.000 --> 00:40:06.000 Go. 00:40:06.000 --> 00:40:07.000 Yes, it is. But since it's a local machine, there's no network transport involved. 00:40:07.000 --> 00:40:11.000 And. 00:40:11.000 --> 00:40:18.000 There's no no reason to to build a certificate for it. 00:40:18.000 --> 00:40:27.000 Although it's easy to do. Yeah, there's no there's no reason for it. Besides, I had enough problems this afternoon getting this thing running properly. 00:40:27.000 --> 00:40:28.000 Thank you. 00:40:28.000 --> 00:40:33.000 You're welcome. Anybody else? 00:40:33.000 --> 00:40:39.000 I don't know if they still do it. But I thought at one time. 00:40:39.000 --> 00:40:50.000 When they would look up a name. And if it was like a, you know, a… tracking side or whatever. 00:40:50.000 --> 00:40:55.000 Pyle would, in effect. Give it. 00:40:55.000 --> 00:41:09.000 its own IP address. And so when the web browser requested that from the pile, the pile had a web server on it and its only purpose was to send back a. 00:41:09.000 --> 00:41:13.000 one pixel transparent GIF file, I think it was. 00:41:13.000 --> 00:41:21.000 through the web browser. So the web browser was none the wiser on what was going on. 00:41:21.000 --> 00:41:28.000 Good. Good point. I'm not sure. 00:41:28.000 --> 00:41:29.000 I I I remember seeing. 00:41:29.000 --> 00:41:36.000 I remember reading about that a long time ago, but, you know, I haven't kept up with it, so maybe they changed that lately. 00:41:36.000 --> 00:41:41.000 I do remember that story, Phil. I don't know if it was. 00:41:41.000 --> 00:41:48.000 So just from us talking about it years ago, or I don't remember where I would have read it. 00:41:48.000 --> 00:41:59.000 Yeah. Okay? And and finally on the Docker PS line is the name of the container Pihole. 00:41:59.000 --> 00:42:09.000 So here's here's another command that I use all the time. 00:42:09.000 --> 00:42:14.000 If I actually want to connect to the container. 00:42:14.000 --> 00:42:18.000 I don't have to SSH Stuart. I don't have to. 00:42:18.000 --> 00:42:24.000 use any tool. From the host where the container is running. 00:42:24.000 --> 00:42:28.000 I do Docker exec. minus TI. 00:42:28.000 --> 00:42:35.000 Container name and command. And I'm actually. 00:42:35.000 --> 00:42:45.000 I have a command prompt inside the container. 00:42:45.000 --> 00:42:50.000 You know, this is that actually that actual pie hole container. 00:42:50.000 --> 00:42:55.000 And this is how I can go in and change things. 00:42:55.000 --> 00:43:11.000 Although, if I do change something. 00:43:11.000 --> 00:43:16.000 you know, if I create a file in this container. 00:43:16.000 --> 00:43:24.000 What is the… ramification of restarting the container. 00:43:24.000 --> 00:43:28.000 In other words, doing Docker compose up minus D. 00:43:28.000 --> 00:43:31.000 I would assume that that file goes away. 00:43:31.000 --> 00:43:33.000 Why? 00:43:33.000 --> 00:43:45.000 There is an ephemeral system. It's going to rebuild the entire container from from the registry or whatever's cached everything the moment you tell Docker to shut down everything in the Docker. 00:43:45.000 --> 00:43:53.000 container goes away. You'll have to mount… The directory that you're looking to hold onto. 00:43:53.000 --> 00:43:56.000 Locally. 00:43:56.000 --> 00:44:03.000 Yep. A Docker container is a read-only image. 00:44:03.000 --> 00:44:09.000 When you run it. you instantiate it, you create a copy in memory. 00:44:09.000 --> 00:44:12.000 You can go in there and play with it all day long. 00:44:12.000 --> 00:44:23.000 But when you shut down. you revert to the image that was saved before. 00:44:23.000 --> 00:44:32.000 Uh… 00:44:32.000 --> 00:44:39.000 Oh, never mind. It helps if you're on a host. 00:44:39.000 --> 00:44:47.000 Good. These are the 2 physical images I have on the host. 00:44:47.000 --> 00:44:55.000 This one latest had problems this afternoon. So I looked up and grabbed. 00:44:55.000 --> 00:45:00.000 A recent version. and that's the one I'm using. 00:45:00.000 --> 00:45:12.000 continues. It's also it's also a lot bigger, 115 meg versus 42 meg. 00:45:12.000 --> 00:45:20.000 No. Okay. And I'm confused. The one that's called latest then is not actually the latest. 00:45:20.000 --> 00:45:27.000 That is the latest image. Remember? Container images are always. 00:45:27.000 --> 00:45:31.000 Read on it. In other words, they're static. Right. 00:45:31.000 --> 00:45:45.000 Once you run them. They're in memory, and yes, you can change them, but as soon as you stop them, it's gone. It's gone. And then when you next time you start it, you get a copy of the original image again. Okay. 00:45:45.000 --> 00:45:51.000 And this happened to be the latest one. I don't know what the data was on it. It's immaterial. 00:45:51.000 --> 00:45:56.000 But I had a problem with that. The web server, the admin server wasn't running properly. 00:45:56.000 --> 00:46:03.000 So I went back to a previous version. 00:46:03.000 --> 00:46:09.000 Okay… Okay. Okay. 00:46:09.000 --> 00:46:20.000 and that whole process. Let's see, where are we? 00:46:20.000 --> 00:46:35.000 Uh, let's see why a container? The simplest way to provide a service. Containers provide services. We'll talk about that here in a few minutes. 00:46:35.000 --> 00:46:43.000 They isolate that service to a simple environment that is contained. 00:46:43.000 --> 00:46:49.000 within that container image. 00:46:49.000 --> 00:46:53.000 You can easily… you can upgrade a container at any point in time. 00:46:53.000 --> 00:47:03.000 You never have to touch a host Os. In fact, sometimes at some point soon, I've been building some servers in the back room for AI. 00:47:03.000 --> 00:47:07.000 I will show you what. A. 00:47:07.000 --> 00:47:13.000 OS looks like that is built to run containers. 00:47:13.000 --> 00:47:22.000 where the OS itself acts like a container. It is a read-only system. 00:47:22.000 --> 00:47:28.000 That is immutable. It cannot be changed. 00:47:28.000 --> 00:47:29.000 Thank you. 00:47:29.000 --> 00:47:35.000 They got to be replicated. 00:47:35.000 --> 00:47:36.000 Hey, Tyler. Is your mic open? 00:47:36.000 --> 00:47:40.000 Yeah. Let me turn it off. 00:47:40.000 --> 00:47:49.000 We can hear a lot of key clicks. OSP clicks. It's not like somebody sucking on a straw. 00:47:49.000 --> 00:47:56.000 Thank you. All right. 00:47:56.000 --> 00:48:02.000 What makes it possible? Well, in the Docker world, in the container world is called is git. 00:48:02.000 --> 00:48:09.000 We've had many presentations on Git over the years. It is the backbone. 00:48:09.000 --> 00:48:17.000 of almost every system on the Internet. Windows and Linux and everything else. 00:48:17.000 --> 00:48:22.000 Because it gives you a lot of advantages. It runs on everything. 00:48:22.000 --> 00:48:28.000 When you check out a version, it is guaranteed to be the same as the last time you checked it out. 00:48:28.000 --> 00:48:32.000 If you want to upgrade it, you can easily. 00:48:32.000 --> 00:48:39.000 Post a commit. If you have something breaks, you can roll back to the previous one. 00:48:39.000 --> 00:48:50.000 There are no dependencies involved. and it also also works great for demos. 00:48:50.000 --> 00:48:56.000 Okay, this is what we have tonight. 00:48:56.000 --> 00:49:01.000 The lab is my workstation. Actually, my workstation right here. 00:49:01.000 --> 00:49:07.000 We have a pie hole container. We have the slides we're looking at. 00:49:07.000 --> 00:49:17.000 and we have a demo Vm. that uses… by whole DNS. 00:49:17.000 --> 00:49:24.000 In fact, that's why. We've got the numbers up here. 00:49:24.000 --> 00:49:36.000 13, 1,375 report queries so far, 127 blocked around 9%. 00:49:36.000 --> 00:49:44.000 building a container. There is a thing called a… Compose file. 00:49:44.000 --> 00:49:54.000 Notice that in this directory I have a compose file right here. 00:49:54.000 --> 00:50:06.000 See, what tab is it on right here? I put the compose file in the presentation here so that if you want to, if you download the PDF, you can find it. 00:50:06.000 --> 00:50:11.000 If you want, drop me a note. I'll be happy to send you a copy of it. 00:50:11.000 --> 00:50:17.000 I want to make sure that you don't mistype anything. 00:50:17.000 --> 00:50:28.000 A composed file is very simple. Remember, before I said that Docker is… has one function in life, and that's to provide a service. 00:50:28.000 --> 00:50:36.000 There's one service in this compose file. pie hole that is a service involved. 00:50:36.000 --> 00:50:42.000 So I'm going to like the compose file for Jitsi had like 15 or 20. 00:50:42.000 --> 00:50:50.000 Services, all defined in a single compose file. Each service. 00:50:50.000 --> 00:50:56.000 Has a name. as an image. 00:50:56.000 --> 00:51:04.000 We've talked about this in the past. The restart allows you to control what happens if. 00:51:04.000 --> 00:51:14.000 You lose power, our systems reset, or whatever. In this case, this container will always restart. 00:51:14.000 --> 00:51:23.000 Upon boot up. Unless you… it was physically stopped at the time. 00:51:23.000 --> 00:51:32.000 post name. Here's the 3 port definitions. DNS can be either TCP or UDP. 00:51:32.000 --> 00:51:36.000 and then port 80, then, for the admin console. 00:51:36.000 --> 00:51:43.000 Here's the environment. 00:51:43.000 --> 00:51:50.000 time zone central web web password change me, which I didn't bother to change. 00:51:50.000 --> 00:51:57.000 and FTL conf. FTL is the. 00:51:57.000 --> 00:52:06.000 Name that they use internally in Pihole. and we have 2 upstream servers of 5. 00:52:06.000 --> 00:52:11.000 1.1 9.9. 00:52:11.000 --> 00:52:20.000 I forget which is which. I think 1.1 is Cloudflare. 9.9 is one of the other major providers, if I remember correctly. 00:52:20.000 --> 00:52:35.000 What did FTL stand for? I even think it was faster than light, but that's the name that PIHO uses for his services. Right. 00:52:35.000 --> 00:52:44.000 Sometimes you need to keep data between. container boots. 00:52:44.000 --> 00:52:51.000 in which… in which case you mount a local volume. 00:52:51.000 --> 00:52:56.000 to the container. 00:52:56.000 --> 00:53:00.000 So the container container is on the the left. 00:53:00.000 --> 00:53:05.000 the… system is on the right. 00:53:05.000 --> 00:53:13.000 our our vice versa. So there's 2 actual directories. 00:53:13.000 --> 00:53:29.000 in the directory where the container runs. Here's scdnsmask.d and Etsyhole. 00:53:29.000 --> 00:53:36.000 Miss Dns mask. nearby home. 00:53:36.000 --> 00:53:39.000 And if we and if we look in the container. 00:53:39.000 --> 00:53:46.000 You would see the exact same thing in Etsy slash piho. 00:53:46.000 --> 00:54:04.000 Where's my container? 00:54:04.000 --> 00:54:11.000 Here's Etsy pie hole directory. in the container. 00:54:11.000 --> 00:54:17.000 and I see what was the other one? The other one was Dns masks. 00:54:17.000 --> 00:54:41.000 and here's Gina's mask up here. you guys may ask that D. 00:54:41.000 --> 00:54:44.000 and there's the 2 files we just saw on a host. 00:54:44.000 --> 00:54:54.000 In the directory. Okay, cool. 00:54:54.000 --> 00:55:15.000 So that's the Docker compose in a nutshell. If you want to run it. 00:55:15.000 --> 00:55:23.000 Docker command. Compose. We'll look for the docker compose file in the current directory. 00:55:23.000 --> 00:55:28.000 Up is the command up. and minus D. 00:55:28.000 --> 00:55:42.000 means convert to a demon. In other words, once you will not see any standard out will not go to the console and the container will just start itself. 00:55:42.000 --> 00:55:48.000 And then it will run in the background. and that is how. 00:55:48.000 --> 00:55:57.000 I started a container here 3 hours ago. 00:55:57.000 --> 00:56:04.000 Okay. 00:56:04.000 --> 00:56:09.000 One of the problems I did find this afternoon. 00:56:09.000 --> 00:56:15.000 Is the permissions were wrong. on. 00:56:15.000 --> 00:56:24.000 the buying mouse. come to find come to find out there was an SE Linux problem. 00:56:24.000 --> 00:56:30.000 as sclinux is the the favorite tool everybody wants to hate. 00:56:30.000 --> 00:56:37.000 In the Docker world. by putting a colon Z on the end of the mount. 00:56:37.000 --> 00:56:42.000 volume, volume mount. 00:56:42.000 --> 00:56:48.000 a capital Z. Means keep the volumes private. 00:56:48.000 --> 00:56:55.000 and only this container should use it. 00:56:55.000 --> 00:56:59.000 Notice that I have lowercase Z's on these volumes. 00:56:59.000 --> 00:57:05.000 And that's the opposite case. 00:57:05.000 --> 00:57:11.000 It's that volume can be shared. amongst anyone. 00:57:11.000 --> 00:57:17.000 or any container. 00:57:17.000 --> 00:57:34.000 and you were joking that… People hate this because of SC Linux. No, people hate SE Linux, because when something breaks, you never know what it is. Okay. 00:57:34.000 --> 00:57:43.000 Just as an aside. 00:57:43.000 --> 00:57:50.000 Whenever I said, whenever I have a weird problem on the server, the first thing I do is look for SE Linux. 00:57:50.000 --> 00:57:59.000 can't enforce. 00:57:59.000 --> 00:58:03.000 Okay, we talked about starting at a composed file. 00:58:03.000 --> 00:58:08.000 And again, that compose file is. What would you… what we were just looking at? 00:58:08.000 --> 00:58:17.000 If you name it docker-compose.yaml. Then you don't have to get. You don't have to give compose a file name. 00:58:17.000 --> 00:58:26.000 It will assume that that is a file name in the current directory where the command is issued. 00:58:26.000 --> 00:58:36.000 We mentioned the dashboard. This shows all the information about. 00:58:36.000 --> 00:58:52.000 you know, a pie hole? It is… You know, if query log, we've got, this is just everything in the last three hours. 00:58:52.000 --> 00:59:00.000 and there is only one system using the pie hole for the last 3 h. 00:59:00.000 --> 00:59:05.000 and it has come up with 18 pages of crust. 00:59:05.000 --> 00:59:16.000 and you can probably guess who guess who it is by looking at that page. 00:59:16.000 --> 00:59:28.000 That is my ancient Windows 10 Vm. and he has just been farting around looking for. 00:59:28.000 --> 00:59:37.000 Oh. updates, probably. 00:59:37.000 --> 00:59:48.000 Yeah, he's doing updates. 00:59:48.000 --> 00:59:54.000 Of course, I I haven't booted it in probably a year. 00:59:54.000 --> 01:00:02.000 That's the only way around windows in the Vm. 01:00:02.000 --> 01:00:11.000 Yeah. Speaking of windows… When I create my Windows VM, I have one. 01:00:11.000 --> 01:00:19.000 I don't like it, but… I give it eight gig of memory. Is that enough to run a Windows VM? 01:00:19.000 --> 01:00:23.000 Yeah, most of the time. 01:00:23.000 --> 01:00:26.000 Okay. 01:00:26.000 --> 01:00:35.000 If you want decent performance out of it, though, but you might want to go to 16. 01:00:35.000 --> 01:00:42.000 No. That'd be the whole computer. 01:00:42.000 --> 01:00:54.000 Okay, the dashboard has query logs. Domains that were blocked, see if we can see how I can find that real quick. 01:00:54.000 --> 01:01:05.000 Uh… We lost… 01:01:05.000 --> 01:01:24.000 Hmm. 01:01:24.000 --> 01:01:32.000 No, I'm not. I'm not sure. 01:01:32.000 --> 01:01:38.000 I will come back to query log one. 01:01:38.000 --> 01:01:47.000 Okay, we're in the status column. block, and then it says gravity in parentheses. 01:01:47.000 --> 01:01:55.000 Gravity is the source of the blacklist. 01:01:55.000 --> 01:02:08.000 Yeah, remember there we. Uh, see, there's… 80, 82,000 domains on the ad list. There are many different ad lists that are used. 01:02:08.000 --> 01:02:17.000 or that pile uses to decide what to block. Okay. 01:02:17.000 --> 01:02:21.000 So that when you 1st start this out, you have to choose. 01:02:21.000 --> 01:02:38.000 No, it's it's all built in. Okay, okay. It just so happens those 1st 2 were found in the gravity list because I'm looking down further now, and there's other ones that are came from other places. Okay. 01:02:38.000 --> 01:02:46.000 Yeah, I see. Oh, that might have been. Yeah, that was the oldest page. 01:02:46.000 --> 01:02:54.000 That was some of the first the 1st cruft that threw out. 01:02:54.000 --> 01:03:04.000 Although… I'm surprised that the. 01:03:04.000 --> 01:03:12.000 list of block domains isn't isn't up here. because this is domain management. 01:03:12.000 --> 01:03:18.000 That allows you to whitelist, I'm assuming. 01:03:18.000 --> 01:03:24.000 got domain to be added. Project. 01:03:24.000 --> 01:03:31.000 Okay. 01:03:31.000 --> 01:03:39.000 Remember, we've got a VM with a browser. We've got the pie hole. 01:03:39.000 --> 01:03:48.000 container that is running pihole. Which passes the query upstream to 1.1 or 9.9. 01:03:48.000 --> 01:04:01.000 and then the reply comes back and gives you a valid IP address. 01:04:01.000 --> 01:04:06.000 This is the part I haven't looked at yet. 01:04:06.000 --> 01:04:16.000 Friday thirteenth adds pop-ups, trackers, autoplay junk. Oh, speaking of which I was going to try. 01:04:16.000 --> 01:04:26.000 YouTube. 01:04:26.000 --> 01:04:47.000 Notice the DNS server configured here. which is my workstation where the port 53 is. 01:04:47.000 --> 01:05:02.000 Damn it. 01:05:02.000 --> 01:05:32.000 Is it nice to have no ad pop-ups on the on the home page? Yeah. 01:05:42.000 --> 01:05:48.000 All right. We talked about containers. I would challenge anyone. 01:05:48.000 --> 01:05:54.000 to get familiar with it. There are a lot of gotchas. 01:05:54.000 --> 01:06:02.000 I can pass along a hint ChatGPT 5.5 is pretty good about debugging. 01:06:02.000 --> 01:06:18.000 Okay. In fact, that's that's how I got the Jitsi server running this last week. 01:06:18.000 --> 01:06:27.000 I actually did find a problem. There are various utilities that could be. 01:06:27.000 --> 01:06:38.000 bound to port 53. If you have a problem, look for some system D resolver possibly. 01:06:38.000 --> 01:06:45.000 which are which is basically a DNS forwarder. Dns mask. 01:06:45.000 --> 01:06:51.000 is actually what the pile uses. 01:06:51.000 --> 01:07:02.000 and name D, obviously, since that is actually a server. 01:07:02.000 --> 01:07:09.000 One of the best advantages of using something like a pie hole as your DNS server. 01:07:09.000 --> 01:07:15.000 is that you get to trap all. devices on the network. 01:07:15.000 --> 01:07:22.000 I'm just using the one Vm here, which is still humping Windows 10 updates. 01:07:22.000 --> 01:07:29.000 But you know, as we saw, there are… 01:07:29.000 --> 01:07:34.000 153… Dns queries that have been blocked. 01:07:34.000 --> 01:07:40.000 Just in the Windows update cycle. 01:07:40.000 --> 01:07:44.000 In addition, yeah, go ahead. 01:07:44.000 --> 01:07:51.000 Have you noticed how many major PC companies are switching over to default to some version of Linux? 01:07:51.000 --> 01:07:56.000 No, they're not switching over, they are making it available as an option. 01:07:56.000 --> 01:08:12.000 Actually… I was reading something yesterday that said Dell, if you don't say anything, you get… Linux, I forget which version they use, but… If you want to pay a little extra money, you can have windows. 01:08:12.000 --> 01:08:15.000 And I think HP is doing the same thing. 01:08:15.000 --> 01:08:22.000 That's, that's on certain models that they give you the option is what it amounts to. 01:08:22.000 --> 01:08:29.000 And it's generally the lower-priced units because those are the ones that they can build without the. 01:08:29.000 --> 01:08:33.000 TPM or TMP version 2 chip and all that kind of stuff. 01:08:33.000 --> 01:08:35.000 TPM. Yeah. 01:08:35.000 --> 01:08:39.000 Yeah. 01:08:39.000 --> 01:08:44.000 Well, you can… I'm not sure it's a TPM, but. 01:08:44.000 --> 01:08:51.000 When I got my… when I got a new laptop last fall, I actually had to replace the Wi-Fi chip in it. 01:08:51.000 --> 01:08:57.000 Because the one that came with it was built for Windows, and it wasn't standard hardware. 01:08:57.000 --> 01:09:07.000 and there was no Linux driver for it. So I spent 20 bucks for an Intel chip, dropped it in there, and they're at a problem. 01:09:07.000 --> 01:09:08.000 Now, when you say dropped it in. Explain that a little bit. 01:09:08.000 --> 01:09:12.000 I think… the laptop. 01:09:12.000 --> 01:09:15.000 I dropped in the laptop. 01:09:15.000 --> 01:09:16.000 Write the keyboard off. pry the keyboard off. 01:09:16.000 --> 01:09:18.000 Yeah, I know what you said. 01:09:18.000 --> 01:09:23.000 No, in this case, and in this case, it was a back panel. Depends on the hardware. 01:09:23.000 --> 01:09:24.000 Okay. 01:09:24.000 --> 01:09:32.000 But the point I was making is. Dell and HP aren't going to offer Linux on their cheapy stuff. 01:09:32.000 --> 01:09:41.000 Because they don't want to spend the extra 15 bucks a unit to put in hardware that's guaranteed to be compatible. 01:09:41.000 --> 01:09:43.000 Wait a minute, say that again? 01:09:43.000 --> 01:09:51.000 I said, I don't think Dell or Hp. Is going to offer Linux on their cheapy models. 01:09:51.000 --> 01:10:02.000 Because to guarantee the Linux work on the cheapy model, they're going to have to spend an extra 10, 15, 20 bucks for hardware that doesn't require. 01:10:02.000 --> 01:10:09.000 a Windows driver that's actually the program to run the hardware. 01:10:09.000 --> 01:10:17.000 Because what I… what I was reading, it says that's exactly the ones they were going to do it on. 01:10:17.000 --> 01:10:23.000 There's not much money in a cheap laptop, not much profit for Dell or HP. 01:10:23.000 --> 01:10:31.000 And if you take out the cost of the… Windows software, which is not free. 01:10:31.000 --> 01:10:38.000 They make more money. The other thing that they were saying is they get so many fewer. 01:10:38.000 --> 01:10:43.000 A customer calls, because when Windows 11 doesn't want to work. 01:10:43.000 --> 01:10:54.000 The computer manufacturer has to field that… those calls don't go to Microsoft, they go to HP or whatever. 01:10:54.000 --> 01:10:59.000 And apparently that's a significant savings. 01:10:59.000 --> 01:11:02.000 Good point. I'm surprised by the low end models, though, because there is so much croft. 01:11:02.000 --> 01:11:08.000 I don't know. 01:11:08.000 --> 01:11:13.000 Especially Wi-Fi drivers on laptops. You know, if it's the El Cheapo version. 01:11:13.000 --> 01:11:22.000 is not going to use a standard driver. It's going to have to use a Windows driver which actually downloads the executable code into the chip. 01:11:22.000 --> 01:11:27.000 When you boot it. 01:11:27.000 --> 01:11:34.000 Because that that's that's the way I figured it out on my vivo book. 01:11:34.000 --> 01:11:35.000 Hmm. 01:11:35.000 --> 01:11:46.000 Jackson, you know, it actually has the same Cpu as my main workstation does, so 1010 core i9. 01:11:46.000 --> 01:11:47.000 Yeah, go ahead. 01:11:47.000 --> 01:11:54.000 Man, yeah. Oh, I guess I have a question about well. 01:11:54.000 --> 01:12:06.000 in one environment, uh, also that pie hole could run in, can we could it work in the terminal on on windows? 01:12:06.000 --> 01:12:11.000 Uh… I don't know if there is a Windows version. 01:12:11.000 --> 01:12:13.000 Let me check. Okay. Oh. 01:12:13.000 --> 01:12:30.000 I'm thinking you might, you might be able to run a container under Wizzle. Anybody? Any of you guys that get stuck in the Windows world know if that's possible? 01:12:30.000 --> 01:12:32.000 Say that again? 01:12:32.000 --> 01:12:33.000 He was asking if he could run pi hole on Windows. 01:12:33.000 --> 01:12:37.000 Oh, uh… 01:12:37.000 --> 01:12:45.000 and I don't know if there's a Windows version out there, but I was wondering if you can run containers in Wizzle on windows. 01:12:45.000 --> 01:12:51.000 Yes, yes, I do it. I actually build my containers at work on my work laptop in the WSL. 01:12:51.000 --> 01:12:52.000 Okay. 01:12:52.000 --> 01:12:56.000 It's the only way it actually works. 01:12:56.000 --> 01:12:57.000 Interesting. 01:12:57.000 --> 01:13:07.000 Okay, cool. Because I've been I've been learning a little bit about, you know, Vms a little bit. But I guess I was kind of wondering how I could. 01:13:07.000 --> 01:13:28.000 Um… You know, get it to work where it's still… Uh, on Windows, that way I don't, like, maybe have to, uh, you know, fire up the virtual machine along with it, or… If I'd have to do my browsing on the virtual machine, or… I was just thinking about it, and just wondered. 01:13:28.000 --> 01:13:34.000 Yeah, well, technically, then you would use Windows Subsystem for Linux. 01:13:34.000 --> 01:13:44.000 You'll run Docker there and run the container there, figure out your bindings, and then every time you start a laptop, it would bring up the container. 01:13:44.000 --> 01:13:45.000 Oh. Okay. 01:13:45.000 --> 01:13:50.000 Can you use that for your Dns server? 01:13:50.000 --> 01:13:57.000 Okay, yeah, that's awesome. That sounds… hold on. Sounds like worth learning how to do that, yeah. 01:13:57.000 --> 01:13:58.000 Well, thank you. 01:13:58.000 --> 01:14:07.000 Yeah. Maybe if somebody wants to do that from the Windows world, maybe we do a base in the future. Yeah, yeah. 01:14:07.000 --> 01:14:15.000 But that means I have to install Windows. 01:14:15.000 --> 01:14:18.000 Well, can you run Wizzle on in a VM? 01:14:18.000 --> 01:14:19.000 You know, in a Windows video. Say again. 01:14:19.000 --> 01:14:23.000 Whistle is a VM. Whistle is a VM. 01:14:23.000 --> 01:14:31.000 No, no, I'm saying, can you run it in a Windows VM? 01:14:31.000 --> 01:14:35.000 Maybe… 01:14:35.000 --> 01:14:36.000 I think he means a VM… Running Windows. 01:14:36.000 --> 01:14:39.000 Maybe. 01:14:39.000 --> 01:14:40.000 Yeah. In other words, I I don't have any hardware with windows on it. 01:14:40.000 --> 01:14:44.000 Yeah. Nope. 01:14:44.000 --> 01:14:47.000 No. 01:14:47.000 --> 01:14:56.000 and it'd be nice if I could take one of, you know, one of the Vms I've got. 01:14:56.000 --> 01:15:03.000 because the main issue is. There are very few containers that, in fact. 01:15:03.000 --> 01:15:07.000 Tyler, what what is the container world for windows? 01:15:07.000 --> 01:15:10.000 I've never looked at it. 01:15:10.000 --> 01:15:15.000 about like Minikube or like just Docker running in WSL? 01:15:15.000 --> 01:15:23.000 No, I'm saying are is there such a thing as a Docker container that'll run natively on windows? 01:15:23.000 --> 01:15:28.000 No, I think it all says install WSLN. 01:15:28.000 --> 01:15:35.000 Okay, that that's what I thought, because. You know, many, many years ago. 01:15:35.000 --> 01:15:41.000 One of my clients wanted… to go to a SQL server. 01:15:41.000 --> 01:15:47.000 And unfortunately, since they run Microsoft, it had to be Microsoft SQL Server. 01:15:47.000 --> 01:15:57.000 and I found the SQL Server container, which is the you know, stripped down version. You don't have. I guess it's equivalent of express. It's free. 01:15:57.000 --> 01:16:07.000 So I dropped a SQL Server container on the Linux server, and everybody in the office uses it for their application. 01:16:07.000 --> 01:16:18.000 Yeah, about 10 years ago I did a couple presentations on it. 01:16:18.000 --> 01:16:25.000 Some other features, smart TVs are terror are terrible. 01:16:25.000 --> 01:16:31.000 constantly phone home, send telemetry, generate massive DNS traffic. 01:16:31.000 --> 01:16:38.000 That's one of the reasons I I hate the fact that I bought a Samsung or Jim or. 01:16:38.000 --> 01:16:44.000 Joey bought me a Samsung. Six years ago. Biden. 01:16:44.000 --> 01:16:51.000 That's where I spent my COVID check on. Oh! 01:16:51.000 --> 01:16:56.000 Why are you plugging your TV into the internet? 01:16:56.000 --> 01:16:59.000 Because sometimes you need it. 01:16:59.000 --> 01:17:12.000 Go buy Android box and plug that in at least it knows if you don't like it, you'll yank it off and tell it to. 01:17:12.000 --> 01:17:16.000 Pitch it in the trash. 01:17:16.000 --> 01:17:20.000 Hmm. 01:17:20.000 --> 01:17:46.000 Oh. Yeah, Windows telemetry. You saw all of the Microsoft cruft and the query query log here. 01:17:46.000 --> 01:17:54.000 All right. which I mentioned whitelist. You know, there is a whitelist here for. 01:17:54.000 --> 01:18:00.000 domains. You can add anything you want. 01:18:00.000 --> 01:18:15.000 Add to blacklist or add to whitelist. 01:18:15.000 --> 01:18:21.000 Security considerations. You never want to expose a pie hole publicly. 01:18:21.000 --> 01:18:28.000 You want to add in password on it, update the containers, backup persistent volumes. 01:18:28.000 --> 01:18:34.000 Remember, we were talking about persistent volumes. Those are the 2 directories here. 01:18:34.000 --> 01:18:41.000 Etsy DNSmask.d, and etc pi hole. That's what you want to back up. 01:18:41.000 --> 01:18:45.000 When we talk about. persistent volumes. 01:18:45.000 --> 01:18:50.000 Makes sense. 01:18:50.000 --> 01:18:54.000 And why are you backing him up? 01:18:54.000 --> 01:18:59.000 If you want to be able to recover the pie hole. 01:18:59.000 --> 01:19:00.000 In other words, after you've used it for 4 or 5 years, you may have. 01:19:00.000 --> 01:19:04.000 Okay. 01:19:04.000 --> 01:19:12.000 a big whitelist of domains and configuration information, etc. 01:19:12.000 --> 01:19:20.000 If you… Back up those persistent volumes. 01:19:20.000 --> 01:19:26.000 that we talked about before. Remember, these are the 2 physical volumes on the host. 01:19:26.000 --> 01:19:37.000 that the container uses to store its configuration information that would survive a restart. 01:19:37.000 --> 01:19:39.000 Okay, thank you. 01:19:39.000 --> 01:19:49.000 Did that work for you, Stan? you know. Remember, containers are static. 01:19:49.000 --> 01:19:54.000 You cannot change a container. You could add to it when it's running. 01:19:54.000 --> 01:20:01.000 But as soon as you stop it and restart it, whatever you've added is is is gone. 01:20:01.000 --> 01:20:05.000 you know, because what what you're adding to running container is ephemeral. 01:20:05.000 --> 01:20:15.000 Now, there are ways to save it. One of those ways to persist the information from one instance to the next, or from one boot to the next. 01:20:15.000 --> 01:20:22.000 is to save it in a directory that's actually on the host instead of in the container. 01:20:22.000 --> 01:20:29.000 You know, these these directories are not part of the container file system. 01:20:29.000 --> 01:20:35.000 So that when you restart the container, it knows to look for these 2 directories on the host. 01:20:35.000 --> 01:20:45.000 and adds them into the container. And let's see… where can I continue? Right here. 01:20:45.000 --> 01:20:50.000 you know, they are right here. This is physically in the container. 01:20:50.000 --> 01:20:55.000 And those two directories are mine mounted here into the container. 01:20:55.000 --> 01:21:05.000 whenever the container boots because they are configured here. 01:21:05.000 --> 01:21:14.000 in the Docker compose. 01:21:14.000 --> 01:21:24.000 Okay. Okay. cleared his mind right man still catching. 01:21:24.000 --> 01:21:30.000 got me in the right direction. 01:21:30.000 --> 01:21:39.000 All right. If you want to play around all kinds of different stuff you can do. 01:21:39.000 --> 01:21:44.000 I'm going to be doing some Kubernetes stuff here later on, because. 01:21:44.000 --> 01:21:53.000 I got two different projects. One of them is a full AI implementation, the other is a Raspberry Pi implementation that runs Kubernetes. 01:21:53.000 --> 01:21:59.000 Podman is a little bit different manager than Docker. 01:21:59.000 --> 01:22:05.000 I can't tell you the difference between them. Podman basically came from red hat doctor. 01:22:05.000 --> 01:22:12.000 You know, they did their… did their own thing, but it has some advantages over Docker. But again, it's. 01:22:12.000 --> 01:22:23.000 Not totally in the public domain, the way I understand it. 01:22:23.000 --> 01:22:29.000 All right. If you run containers, obviously, you can run more than one, two, three, four, whatever you need. 01:22:29.000 --> 01:22:38.000 Each one I'm going to have a different IP, so you can have… 2, 3, 4 Dns servers as pie holes on your network. 01:22:38.000 --> 01:22:47.000 with one host. 01:22:47.000 --> 01:22:57.000 alternative blocking, extracns. All right. Lessons we've learned. 01:22:57.000 --> 01:23:03.000 DNS is critical infrastructure. You don't have to take my word for it. 01:23:03.000 --> 01:23:11.000 point point any system at a DNS server that is down, and you're not going anywhere. 01:23:11.000 --> 01:23:20.000 The flip side of that is kiss rules. Keep it so keep it simple. 01:23:20.000 --> 01:23:25.000 Visibility changes everything. Here we're talking about the fact that. 01:23:25.000 --> 01:23:30.000 If those ad blockers can see you, in other words, if you're visible to them. 01:23:30.000 --> 01:23:40.000 then you're tracking information, and any information that is gathered as you pass through sites on the internet. 01:23:40.000 --> 01:23:45.000 can be collected and sold. 01:23:45.000 --> 01:23:49.000 The bottom line here, can doing it in a container. 01:23:49.000 --> 01:24:02.000 makes the deployment trivial. Assuming you have a Linux host or run it in Windows system for Linux. 01:24:02.000 --> 01:24:09.000 Final thought, if you don't control a DNS, you don't control your network. 01:24:09.000 --> 01:24:14.000 All right. Questions. 01:24:14.000 --> 01:24:20.000 This is Stan. Say you got cousin Willie and he's got a Windows machine. 01:24:20.000 --> 01:24:38.000 And you've got him running things like, uh… unit… Origin or privacy badger and stuff like that. What's the advantage over a pie hole, and how much do you have to do to get him to use a pie hole? 01:24:38.000 --> 01:24:52.000 And just, you know, and he… You know, can you just have him buy a pie machine and install it on there and he's got to buy a cable to make a sort of a network to it? 01:24:52.000 --> 01:24:59.000 No, what what in that case, what I would recommend is buy yourself a pie and a case. 01:24:59.000 --> 01:25:09.000 burn a chip, put it in there, set the IPs for his network, send them the Pi, a cable, and his power… and a power supply. 01:25:09.000 --> 01:25:18.000 and then remote into his machine, or walk him through changing his DNS server to the IP on the Pi. 01:25:18.000 --> 01:25:26.000 And that… and for him, what's the real advantage of pie hole over. 01:25:26.000 --> 01:25:35.000 The other stuff these installed. In a nutshell. 01:25:35.000 --> 01:25:38.000 Compared to Privacy Badger and uBlock Origin and things like that. 01:25:38.000 --> 01:25:47.000 So… With uBlock and Privacy Browser, you're limited to just the browser. 01:25:47.000 --> 01:25:52.000 If anything else on the computer goes to look something up. 01:25:52.000 --> 01:25:57.000 You block origin… Brave privacy brat. 01:25:57.000 --> 01:26:02.000 The Privacy Badger. can't get in the way. 01:26:02.000 --> 01:26:09.000 By setting the… By putting the block at the DNS layer. 01:26:09.000 --> 01:26:29.000 So, when it tries to go look up known bad domain, he… then it doesn't matter what it is. It's the DNS server that it's talking to it. If the network is set up properly, it's the only DNS server it can talk to. 01:26:29.000 --> 01:26:33.000 I think basically you block origin does a great job. 01:26:33.000 --> 01:26:34.000 But only on the browser that it's installed with. 01:26:34.000 --> 01:26:39.000 Edinburgh. 01:26:39.000 --> 01:26:44.000 So if you hook up your cell phone to the. 01:26:44.000 --> 01:26:58.000 to the same network, uh… then you're not going to have the protection that you block origin is bringing to say Firefox. So that's the beauty of the pie hole is it protects everything that goes through the network. 01:26:58.000 --> 01:27:00.000 If I understand it correctly. 01:27:00.000 --> 01:27:06.000 Yeah, that's true. In fact, normally what you would do. 01:27:06.000 --> 01:27:12.000 is build your Raspberry Pi, send it to send it to Norm, or not not Norm, or Stan's. 01:27:12.000 --> 01:27:13.000 Billy. Cousin Willie. 01:27:13.000 --> 01:27:22.000 Willie? And then walk him through logging into his router. 01:27:22.000 --> 01:27:33.000 Go into DHCP. and set the DNS server for DHCP to the IP address of the pie hole. 01:27:33.000 --> 01:27:42.000 And that way everybody on the network that gets a DHCP address would have the pi hole as the Dns server. 01:27:42.000 --> 01:27:56.000 for every device on the network. including your smart TV, your phones, your Wi-Fi, etc. 01:27:56.000 --> 01:27:57.000 Thank you. 01:27:57.000 --> 01:28:05.000 Certainly. 01:28:05.000 --> 01:28:09.000 All right. Anybody else? 01:28:09.000 --> 01:28:12.000 I was just going to add comment to Stan. 01:28:12.000 --> 01:28:17.000 If you decide to do that, just remember your cousin Willie. 01:28:17.000 --> 01:28:22.000 Whenever his computer will not get onto the internet, for whatever reason. 01:28:22.000 --> 01:28:23.000 You hear me calling you? 01:28:23.000 --> 01:28:29.000 They'll be calling you. 01:28:29.000 --> 01:28:32.000 Who else is he gonna call, right? Right. 01:28:32.000 --> 01:28:33.000 That's right. 01:28:33.000 --> 01:28:37.000 He probably does that anyway. 01:28:37.000 --> 01:28:49.000 So Gary, you want to put a book in on here and then we continue on with Q&A and discussion or why do I get the feeling that Phil has a cousin, Willie? 01:28:49.000 --> 01:28:58.000 I always like to to let the rain recording going. Sometimes we get some good good. 01:28:58.000 --> 01:29:03.000 Good question. I mean, if anybody has any questions specific to tonight's topic, by all means, ask them now. But. 01:29:03.000 --> 01:29:16.000 Every farmer. Audre Whitaker Jr. Had lost her mind by the next morning. 01:29:16.000 --> 01:29:17.000 And sorry about that. I think somebody might's mic was open. 01:29:17.000 --> 01:29:25.000 Dave again. That was Steve. 01:29:25.000 --> 01:29:30.000 Oh, you got them, Ken? Okay. Alrighty. 01:29:30.000 --> 01:29:38.000 So so yeah, definitely everybody go ahead and ask questions or make comments about tonight's material and. 01:29:38.000 --> 01:29:42.000 If you don't hear anybody else talking about tonight, feel free to. 01:29:42.000 --> 01:29:48.000 Make comments or ask questions about other. things in the world of. 01:29:48.000 --> 01:29:51.000 open standards. Okay. 01:29:51.000 --> 01:29:57.000 on our discuss mailing list? Is that what you're saying? 01:29:57.000 --> 01:30:05.000 of of. Sure, go ahead and chat about it. Go ahead. Go with it, Sam. 01:30:05.000 --> 01:30:10.000 I'm asking, I missed that a blurb where I missed something you said. Sorry! 01:30:10.000 --> 01:30:17.000 Oh, I just said that if you don't have to keep your question specific to tonight's topic. 01:30:17.000 --> 01:30:26.000 If people don't have anything specific to what Lee was just talking about, you can go ahead and broaden it out to general Q&A. 01:30:26.000 --> 01:30:33.000 I was just going to make a comment. Um, on my desktop. 01:30:33.000 --> 01:30:42.000 I run L Ubuntu and. Yeah, yeah, I know it's not as good as Susilee. 01:30:42.000 --> 01:30:51.000 And I run Brave Browser, and I've never bothered to set anything up on Braze, I just, you know, out of the box, turn it on. 01:30:51.000 --> 01:30:54.000 And I don't get the ads. They're just not there. 01:30:54.000 --> 01:30:55.000 That's brave browsers basically set up with uBlock origin slash. 01:30:55.000 --> 01:31:01.000 No. I'm sorry? 01:31:01.000 --> 01:31:03.000 A brave browser? is set up by default with some of the best ad blocking tech in there. 01:31:03.000 --> 01:31:09.000 Yes, sir. 01:31:09.000 --> 01:31:10.000 built in. You actually have to go turn it off. 01:31:10.000 --> 01:31:13.000 Yeah. Yeah. What? Well, okay. 01:31:13.000 --> 01:31:16.000 I believe it's under the brave shields. 01:31:16.000 --> 01:31:27.000 Yeah, I have turned it off for a couple of websites, you know, but… I have noticed that if I run Brave on my phone. 01:31:27.000 --> 01:31:33.000 Oh, God. I mean, I've just given up using a browser on my phone. It's pointless. 01:31:33.000 --> 01:31:34.000 You know. 01:31:34.000 --> 01:31:46.000 I think that… I think that's because the application stores, like the Android store and the Apple Store won't let things that have ad blockers through, basically. That's my understanding. 01:31:46.000 --> 01:31:47.000 Well, that could very well be. 01:31:47.000 --> 01:31:48.000 But if you let ad walkers through the Apple Store, the Android store won't let you on. 01:31:48.000 --> 01:31:53.000 Yeah. 01:31:53.000 --> 01:31:54.000 Hmm. 01:31:54.000 --> 01:32:02.000 Well, I have hang on, I can tell you for certain that when I install Firefox on my phone, the first thing I do is go out there and get you block and no script. 01:32:02.000 --> 01:32:14.000 and all my standard extensions. Because they don't come on the browser for on the from the Google Play Store, but you can install them. 01:32:14.000 --> 01:32:23.000 Well, I wonder about the Brave browser there. Could it be that they've taken them out, or could they just have it turned off, Tyler? 01:32:23.000 --> 01:32:29.000 It could be that they're just turned off, but it's very possible that, you know. 01:32:29.000 --> 01:32:33.000 To put it bluntly, Google's not a search engine company. 01:32:33.000 --> 01:32:34.000 Not at work. 01:32:34.000 --> 01:32:41.000 Our ad company. Google is an ad company with a whole bunch of expensive hobbies. 01:32:41.000 --> 01:32:42.000 Oh, yeah, no question about it. 01:32:42.000 --> 01:32:54.000 So… so them using allowing through their. store a product that blocks their main method of making money? 01:32:54.000 --> 01:32:59.000 is… 01:32:59.000 --> 01:33:02.000 How should I put it? Counterproductive. 01:33:02.000 --> 01:33:05.000 Stupid? 01:33:05.000 --> 01:33:07.000 Shooting themselves in the foot. 01:33:07.000 --> 01:33:09.000 Yeah, I understand. And from your viewpoint, but I don't give a rat… about their viewpoint. 01:33:09.000 --> 01:33:16.000 You're not going to press your boss. 01:33:16.000 --> 01:33:29.000 But I wonder… I'll check with ChatGPT and see if it's possible to turn some of that stuff back on. 01:33:29.000 --> 01:33:30.000 I misunderstood you, Steve. I thought you were saying that. 01:33:30.000 --> 01:33:33.000 possible. Um… 01:33:33.000 --> 01:33:38.000 When you ran Brave on your phone. the. 01:33:38.000 --> 01:33:44.000 It was so tightened down that you don't get any response. 01:33:44.000 --> 01:33:50.000 No, um, websites and things come up, but the amount of ads you get. 01:33:50.000 --> 01:33:56.000 And of course, the thing jumps to Facebook once every 5 or 10 minutes. 01:33:56.000 --> 01:33:57.000 That's not right. 01:33:57.000 --> 01:34:00.000 And I love Facebook software. 01:34:00.000 --> 01:34:05.000 That's not right. It sounds like you got something on your phone. 01:34:05.000 --> 01:34:07.000 Well, that could be. It's an Android. It's an Android. 01:34:07.000 --> 01:34:12.000 Using Android or, uh, iOS? 01:34:12.000 --> 01:34:17.000 It's a Samsung Galaxy 15, maybe? Does that make sense? 01:34:17.000 --> 01:34:22.000 I got a lot of volume. You might try mole browser. 01:34:22.000 --> 01:34:30.000 And it comes with uBlock Origin already built in. Get it F droid. 01:34:30.000 --> 01:34:37.000 dot com or .org f droid. dot com. 01:34:37.000 --> 01:34:39.000 It's called the Mull Browser. No ads. Nothing. 01:34:39.000 --> 01:34:45.000 Interesting. Yeah, I mean… When I run Brave on my desktop, it just… it's, you know, the world is quiet. 01:34:45.000 --> 01:34:51.000 Yeah, I hate. 01:34:51.000 --> 01:34:54.000 Yeah, but… 01:34:54.000 --> 01:34:55.000 Oh, what? 01:34:55.000 --> 01:35:05.000 Or is if the person on the website says, this is our sponsor today, and, you know, they'll go on for minutes, but… you know, I know who that is, and I can fast forward through it. 01:35:05.000 --> 01:35:08.000 Or listen to them. Whatever. 01:35:08.000 --> 01:35:17.000 Steve, before you do anything, go into your Brave settings and shield and make sure block ads and trackers is set to aggressive. 01:35:17.000 --> 01:35:27.000 Okay. I'll have to figure out how to… I don't necessarily know how to do that on this postage stamp phone. 01:35:27.000 --> 01:35:28.000 Oh, it's got to be hamburger on there somewhere. 01:35:28.000 --> 01:35:34.000 Screen. Well, you would think. 01:35:34.000 --> 01:35:39.000 There isn't. There isn't Firefox on the top right. 01:35:39.000 --> 01:35:49.000 Yeah, here's a couple of dots. 01:35:49.000 --> 01:35:51.000 Settings… Brave Shields, let's see what happens there. 01:35:51.000 --> 01:35:58.000 Okay. 01:35:58.000 --> 01:35:59.000 Shields and privacy. 01:35:59.000 --> 01:36:13.000 It's Firefox, but that's who. Yeah. Firefox on Firefox. There's 4 vertical dots in the top right, and that takes you to settings and the rest of the rest of what you need. 01:36:13.000 --> 01:36:14.000 Well, the thing… 01:36:14.000 --> 01:36:22.000 On my Android, it's on the bottom right, there's a… The three dots in settings, and it's right there at the very beginning. 01:36:22.000 --> 01:36:26.000 have the brave shields. 01:36:26.000 --> 01:36:35.000 Yeah, I found the Brave Shields… What is auto-redirect AMP pages? 01:36:35.000 --> 01:36:36.000 Don't move. 01:36:36.000 --> 01:36:44.000 AMP is Google's attempt at bandwidth saving. When 2G and 3G were the norm. 01:36:44.000 --> 01:36:59.000 So, instead of getting the actual page from… The website, the… Uh, the Android… Uh, browser would go out and ask Google to retrieve the page, and then. 01:36:59.000 --> 01:37:05.000 Dumb it down to reduce bandwidth. Utilization. 01:37:05.000 --> 01:37:09.000 Hmm. 01:37:09.000 --> 01:37:11.000 So. 01:37:11.000 --> 01:37:22.000 Well, I turned a bunch of stuff off here. Let's see what happens. 01:37:22.000 --> 01:37:31.000 Yeah. It also would help if I could spell. 01:37:31.000 --> 01:37:32.000 That's what that sixth grade teacher was telling me. 01:37:32.000 --> 01:37:34.000 Yeah, that would help. 01:37:34.000 --> 01:37:44.000 Does anybody have any experience with specific block lists that they like? 01:37:44.000 --> 01:37:47.000 Are we all just not doing this? 01:37:47.000 --> 01:37:55.000 Yep, here we go. YouTube, and the first thing I see is some doctor selling some goddamn… stuff. 01:37:55.000 --> 01:38:02.000 Oh yeah. Are you in the Brave browser or did it kick over to YouTube itself? 01:38:02.000 --> 01:38:07.000 Well, I started the Brave browser, and then I went to YouTube. 01:38:07.000 --> 01:38:16.000 Right, but sometimes the browser understands that you may have a… 01:38:16.000 --> 01:38:21.000 native app for it, and it boots up that… 01:38:21.000 --> 01:38:38.000 No, I don't think I have that. 01:38:38.000 --> 01:38:46.000 I'll play with it. Sometime. 01:38:46.000 --> 01:38:56.000 But, Tyler, your point is well taken. But if I actually want to do some browsing, I will generally. 01:38:56.000 --> 01:39:05.000 go to my desktop computer. I much prefer a big screen anyway. 01:39:05.000 --> 01:39:15.000 Yeah, that's where I do 90% of my stuff unless it's… my audiobooks and that runs on my phone because I'm buying them through Audible. 01:39:15.000 --> 01:39:21.000 Yeah, I've got, uh, I've got, um… books I read on my phone. 01:39:21.000 --> 01:39:29.000 But, you know, they don't… they don't use… they don't use a browser at all. I mean, I download them from Amazon and. 01:39:29.000 --> 01:39:32.000 done, they work offline. 01:39:32.000 --> 01:39:35.000 Until Amazon says no but you know that's that's the only with Amazon publishing. 01:39:35.000 --> 01:39:46.000 Pardon? Yeah. No, that works great. 01:39:46.000 --> 01:39:53.000 So, Lee, what are you using to run… containers and Kubernetes. 01:39:53.000 --> 01:39:57.000 Uh, rancher. 01:39:57.000 --> 01:40:07.000 I'm working trying to get through Talos OS. I got it running on four mini PCs tied together. 01:40:07.000 --> 01:40:08.000 Okay. 01:40:08.000 --> 01:40:16.000 Um, the list of devices it's supposed to run on include this. 01:40:16.000 --> 01:40:31.000 SBC called a orange pie. It actually has a, uh… On the back it has a… NVMe slot, but I can't get the damn thing to boot to that. 01:40:31.000 --> 01:40:33.000 Something's not updated, right? 01:40:33.000 --> 01:40:40.000 Yeah, sorry. Actually, my cluster is. 01:40:40.000 --> 01:40:48.000 L. 34 51 small form factors with a 6 core Xeon in a 3 and a half gigahertz. 01:40:48.000 --> 01:40:59.000 And I got… I got 3 of them, so that gives me 36 cores, and… 256 gate. 01:40:59.000 --> 01:41:00.000 Don't say that out loud. Somebody might come and raid you. 01:41:00.000 --> 01:41:05.000 terabyte of memory. 01:41:05.000 --> 01:41:18.000 It's not like I have 128GB sitting in the Dell 720 back there that runs all my disks. 01:41:18.000 --> 01:41:22.000 Yeah, when I… winter. 01:41:22.000 --> 01:41:44.000 I don't know exactly what model they are, but the IBM Think Centers. I got them because they actually have a PCIe slot that you can get an adapter card to put a… low form factor… PCIe card. Can't put the the standard riser on it, but if you take that. 01:41:44.000 --> 01:41:53.000 that off you can at least get it plugged in and then you know… GM something non-conductive in there to keep it from coming out of the slot. 01:41:53.000 --> 01:41:54.000 The biggest problem I keep on running into is that. 01:41:54.000 --> 01:41:56.000 Yeah. 01:41:56.000 --> 01:42:10.000 couple of my loads I need GPUs for and um… When the OS is a API, things get squirrely. 01:42:10.000 --> 01:42:16.000 Let's see if I can actually go pop up. 01:42:16.000 --> 01:42:29.000 Now that button. 01:42:29.000 --> 01:42:32.000 A sad question, Lee. I've heard you say in the past you've collected thousands of. 01:42:32.000 --> 01:42:37.000 Yeah. 01:42:37.000 --> 01:42:44.000 bad sites and so forth. Did you pass that collection into the Raspberry Pi, or the Pi Hole? 01:42:44.000 --> 01:42:48.000 No, that's that that that's on our mail servers. 01:42:48.000 --> 01:42:52.000 like 170,000 at this point. Plus, they got a list of about 50 class C's. 01:42:52.000 --> 01:42:57.000 And what? 01:42:57.000 --> 01:43:01.000 If I see if I see more than 4. 01:43:01.000 --> 01:43:06.000 Ips in a single class CI block or whole class C is the provider doing their due diligence. 01:43:06.000 --> 01:43:12.000 And… And where are you blocking that in the host file, or what? 01:43:12.000 --> 01:43:15.000 No, in the access file for postfix. 01:43:15.000 --> 01:43:20.000 Oh, okay. That was my question. Thank you. 01:43:20.000 --> 01:43:23.000 Sure. 01:43:23.000 --> 01:43:25.000 Over. 01:43:25.000 --> 01:43:34.000 Yeah, Lee, I was going to mention that when you were talking earlier about having that incompatible Wi-Fi chip in that laptop. 01:43:34.000 --> 01:43:39.000 There's a guy over on Github. I put it in the chat. 01:43:39.000 --> 01:43:42.000 And he has a list of a whole bunch of USB sticks. 01:43:42.000 --> 01:43:47.000 That their firmware or whatever has been submitted and is. 01:43:47.000 --> 01:43:57.000 currently in the kernel. So, you know, in other words, if you buy one with that chipset or whatever, it should just run with no problem, you know, on Linux. 01:43:57.000 --> 01:43:59.000 Yeah. No. And there's a lot of them out there. But the problem is sometimes a vendor goes cheap. 01:43:59.000 --> 01:44:04.000 Yeah. 01:44:04.000 --> 01:44:12.000 and they want to save 10 bucks on the hardware, and they use one of the stupid windows only. 01:44:12.000 --> 01:44:16.000 hardware devices like the Wi-Fi chip in my laptop. 01:44:16.000 --> 01:44:28.000 that can't run under Linux, because there's no code in the chip that gets to ask it and has to download on every boot from the driver. 01:44:28.000 --> 01:44:33.000 Yeah, well, these are… I thought of having one of those, or whatever. 01:44:33.000 --> 01:44:41.000 hanging around just as like an emergency backup. Somebody brings a machine over and you're wanting to try to either put Linux on it or. 01:44:41.000 --> 01:44:42.000 Ah, okay, yeah, I I I see where you're going. Yeah, that that's a good point. 01:44:42.000 --> 01:44:55.000 Just see if it works. You know… Yeah, and the other thing, too, is even though he's talking about USB sticks, he does talk about the chipsets in them. 01:44:55.000 --> 01:45:03.000 And, you know, if the chips are in the kernel, and it's conceivable that they could come up with a you know, many Pcie. 01:45:03.000 --> 01:45:07.000 card for a laptop, also. 01:45:07.000 --> 01:45:12.000 Yeah. Okay. 01:45:12.000 --> 01:45:18.000 Yeah, I I just threw my, uh… access list. 01:45:18.000 --> 01:45:31.000 I don't know how many lines we got here, but this is all the class C that I've collected over the last few years. 01:45:31.000 --> 01:45:40.000 and you do a WC on it. 01:45:40.000 --> 01:45:47.000 In Vim, you just do a shift or control gene, it would take you to the bottom and then you'd see the count. 01:45:47.000 --> 01:45:50.000 Yeah, but I got blank… I got blank lines in there. 01:45:50.000 --> 01:46:02.000 Oh, oh, oh. 01:46:02.000 --> 01:46:08.000 580. What's the 71 and 88 Phil? Do you remember? 01:46:08.000 --> 01:46:18.000 I think 71 is the number of lines. I think 88 might be either the number of words, maybe? 01:46:18.000 --> 01:46:24.000 or 1180 might be the number. Well, I think 1180 is the number of characters, maybe. 01:46:24.000 --> 01:46:34.000 Yeah. So I… and see. 01:46:34.000 --> 01:46:44.000 It's line 24. 67 lines. So yeah, it's probably about 35. 01:46:44.000 --> 01:46:51.000 Or probably 30. Yeah, because some of them are blocked contiguous blocks. 01:46:51.000 --> 01:46:57.000 like the like. Yeah. 01:46:57.000 --> 01:46:59.000 That's the whole domains, this slash 24. 01:46:59.000 --> 01:47:02.000 Yeah, sure, they're all flash 24s. 01:47:02.000 --> 01:47:10.000 Yeah. And like I say, my role is, if I see 4 Ips in a Class C, I block the whole class C. 01:47:10.000 --> 01:47:30.000 Because that means the provider doesn't give a damn. 01:47:30.000 --> 01:47:38.000 God bless you. 01:47:38.000 --> 01:47:46.000 Okay, well, people are thinking of other questions apropos to tonight's talk. I'm going to drift off to a different. 01:47:46.000 --> 01:47:51.000 area or different topic. Android. Oh. 01:47:51.000 --> 01:48:02.000 I just added some. micro SD into an Android, and that freed up space and moved moved the. 01:48:02.000 --> 01:48:08.000 application files over to this to the micro SD. 01:48:08.000 --> 01:48:20.000 Pardon me. Turn that off. Um… But the I now have the option of utilizing the original internal. 01:48:20.000 --> 01:48:24.000 Memory on the chip or on the phone, 64 gig. 01:48:24.000 --> 01:48:32.000 Uh, and I could… take some of that memory and apply it to being used. 01:48:32.000 --> 01:48:39.000 As memory for the operating system. So it suggests 1, 2, or 3 gigabytes. 01:48:39.000 --> 01:48:46.000 My first thought is, it's great. If I do that, then I need to get some of that internal memory back on the. 01:48:46.000 --> 01:48:53.000 phone itself, how difficult is it to get back that three gigabytes of memory that I've now allocated to the OS? 01:48:53.000 --> 01:48:54.000 When you say memory, do you mean RAM or storage? 01:48:54.000 --> 01:48:59.000 Is it true? Ram. 01:48:59.000 --> 01:49:05.000 Well, on a cell phone, yeah, it's like… What it's offering is now that I have moved. 01:49:05.000 --> 01:49:13.000 moved some of the application stuff off. The internal storage. 01:49:13.000 --> 01:49:22.000 It's offering to use that internal storage as as RAM for the OS. 01:49:22.000 --> 01:49:27.000 allowed some of it to be used. It's suggesting 1, 2, or 3 gigabytes. 01:49:27.000 --> 01:49:33.000 Huh. with the promise that it'll improve the speed. 01:49:33.000 --> 01:49:37.000 I don't believe you. 01:49:37.000 --> 01:49:42.000 No, you mean you don't believe the phone. And I'm sure Gary, you know, it doesn't have a clue. 01:49:42.000 --> 01:49:51.000 I don't believe it. 01:49:51.000 --> 01:49:56.000 I mean, you know, my my first guess would be. Okay, fine. If you. 01:49:56.000 --> 01:50:05.000 If you. go into the settings after you've done that, let's say I give it 3 gigabytes of what used to be. 01:50:05.000 --> 01:50:11.000 internal storage, turn that over to to be used as. 01:50:11.000 --> 01:50:18.000 as RAM for the for the OS. I should be able to go back into the settings, I would think. 01:50:18.000 --> 01:50:27.000 and reclaim one, two or three of those gigabytes, I probably would have to power cycle the phone. 01:50:27.000 --> 01:50:31.000 Shut it down, and when it would come back up it would. 01:50:31.000 --> 01:50:40.000 It would realize it can't use that for internal store or for, uh… Ram or anyone. 01:50:40.000 --> 01:50:54.000 Okay, nobody's got the experience. going to be doing more research. It was something I just stumbled on this afternoon, so haven't had a chance to research it yet. 01:50:54.000 --> 01:50:55.000 Hmm. 01:50:55.000 --> 01:50:59.000 Like I said, I don't believe you. 01:50:59.000 --> 01:51:03.000 Thank the guy at the phone store lied to you. 01:51:03.000 --> 01:51:19.000 It wasn't even a human. It was a smart-ass phone all on its own, suggested it. 01:51:19.000 --> 01:51:20.000 Yeah, I'm not sure. 01:51:20.000 --> 01:51:27.000 In case anybody's interested, I put the link that alternative2.net. 01:51:27.000 --> 01:51:35.000 About Pyle tells a different, uh… was out there, like, AdGuard. I think that's relatively popular. 01:51:35.000 --> 01:51:51.000 And then, uh, I think I showed Tyler's one Tyler uses in there, too. 01:51:51.000 --> 01:51:57.000 I understand that last part. He said, what about Tyler uses that too? 01:51:57.000 --> 01:52:04.000 Uh, I think he's using a tech medium. DNS server? 01:52:04.000 --> 01:52:11.000 Is that right, Tyler? 01:52:11.000 --> 01:52:16.000 I thought he said something about that earlier. 01:52:16.000 --> 01:52:21.000 guessing Tyler must have stepped away from his box for a moment. He's still logged in, but. 01:52:21.000 --> 01:52:25.000 Yeah, I think he didn't realize he's muted. 01:52:25.000 --> 01:52:30.000 Somebody keeps on muting me stop that! 01:52:30.000 --> 01:52:43.000 I'm about 42… 01:52:43.000 --> 01:52:57.000 Yeah, I'm working with Technetium because it's… where pie hole comes from the… The position of I want to block stuff and then I tack on it. 01:52:57.000 --> 01:53:05.000 DNS on to that technician is… technitium looks like it's more of, I need a DNS server. 01:53:05.000 --> 01:53:11.000 full-blown DNS server that I can configure via web and is… Not aurora pain. 01:53:11.000 --> 01:53:41.000 Now I'm going to attack ad blocking onto that. 01:54:16.000 --> 01:54:24.000 I actually had an interesting conversation. Monday afternoon with some guys from Boeing. 01:54:24.000 --> 01:54:35.000 Um… Do you guys use to check and make sure that your certificates are getting renewed? 01:54:35.000 --> 01:54:45.000 Were you got any of you guys actually do that? 01:54:45.000 --> 01:54:54.000 When the box stopped working, they didn't get renewed. 01:54:54.000 --> 01:54:59.000 all we all I use around here is let's encrypt search, and that's automated. 01:54:59.000 --> 01:55:10.000 Right. So none of you actually have something watching that certificate and making sure it never gets or never expires? 01:55:10.000 --> 01:55:15.000 Well, the I watched the certificate with an Agios check to make sure it's still good. 01:55:15.000 --> 01:55:20.000 And then there's a cron job that runs. I don't know if it was daily or weekly. 01:55:20.000 --> 01:55:29.000 that if it's over 60, if you get. If you hit 60 days, it renews it. 01:55:29.000 --> 01:55:42.000 Lars. to jump ship their Boeing and apply to… what they call… Network integration engineer. 01:55:42.000 --> 01:55:53.000 But it was really… the job is to manage… Sounds like an enterprise version of… Unify. 01:55:53.000 --> 01:55:59.000 pushes out policies and patches to routers and switches within the network. 01:55:59.000 --> 01:56:00.000 Hmm. 01:56:00.000 --> 01:56:08.000 They had a guy retire and since I'm looking to jump ship off of Siemens, because… I gave them a year. 01:56:08.000 --> 01:56:11.000 They haven't talked to me at all about where. 01:56:11.000 --> 01:56:17.000 I'm going personally. 01:56:17.000 --> 01:56:24.000 And I started throwing… resumes are boring because they had that. 01:56:24.000 --> 01:56:31.000 new fighter jet that they're building down by. The Saint Louis airport. 01:56:31.000 --> 01:56:34.000 No, I think they're doing the trainer over there. 01:56:34.000 --> 01:56:41.000 All the trainers over there too. I've thrown my resume at… I've literally had. 01:56:41.000 --> 01:57:00.000 The resume version of the money gun pointed at every job that says Python in it, and I'm like… And you're going, will any of you respond? 01:57:00.000 --> 01:57:03.000 I think you should zoom right now. 01:57:03.000 --> 01:57:10.000 But these guys finally did, and I'm like… Sounds simpler than the identity management. 01:57:10.000 --> 01:57:17.000 platform that I just or I currently manage that's supposed to die. 01:57:17.000 --> 01:57:29.000 management ever gets around to actually, you know. spending money… 01:57:29.000 --> 01:57:34.000 Watch your language. 01:57:34.000 --> 01:57:41.000 They actually asked me what was my greatest weakness? I'm like Epic downtime. 01:57:41.000 --> 01:57:46.000 I literally just can't get over shutting down a system to cause pain. 01:57:46.000 --> 01:57:52.000 Because the person who wants to write the check is an. 01:57:52.000 --> 01:58:18.000 In better terms than that, but… 01:58:18.000 --> 01:58:21.000 Ready to shut her down 01:58:21.000 --> 01:58:27.000 Well, questions and comments seem to be slowing down. 01:58:27.000 --> 01:58:28.000 For those who 01:58:28.000 --> 01:58:30.000 applied lately 01:58:30.000 --> 01:58:35.000 What's the general accepted, I'm annoying you about a job 01:58:35.000 --> 01:58:38.000 Right, that you guys usually do 01:58:38.000 --> 01:58:42.000 Once a week, twice a week 01:58:42.000 --> 01:58:46.000 Say it again, I didn't follow you. 01:58:46.000 --> 01:58:47.000 How often 01:58:47.000 --> 01:58:50.000 Have you gotten any response back from the company yet, or 01:58:50.000 --> 01:58:54.000 You just sent in the resume and they haven't sent you anything back 01:58:54.000 --> 01:58:57.000 A lot of them, it's just I've applied 01:58:57.000 --> 01:58:59.000 Some of these 01:58:59.000 --> 01:59:04.000 Well, these last two, I've actually interviewed once or twice 01:59:04.000 --> 01:59:06.000 One, I got rejected 01:59:06.000 --> 01:59:11.000 I was in the 70 percentile range of the map match, because 01:59:11.000 --> 01:59:15.000 I don't have a credit card to 01:59:15.000 --> 01:59:18.000 have a$ 12,000 01:59:18.000 --> 01:59:21.000 fine hit against about 01:59:21.000 --> 01:59:30.000 from Amazon for because an AI thought my website was tasty 01:59:30.000 --> 01:59:31.000 I don't understand that 01:59:31.000 --> 01:59:40.000 I didn't understand that either. I'm sorry. 01:59:40.000 --> 01:59:47.000 the… there was a guy that woke up the other day, says, I put a$ 10 limit on my Google 01:59:47.000 --> 01:59:49.000 Infrastructure 01:59:49.000 --> 01:59:52.000 Woke up one day 01:59:52.000 --> 01:59:59.000 Google had charged him$ 12,000 because an AI looked at his website that looks neat 01:59:59.000 --> 02:00:00.000 It started 02:00:00.000 --> 02:00:11.000 banging away at it 02:00:11.000 --> 02:00:15.000 I half understand that 02:00:15.000 --> 02:00:16.000 And why did that become a$ 12,000 charge? 02:00:16.000 --> 02:00:35.000 As the AI generated so much traffic, it turned into$ 12,000. 02:00:35.000 --> 02:00:36.000 Oh 02:00:36.000 --> 02:00:40.000 Google did not shut down the service when when the charge hit the$ 1$ 10 it kept let it kept running and let the AI continue to munch on his website 02:00:40.000 --> 02:00:41.000 Okay. 02:00:41.000 --> 02:00:42.000 I'm like 02:00:42.000 --> 02:00:44.000 I have this nice little firewall over here 02:00:44.000 --> 02:00:49.000 And when AI decides it wants to bang on my door, I go 02:00:49.000 --> 02:00:52.000 No, go away 02:00:52.000 --> 02:00:57.000 And there's nothing for for the 02:00:57.000 --> 02:01:01.000 Amazon or AWS to charge to 02:01:01.000 --> 02:01:04.000 So, when the people say, do you have experience running 02:01:04.000 --> 02:01:06.000 on AWS, I'm sitting here going 02:01:06.000 --> 02:01:08.000 I've been going through the training 02:01:08.000 --> 02:01:26.000 Work hasn't given me an account 02:01:26.000 --> 02:01:30.000 Okay. 02:01:30.000 --> 02:01:32.000 Well, how about a bookend, Gary 02:01:32.000 --> 02:01:35.000 Yeah, I think 02:01:35.000 --> 02:01:42.000 Unless somebody has a last minute objection, we're going to turn off the recording and start shutting down. 02:01:42.000 --> 02:01:53.000 But thank you all very, very much for being here this evening. Good questions, good observations. Thank you to Lee for putting together an excellent presentation on 02:01:53.000 --> 02:01:56.000 Subject we need to learn something about. 02:01:56.000 --> 02:01:58.000 And thank you, Lee, for 02:01:58.000 --> 02:02:05.000 or stretching it a little to make up for grants and ability to be here due to his work emergency 02:02:05.000 --> 02:02:11.000 And thank you all for putting up with me being a little wordy to also stretch time a little bit at the beginning. 02:02:11.000 --> 02:02:12.000 So 02:02:12.000 --> 02:02:14.000 Anyway 02:02:14.000 --> 02:02:31.000 By the way, for those of you, I'll put this as part of the bookend for those of you who were looking for the tutorial, the base on the front of this recording. There was none tonight because the presenter, Grant 02:02:31.000 --> 02:02:40.000 Got a called at work for an emergency, and so he wasn't available to do the base tutorial at the beginning of this. 02:02:40.000 --> 02:02:56.000 This was Wednesday, the 13th of May, 2026. It's the monthly general meeting of SLU, the Saint Louis Unix User Group. And our main speaker tonight, our only speaker tonight was Lee Lam 02:02:56.000 --> 02:03:04.000 Omni tech and Lee was talking to us about 02:03:04.000 --> 02:03:14.000 Well, pihole use of pie hole to capture all those annoying ads and stop 02:03:14.000 --> 02:03:18.000 Stop those things be at us. It shouldn't be having. 02:03:18.000 --> 02:03:20.000 Thank you very much, all. 02:03:20.000 --> 02:03:32.000 And we will see you hopefully next Thursday. Stay tuned and watch the website, and we'll see what the topic will be for next Thursday, the St. Louis location. Good night. 02:03:32.000 --> 02:03:33.000 Thank you all 02:03:33.000 --> 02:03:38.000 Good night.