@GossiTheDog I am pretty convinced at this point that the biggest reason for instability in so-called production networks is because of the enterprises' addiction to professional software solutions with support contracts.

If production environments were run with the software most of us techs would actually prefer to use, companies would save money and reliability would increase.

But businesses need that support contract, they need a phone number to call and yell at when shit goes down. Everything is a mystical black box, and IT professionals are basically just coordinating vendor support. No one knows how anything works anymore.

@darius If your solution does not include #IPv6, ... you are part of the problem.

Us network engineers have been trying to tell you for 25+ yeats now.

@darius JESUS MARY AND JOSEPH!

We do NOT need easier access to RESULTS.

We need better documentation to the constructs that deliver those results.

At a certain point, you have to start admitting that layers of extrapolation are counterproductive.

The Fediverse is already a tangled mess of RESTFUL calls.

nuintari's rules of networking 0x13:

Seriously.

NAT is not a firewall.
NAT is not kind of a firewall.
NAT is not like a firewall.
NAT is not sort of a firewall.
NAT is not a firewall.

There is a world of difference between explicitly denied traffic, and traffic dropped because the device just didn't know what to do with it.