Re:IPv6 is no longer considered optional
by vidarh on Thursday April 26, 2012 @08:07AM
(#3893456)
Beyond a lack of public IP's, it's the obstructive nature of it that makes it (sort of) useful.
It's not really any safer than starting with a firewall where everything is denied by default and opening port by port of inbound traffic.
But NAT'ing every internal address forces you into a pattern where the external IP is not tied to where the service is hosted at all - you need to explicitly map that in your firewall -, and where if you were to, say, accidentally turn off all your filtering, you leave yourself isolated instead of exposed.
I don't think these are important enough to care about NAT once we switch to IPv6 - you can certainly be just as defensive through other means.
It's not really any safer than starting with a firewall where everything is denied by default and opening port by port of inbound traffic.
But NAT'ing every internal address forces you into a pattern where the external IP is not tied to where the service is hosted at all - you need to explicitly map that in your firewall -, and where if you were to, say, accidentally turn off all your filtering, you leave yourself isolated instead of exposed.
I don't think these are important enough to care about NAT once we switch to IPv6 - you can certainly be just as defensive through other means.