09-28-2024
10:43 PM
- last edited on
09-29-2024
12:44 AM
by
rupeshah
Hi ! student here preparing for the CCST networking exam . ( First post )
NAT is also a great tool to use when an organization
changes its Internet service provider (ISP), but the networking manager needs to avoid the
hassle of changing the internal address scheme.
I read the text above in Todd lammle's book . the question i have here is why would you need to renumber internal IP address scheme in pre NAT systems since private and public IP address ranges are different and they do not overlap ?
Solved! Go to Solution.
09-29-2024 04:35 AM
Possiblity two things that remark has in mind, if you are using public ISP IPs, beyond one just for private to public, if you change ISPs all of them would need to change. For example your company hosts its own public web and mail servers. If such servers were also behind NAT, moving to a different ISPs would not require changing their host IPs. (Unclear how this would be a huge advantage, as you would still need to deal with the change to their public NATted IPs.)
The second situation I'm unsure about. Assuming all your IPs are public IPs and you have your own AS, there may be an issue if you move between global IP address block assignment regions. I.e. what if you move from England to Australia, can you use your public IPs and AS?
09-29-2024 04:05 AM
we are not sure what document you reviewing there are many document and trainer all over.
the question i have here is why would you need to renumber internal IP address scheme in pre NAT systems since private and public IP address ranges are different and they do not overlap ?
High level we do NAT since RFC 1918 address not routable to Internet, so we do NAT using Public IP address.
You can learn more information as below :
https://www.cisco.com/c/en/us/products/routers/network-address-translation.html#~q-a
suggest to post in learning community so can be address correctly :
09-29-2024 04:35 AM
Possiblity two things that remark has in mind, if you are using public ISP IPs, beyond one just for private to public, if you change ISPs all of them would need to change. For example your company hosts its own public web and mail servers. If such servers were also behind NAT, moving to a different ISPs would not require changing their host IPs. (Unclear how this would be a huge advantage, as you would still need to deal with the change to their public NATted IPs.)
The second situation I'm unsure about. Assuming all your IPs are public IPs and you have your own AS, there may be an issue if you move between global IP address block assignment regions. I.e. what if you move from England to Australia, can you use your public IPs and AS?
09-29-2024 04:39 AM - edited 09-29-2024 04:41 AM
Sticking to your question. This situation happens, for example, when your company buy another company and they need to integrade their network, using some ISP service, and for coincidence they use the same internal network range. On this case a NAT between them is necessary.
Antoher situation is when you hire a new ISP but they will not give you a public IP address. There might be different cases where you need NAT in order to avoid renumber internal networks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide