News for hackers. Stuff that matters.
Re:IPv6 privacy addresses crashed the MIT CSAIL network by fulafel on Sunday September 07, 2014 @08:38AM (#8280957)
IPv4 specs forbid NAT. VPN and firewalling are also counter to the spirit of IP, if not the letter.

The internet was designed for end-to-end and works much better if you go along the grain on that.

Re:IPv6 privacy addresses crashed the MIT CSAIL network by ghshephard on Sunday September 07, 2014 @10:49AM (#8281272)
The specs may forbid NAT, but lots of companies are using it with IPv6 in exactly the same way they did with IPv4.

Not everyone wants to expose their internal IPv6 address space to the outside world.

Re:IPv6 privacy addresses crashed the MIT CSAIL network by sp332 on Sunday September 07, 2014 @09:52AM (#8281123)
I'm assuming you mean IPv6? :)
Re:IPv6 privacy addresses crashed the MIT CSAIL network by fulafel on Sunday September 07, 2014 @02:12PM (#8281905)
Nope, IPv4. (You'll have even less sympathy from me complaining IPv6 NAT is painful to set up...)
Re:IPv6 privacy addresses crashed the MIT CSAIL network by sp332 on Sunday September 07, 2014 @03:54PM (#8282183)
Sorry, how does IPv4 ban NAT? Most NAT in the wild is running on IPv4.
Re:IPv6 privacy addresses crashed the MIT CSAIL network by fulafel on Sunday September 07, 2014 @11:24PM (#8283313)
Router Requirements RFC says thou shall only forward packets unmolested.