malware has connected outwards to c&c servers for more than 20 years
It was indeed a shit-show. Adding a NATting router to those set-ups instantly increased their security tremendously. Sure you could use a proper firewall, but the router w/NAT Just Works.
The problem IPv6 seeks to address has mostly been engineered around for now.
For now is the operative phrase. These are band-aids to keep IPv4 running, but they won't be effective forever.
Neither do I, but that's a fixable situation. Get an appliance router that lets you put DD-WRT (or similar) on it. Or use a computer instead of an appliance and set it up any way you like.
I am not running a home router or dd-wrt. But I am not a typlical user going down to best buy to pick up the latest Belkin or Asus wireless AP / router combo they have on sale for $99 and hooking it up to my internet using default "wizard" settings from the mobile app...
Nor I am I trusting Comcast, or ATT to configure their residental rented equipment properly with proper firewall rules
My comment is not about me, I have enterprise grade nextgen firewalls that are $$
My comment is about Grandma that calls up comcast to have them set it all up, or Sally that is going into best buy for the "Geek Squad" so hook her up...
I'm only familiar with the largest ISPs in Britain, but they also have default-deny configurations on the IPv6 routers they supply. Obviously.
> Grandma / Sally
Try avoiding the casual ageism and sexism.
Try not to find offense in all things, feel free to refer to my comment thread from the other day about offense being a you problem not a me problem ;)
ipv6 most configuration end up with all devices publically routable and must have a firewall deny policy inplace to block inbound connection
Shodan is filled with people with misconfigured ipv4 routers that end up with all kinds of device that should not be on the public internet (webcams, printers etc) out there for anyone to connect to. This requires a user to actively do something on the device (most likely following a bad online tutorial) in order to port something though the NAT.
with IPv6 this problem will get FAR FAR FAR FAR worse.
No they're not. They're by default obscured, but anyone can guess your internal IP and send a packet for it, and the router will happily forward it on unless its firewalling tells it not to. And that's without even even getting into all the extra attack surface opened up by legitimate and not-so-legitimate workarounds for the issues NAT causes.
NAT is only kind of a firewall and there have been plenty of terrible router firmwares out there that have lead people to subvert it (UPNP being one of the most problematic).
If you in your other thread don't trust the ISP device, then don't trust NAT on your ISP device either. Quite often the ISP can have their modem route traffic from their internal 10 net to your internal network if they so choose to.
Instead IPv4, or IPv6 setup to drop NEW/SYN connections to your devices via a router that you provide.
There is no logic there. firewall configuration is much harder to secure than NAT configuration.
Disagree. Just the XML parsing logic required for uPnP alone is more complex than a basic firewall implementation.
While people may say "NAT is Not security", it is in fact a layer (ahd huge one) in the security onion, that ipV6 is likely going to increase drastically the amount of ransomware and other malware on the public internet simply because that NAT layer is gone