KCLUG

kclug@kclug.org

3297 discussions

Re: List on Black List
by Chris Bier 21 Feb '26

21 Feb '26

MXtoolbox says we're off all the lists now. Let me know if anyone is still having issues. On Fri, Feb 20, 2026, at 21:51, Chris Bier wrote: > Should be good now. > > On Fri, Feb 20, 2026, at 13:20, Jonathan Hutchins wrote: >> >>> On 02/20/2026 1:05 PM CST Chris Bier <cymorc(a)gmail.com> wrote: >>> >>> Looks like we've recently been put on a black list. I've requested we be removed, but Comcast seems to be blocking us right now. >>> >>> Chris >> Perhaps something to do with the 10,000 probing hits per day maybe? >> -- >> Jonathan

2 1

Website Repo
by Chris Bier 21 Feb '26

21 Feb '26

Hi All, We have an Org and Repo for the current version of the website on codeberg.org that will update the site automatically. If anyone is interested in joining the Org there or building an alternate version of the site (Static Site Generators or other), let me know and I can add you. https://codeberg.org/KCLUG Chris

1 0

List on Black List
by Chris Bier 20 Feb '26

20 Feb '26

Hi All, Looks like we've recently been put on a black list. I've requested we be removed, but Comcast seems to be blocking us right now. Chris

2 1

Hello + domain advice
by vaughan.schmidt＠gmail.com 20 Feb '26

20 Feb '26

Hi, new KCLUG list member here. I signed up after the KCLUG got a shout out on Garmin's Linux Users Slack channel earlier in the week. Anyways: I saw the recent discussion on hosting, and a couple of the comments about single points of failure / 1 contact person made me think to chime in here: Make sure you folks have a good handle on who owns the domain itself, and ideally find a way to mitigate single point of failure there. I've been a member of UCLUG (Upstate Carolina LUG, Greenville SC) for probably 20 years, but have been remote since I moved out of state ~11 years ago. Looks like UCLUG domain name itself just got poached and lost when it was not promptly renewed. I haven't kept up with the very latest, but a lot of the original old guard in that UCLUG have become less active as they've entered retirement, shifted focus, whatever. Aomewhere along the line, the ball got dropped. I did check whois for kclug, and it looks like it is right in the middle of a renewal. Registrant is hidden, but hopefully its one of you. Cheers, and hope to make it to a meeting at some point, -Vaughan

3 2

RE: Hello + domain advice
by Chris Bier 20 Feb '26

20 Feb '26

Welcome, Vaughan! Thanks for the reminder! We've currently got 3 people that have access to the DNS provider and renew when it comes up. Yeah, once it's gone, it's rare to get it back. We've actually got kclug.org, kclug.com, and kclug.net, but haven't really used the .net and .com. Chris On Fri, Feb 20, 2026, at 08:53, vaughan.schmidt(a)gmail.com wrote: Hi, new KCLUG list member here. I signed up after the KCLUG got a shout out on Garmin's Linux Users Slack channel earlier in the week. Anyways: I saw the recent discussion on hosting, and a couple of the comments about single points of failure / 1 contact person made me think to chime in here: Make sure you folks have a good handle on who owns the domain itself, and ideally find a way to mitigate single point of failure there. I've been a member of UCLUG (Upstate Carolina LUG, Greenville SC) for probably 20 years, but have been remote since I moved out of state ~11 years ago. Looks like UCLUG domain name itself just got poached and lost when it was not promptly renewed. I haven't kept up with the very latest, but a lot of the original old guard in that UCLUG have become less active as they've entered retirement, shifted focus, whatever. Aomewhere along the line, the ball got dropped. I did check whois for kclug, and it looks like it is right in the middle of a renewal. Registrant is hidden, but hopefully its one of you. Cheers, and hope to make it to a meeting at some point, -Vaughan *___**___**___**___**___**___**___**___**___**___**___**___**___**___**___*__ KCLUG mailing list -- kclug(a)kclug.org To unsubscribe send an email to kclug-leave(a)kclug.org https://kclug.org/mailman3/postorius/lists/kclug.kclug.org/

1 0

what to do with a liftgrid mining rig?
by David Nicol 18 Feb '26

18 Feb '26

Liftgrid appears to have gone defunct. I've got one of their HNT mining apparatusses installed in my attic, still running as far as I know. Would any of the LoRa enthusiasts here like to take it over? I'm not entirely sure what "take it over" means. -- "Plot complication appearing on sensors now"

3 4

KCLUG hosting
by Jonathan Hutchins 18 Feb '26

18 Feb '26

We have several offers to host the static pages. That's not hard, any of us with a broadband connection could do it. That does leave us with a single point of failure if we lose the person providing it. The same goes with the system being as close to a box-stock Debian server - if the maintainer vanishes that's a lot easier for a new person to understand and recover. We do need the ability to send email via smtp, and that needs to come from a commercial, not residential address. There may also be an issue with the volume of malicious connection attempts, I don't know if that would be significant to a provider. It would also be nice to have a local provider, just to promote the concept of a Kansas City site/service. With that setup we could easily host a podcast with archives as well. -- Jonathan

6 11

Interest in a KCLUG Podcast?
by Chris Bier 06 Feb '26

06 Feb '26

Hi All, Would anyone be interested in creating a KCLUG podcast? We could have a recorded session at meetings and/or also take prerecorded sections. The primary focus would be Linux and FLOSS perspectives from KCLUG members. Chris

3 3

LiftGrid
by David Nicol 03 Feb '26

03 Feb '26

As LoRa was discussed at our recent meeting, the fact that I've got a Helium mining rig running in my attic has prioritized itself into my awareness now. It isn't clear that LiftGrid is still in business. Should I unplug it? -- "Plot complication appearing on sensors now"

1 0

Failed Connections
by Jonathan Hutchins 03 Feb '26

03 Feb '26

I posted the latest logwatch report to the list. I believe those pam login failures are sshd connection attempts. Currently we're running SSHD on port 222. That redirection is so well known now that we might as well run it on 22. I would suggest that we chose a more random, arbitrary port and see if that cuts back on the hits. -- Jonathan

4 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

KCLUG