Where should we put NAT Gateway ?


Recommended Posts

Are you still talking about AWS?  You really need to be clear when talking about AWS or Azures or any other sort of virtual/cloud networking setup vs physical networking.

 

A nat would sit between the network you want to nat, and some other network that your going to nat too.

 

Nat does not have to occur between rfc1918 and public.  But it makes little sense to nat between like network (rfc1918 to rfc1918 or public and public) But there are cases where you might have to do such a thing.  This happens quite a bit in say a production network where a new network is acquired an needs to talk to an existing network and these networks use address space that overlaps.  The better solution is to change the networks to all play nice in the same address space.  But this is not always possible (political reasons) or cost effective in work/production/enterprise environments.

 

Say you take on a new customer you support with connections into your datacenter and they use addresses in the 10/8 space and you have a bunch of different customers all using the same IP space.  While if looking at the big picture you would assign specific address space for each of the customers to change their networks too - this is not something they normally want to do, and quite often if a very large network can be cost prohibitive to change them.. It becomes easier, faster and cheaper to just NAT between their address space and yours.  So you end up with rfc1918 to rfc1918 nats.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.