You can't even remember what you said on page 2 by the time you got to page 3, and it's in writing for you.Then you claimed you just didn't give a toss what the content of your posts were, (as you explain how intelligent and educated you are). Then you claim that this convo isn't about NAT security, but rather about NAT security, relating to cryptographic backdoors. My sources were all bunk, but now they back you up.
NATs can't be hacked from the outside... Sure, sure. Whatever you say Jonny I won't hold you back from your very important job anymore.
Still haven't gave any evidence to prove me wrong. I never said your sources were wrong, just over explaining a simple fact.
Dude, I know you think this statement is making you look knowledgeable, but all I see is you've had 4 jobs in 7 years.
Without any background as to why you quit running your hosting company or why you worked at 3 different ISPs, all this tells us is you have trouble holding a job.
If you behave at work like you have in this thread then I can see why you've changed jobs so much.
It gives my statements more weight because its knowledge I use on a daily basis in my profession. The first two jobs were temporary contracts on which I moved away from my place of study during summer. Those places of work were interested in keeping me on after my place of study, which is something I have to think about. The position I'm currently at now is my year placement in which I was offered a permanent place in my position with a pay rise. I'll be returning back to study but working part-time at my current position, which is a first for the company. I've also received 2 pay rises and 2 substantial bonuses in 6 months for the money I've saved them.
If you've worked in IT and engineering places, you'd realise there's plenty of temporary contract positions and contractors. Here we see a mostly new engineering department every 6 months.
Well from my experience, running a hosting company was something anyone could do a few years ago. leaving him with 3 real jobs probably in a lot less than 7 years, and those jobs could be anything, based on age and experience probably support...
On that note, everyone in this thread is wrong and correct though...but everyone is to stubborn to change
When I did hosting, it was a free hosting service. The hosting company was something very small to begin with but it gained a lot of credit and I ended up selling it on for quite a nice fee when I couldn't give enough time to pursue it. When I finished with it, it was spread across 3 dedicated servers in which I owned at 16. This experience gave me a lot to talk about during interviews and a lot to go with.
I even created my own client management system dedicated for free-hosting which is still used widely to this day across the free hosting market.
http://thehostingtool.com. I launched that website in 2008 when I was 16.
Sorry for being a professional giving my own experience to add to a discussion regarding something quite sensitive. I love how I have to defend myself on some information regarding NAT which is quite frankly, simple knowledge. The integrity of my whole past comes into question by some bafoon who knows how to put "NAT Attacks" in google to get his source. Yes, its the first result on the page. Yet someone who has rolled out two CG-NAT implementations nationally in the UK for ISP's, implemented a new traffic management system and looked at IPv6 deployment for all customers doesn't know what they're talking about.
I'm going to put it in the easiest simplest statement possible.
When your home gateway receives a packet which hasn't had an outbound packet from your LAN, it drops it. This is due to the fact that when your client sends a packet, your router stores the information of who and what type of information it sent. When it receives a reply back, your router knows which computer to send the packet to because its remembered the information from when your machine sent it out. Without that information, it hasn't got a clue where to send it, so it drops it. The only technical way for your router to get round that is by broadcasting the reply it receives to the whole LAN. This is a huge security risk and a traffic hogger, hence why its not done and its not specified in the RFC.
If you ran a minecraft server and you wanted people to connect to it and your behind a NAT, you have to port forward. This means when your gateway ever receives minecraft traffic, it always sends it to that machine you specified in the port-forward. Its the EXACT same principle.
That is basic NAT knowledge, its very simple CCNA NAT information.