I learned a bit about it in CCNA training but I've forgotten most of it.
I remember that it had to do with creating a map of IP addresses for an entire network, all under the same sub-address.
How did this post make you feel?
Find answers, share answers, discuss.
How did this post make you feel?
How did this post make you feel?
kaiuk wrote:I'm not sure what the Cisco answer would be, I'm sure it is something extremely in depth and technical so I'm just going to describe a real world application for it. On a typical local area network you will get a live public IP address from the ISP, but you don't want your local client machines to be exposed to the big bad internet (directly).Ah yes I think I remember learning about this. About the difference between public and private IP addresses. I think originally they only had IPs with no public or private aspect. The only problem is that there weren't enough. You can't possibly give every single device on the planet its own IP address. The best thing to do is give each network its own IP and then give the individual devices their own private IPs within the system. The most common of these being 192.168.1.(something).
You firewall will have the public IP and then it will 'translate' the local IPs on the client machines to give them internet access. All the clients can see the internet, but the internet can only see 1 public IP - your firewall, not the client machines.
How did this post make you feel?
How did this post make you feel?
KenBrace wrote:I think it also depends on the country and ISP.kaiuk wrote:I'm not sure what the Cisco answer would be, I'm sure it is something extremely in depth and technical so I'm just going to describe a real world application for it. On a typical local area network you will get a live public IP address from the ISP, but you don't want your local client machines to be exposed to the big bad internet (directly).Ah yes I think I remember learning about this. About the difference between public and private IP addresses. I think originally they only had IPs with no public or private aspect. The only problem is that there weren't enough. You can't possibly give every single device on the planet its own IP address. The best thing to do is give each network its own IP and then give the individual devices their own private IPs within the system. The most common of these being 192.168.1.(something).
You firewall will have the public IP and then it will 'translate' the local IPs on the client machines to give them internet access. All the clients can see the internet, but the internet can only see 1 public IP - your firewall, not the client machines.
How did this post make you feel?
kylerlittle wrote:I think it also depends on the country and ISP.No. NAT or Network Address Translation uses table to store WAN and LAN side (wide and local area network). Why is that usefull? So we reduce number of taken IP addresses. Instead having unique (wide) IP address on each device, you have unique IP for whole network. IPv4 is limited to 2^32 (4294967296) addresses and we wouldn't use NAT, we would ran out of those addresses much faster. On February 3rd 2011 we ran out of unassigned IPv4 addresses, now we are using IPv6, which has 2^128 addresses :)
How did this post make you feel?
How did this post make you feel?
How did this post make you feel?
Ok, so the next instalment......... I loaded the Grand…
Apologies I do not have an answer but could you please …
Sign up for VIP membership