Notices by warthog9 (warthog9@social.afront.org)

la la la, building up a new firewall for the new house, and I went:

"Hey! ISC DHCP is about as EOL as it gets, it's not in el10, lets migrate to kea like I properly should!"

mucks about, eventually gets 2578 lines of config sorted out, goes to try it

blinks

WAT

There's no way, that would be utterly silly. DNS should be the source of truth here, the want to move to dyn-dns updates and move to kea / dhcp being the source of truth is beyond ludicrous...

https://gitlab.isc.org/isc-projects/kea/-/issues/3617

aaaaand I guess ludicrous it is...

guess I'm backporting dhcp-server from Fedora into my epel10-missing-pieces because kea's nigh useless until that can get fixed

Ohhhh and in case anyone is curious about the firewall

Flagging this up, maybe someone does or knows someone who does: I am in search of a tool steel maker who can replicate some parts. Specifically Leatherman has stopped making the Style PS, and I have a tendency to burn through the little screwdrivers / nail file on them something fierce.

My stashed supply of them is getting low, and replacements are well into "hey I bet I can find someone to make me a pile of parts" territory. So here's my ask: if you are a steel tool worker, or know someone who does and are willing to take a look at an existing part and replicate it as close as possible, possibly with some modifications, hit me up.

Boosts welcome, I'm not sure where to search for this one!

@ryanc @ariadne @equinox not to be a downer, but teamd/libteam doesn't have anything to do with systemd other than systemd-networkd can configure teams.

@ariadne @ryanc @equinox teamd is basically deprecated and there's a push to go back to the in kernel only one last i saw.

Of course I had long ago migrated to teams for the better lacp support, so I've been staring at needing to migrate back...

@simon https://github.com/warthog9/mastodon-block-importer might be helpful (I'm the author) that and keeping an eye on the #FediAdmin and #FediBlock too

Ok, Vger's MX is heading off to point to subspace on Thursday. Web services are staying put for now, so if you link to / use Vger it's staying put (possibly with a massive OS upgrade coming).

The fundamental infrastructure isn't going anywhere even if it has to change it's name, and should lists not want to head off to subspace, infradead, etc I've got https://vger.email up and running and capable of picking things up should anyone want to jump.

End of an era, Vger's been independent of kernel.org from it's start, but it's a non-trivial set of lists that literally keep the Linux kernel community moving, and has since it's inception. It's realistically needed an upgrade to deal with a plethora of problems, and frankly various large e-mail providers have made it nearly untenable to keep doing without it nearly being a full time job (at least at the scale that Vger's at)

Well, vger (as of right now) no longer directly attempts to deliver to gmail/google/googlemail just to get the ridiculous backlog out of the primary mail paths. Vger (1 machine) is kicking all of that queue over to 8 other machines and letting them go try to get that delivered and queue up somewhere where it's not going to cause everyone else pain.

This should, at least for now, settle out several things, but if you are seeing mail wonkiness give postmaster@ a ping and I'll take a look.

Also if you are on Gmail and doing kernel dev, might be worth looking at other email providers.

@jann vger is a particularly busy set of mailing lists, on a daily basis it will send literally millions of emails to individual addresses. Gmail has a lot of users, and thus we send a lot of email their way. Due to our volume, and our need for somewhat agressive retries, we can trip over the bulk sender limits very quickly. This then causes a cycle of more delivery attempts, because they've pushed back on accepting delivery, and our continuing incoming mail.

Recently the back log queue has exceeded 20K messages, noting that is messages not message + delivery email address so it's easily millions of messages + individual emails they weren't accepting.

All of this would be workable if there was a means to reach out, but that's particularly hard and slow with them. So yeah there's thousands of gmail users I can absolutely confirm haven't been getting vger related traffic because of the push backs and there's little from the vger end we can do about it.

Yeah, Gmail is not a great e-mail provider, speaking as someone who doesn't use Gmail and is dealing with an absolutely ridiculous mess trying to get Gmail to actually accept e-mail from not Gmail.

Also if you are subscribed to Vger lists, and use Gmail, please take your lack of getting e-mail up with Gmail because I'm doing what I can to get it through, but they are actively blocking it right now.