Notices by The Psychotic Network Ferret (nuintari@infosec.exchange), page 2

Am I reading this correctly? The #PaleMoon fork of #Firefox refuses to implement #DNS over #HTTPS

And a #FreeBSD port exists?!?!

MY PRAYERS HAVE BEEN FUCKING ANSWERED!

Fuck #DoH, and fuck every browser trying to make it the norm.

nuintari's rules of networking 0x02:

Static routes are bad and should be avoided wherever reasonably possible.

Static default routes should be burned from your network by all means necessary.

@tfiebig @s @azedand2knots SMTP is fundamentally pretty amazing. It was carrier/transport agnostic, could handle incredible delays, and was always accountable for its actions and failures.

And then the assholes arrived. Spammers, and war against them started. SMTP was never designed with any of this in mind. In the name of anti-spam, all of its benefits have eroded away and left us with the shitshow we have today.

It also created the opportunity for the current hegemony of providers to seize control. By the time most noticed, it was too late.

@kaia Basically, what I wish my phone looked like.

Work gave me a card as a way to say sorry about my dog. That was nice. I actually teared up a little.

@silverwizard @benhm3

yeah, at the MSP job I took before my current ISP gig, they were mystified and terrified by DNS. Multi-millions of dollars in monthly revenue, and I got mocked for even suggesting we turn up DNS. DNS was proclaimed as so fundamentally unreliable.

This place also mistrusted automation completely. And, if you mistrust automation, maybe working with computers isn't right for you.

God, that job sucked.

@benhm3 Where in this conversation did I mention that I blame other people for my shortcomings? The vast majority of my shortcomings are my own damn fault, and there are plenty of them. Since you have reiterated that you are a fan, I can surmise you are referring to things I have said outside of this conversation. I can admittedly, be pretty gorram vicious when my failures are due to the limitations of another.

But I digress. A significant reason the rules about DNS almost all end with, "DNS is not hard," is because I don't think the common refrain of, "It's always DNS," is particularly funny, nor is it helpful. It is a defeatist attitude that needs to go away.

People have been blaming the mystery service that is DNS for so long, that a large portion of IT now seems to believe that DNS is beyond their capabilities.

Glad you enjoy the rules.

@silverwizard I'm actually considering becoming the package maintainer for Mastodon::Client for FreeBSD.

That honestly seems less terrible than touching Linux.

@silverwizard Right? When I say try it, I mean NOW, not what was the result five minutes ago? Try it a-fucking-gain.

Good lord, 3rd part vendor's employee needs to VPN into my network.

He encountered one issue, which I corrected. Now he absolutely refuses to so much as try again, and just insists that it can't be made to work. He keeps blaming bad drivers and how he doesn't want to debug Juniper issues.

He won't even try. I fucking fixed the issue he had, and tested it with 16 hours of continuous use over two work days. IT FUCKING WORKS. He just refuses to try.

Why are people like this?

@silverwizard Well, fundamentally, all monitoring systems do this. They check and check and check, and go crazy when a check fails.

But don't tell your humans that everything is okay.

I agreed to help a local MSP out with some of their networking projects, as their network engineer is mourning the loss of his wife.

Its all child's play stuff to me. But, they added me to their alerts, and they have an..... everything is okay alarm. Literally, an email every 30 minutes telling me that nothing is currently broken.

I haven't signed any paperwork, I might just tell them I can't do this after all.

nuintari's rules of networking 0x10:

Learn to subnet, it isn't hard. Not everything needs to be a /24. RFC1918 space is finite.

I love how Linux networking is wildly different from distro to distro. And most distros have a new way and an old way, and sometimes an even older way that is still supported. And there are about a hundred thousand terribly written blog posts about how you can change networking in Linux, absolutely zero of which ever seem to match the distro, version, and state of reality you are in exactly.

Linux is a fucking dumpster fire, and I wish I never had to use it.

Edit: Oh that is cute, add a new network interface, old network interface settings are now GONE.

nuintari's rules of networking 0x2c:

Never scrounge a cable out of the trash. It's in there for a reason.

1st Corollary:

Always cut any cable you're throwing in the trash to prevent breaches of the aforementioned rule.

2nd Corollary:

If you replace ends on a trashed cable without also running it through a tester, you deserve any and all of the pain coming to you.

I really need to move my MX back to self hosted.... I keep saying it, and then something less annoying comes along.

I _could_ stand up postfix, and dovecot, and spamd, and clamav, and migrate all my data, and fight with IP reputation, and DKIM and SPF....

OR!

I could fold myself over and shit on my own face!

So far, I keep picking the less unpleasent path.

@silverwizard "You'll regret that!"

@Natureshadow Thank you for the suggestion, this is AWESOME. Took me about six minutes to spin up a VM and install this, it does everything I need so far!

nuintari's rules of networking 0x20:

Resources in an active/active pair are only a sufficient backup if each side is capable of carrying the full load independently.

@silverwizard Yeah, I should probably mention my desire to stay Linux free in the original post.

#FreeBSD is freedom!