Correct, once all the routing is done and your Core team already sees all the networks in your structure, then you can eliminate the NAT from all the routers, only the Core team or the one that performs load balancing should have NAT rules created.

However, the decision to remove or maintain NAT (Network Address Translation) rules on each node's routers while using static or dynamic routing depends on your network architecture and the specific connectivity and security goals you seek. reach.

Let's look at how both static and dynamic routing affect the need for NAT on a network:

Static Routing

Static routing refers to the practice of manually adding routes to a router's routing table. These routes are fixed and do not change unless they are manually modified or deleted.

Static routing is simple and predictable, but can be difficult to manage in large or rapidly changing networks.

• With NAT: In many networks, NAT is used at the edge, especially on routers connected directly to the Internet, to translate between public IP addresses and private IPs used internally. This allows multiple devices to share a single public IP address.
• No NAT: It is possible to remove NAT in certain scenarios, such as in an internal network where all devices use unique, globally routable IP addresses, or when routing between VLANs within an organization. However, for Internet access, NAT is generally maintained on the edge device.

Dynamic Routing

Dynamic routing uses protocols such as OSPF, EIGRP, or BGP to allow routers to automate the route discovery process and adapt to changes in the network in real time.

• With NAT: As with static routing, in environments where internal networks use private IP addresses and need to access the Internet, NAT is required on the edge device to translate these addresses to one or more public IP addresses.
• No NAT: In networks where routable public IP addresses are used on all devices or in closed networks (such as an intranet) where external access is not required, NAT could be removed on internal routers. For networks employing IPv6, where the address space allows each device to have a unique global address, the use of NAT may be less common.

Considerations

• Security: NAT provides a level of isolation between your internal network and the outside world, which can be beneficial from a security perspective.
• Network simplification: On some networks, especially those that do not require direct external access to internal devices, removing NAT can simplify configuration and diagnosis of network problems.
• Application Requirements: Some applications and services may work better without NAT due to the need for end-to-end connectivity without address translation.

In conclusion, whether you can remove NAT from the routers on each node will depend on your specific network configuration and application requirements.

In many cases, NAT is required on the edge router to allow Internet access from an internal network that uses private IP addresses, while on internal networks or in environments with routable public IP addresses, NAT may not be necessary.