@bonifartius @phnt @slashb

> i don't really see what's the use of a connected networked device but without the right settings to actually work?

"Working" is not reasonably defined as "publicly routeable" because "I want to be able to communicate between these two systems" is a very different proposition from "I want this system exposed to the public".

When the next Mirai-level botnet occurs, all of the people that said "Pfff, NAT isn't a security feature, you should configure your router properly" are still going to blame the routers. ISPs hate for you to run your own router anyway, they try to avoid letting you do that kind fo thing, so "configure your router" means "hack this shitty cheap thing that Comcast misconfigured". And the internet will be nuked and shat on and they'll still be insisting that there's no reason to ever be cautious about a transition between two fundamentally different states.

And, you know, I shouldn't take the bait. I should just post the links to https://tailscale.com/blog/two-internets-both-flakey/ and https://apenwarr.ca/log/20170810 and be done with it.
network_security_architecture--backdoors.jpg