News for hackers. Stuff that matters.
Re:The State of NAT Traversal by userbinator on Tuesday August 26, 2014 @06:07PM (#8229861)
The difference is in the isolation factor: there is absolutely NO way a packet with an internal IP can get anywhere on the public Internet, and likewise a packet with a public IP will never be accepted by a device that has been configured with an internal one. The failure modes are different - although firewalls can be configured to provide an "outgoing connections only" default like NAT, they are also software and thus not immune to bugs; a buggy firewall letting packets through which shouldn't be is far worse than a buggy NAT.
Re:The State of NAT Traversal by oasisbob on Tuesday August 26, 2014 @06:52PM (#8230020)
there is absolutely NO way a packet with an internal IP can get anywhere on the public Internet

That very much depends on your definition of "public internet."

My service provider doesn't properly filter RFC1918 space at their border. From my home on the west coast, I can hit 10.0.0.0/8 devices on the east coast in a separate AS.

Is a reachable printer web interface 3000 miles away in New York on the public internet? The "Internet" is a very tough entity to define succinctly, but I'd argue yes.

Re:The State of NAT Traversal by graylights on Tuesday August 26, 2014 @10:04PM (#8230568)
Why would you need to filter an internal IP as a destination IP, routing should handle that.

I understand filtering the source address as internal IP because that could be malicious spoofing of internal host (and destination can't legitimately reply.)