When computer networks were first starting out, many design decisions were made. Which, in hindsight, were flawed. One example is the lack of security features. Many early protocols, such as HTTP, Telnet, and FTP, assume that all network traffic is legitimate, sent by good actors, and transmitted by trustworthy intermediaries. This later required the addition of secure alternative protocols such as HTTPS, SSH, and FTPS. While this has taken a lot of work to resolve and deploy to servers and clients, it’s not the biggest misstep from the early internet.
IPv4 or the Internet Protocol version 4 is the addressing structure used for computer networks and to communicate over the internet. It has a structure that allows for a maximum of 4,294,967,296 addresses. While 4.3 billion IP addresses may sound like a lot, that is less than one per human being currently alive. Most people in western countries, at least, have more than one internet-connected device each.
Clearly, IPv4 address space is an issue. Unfortunately, in the internet’s early days, this issue was exacerbated by assigning out vast ranges of IP addresses to organisations that could never use them. This practice was adjusted twice, once with the introduction of the classful addressing system. Later with the introduction of the CIDR or Classless Inter-Domain Routing system. Both of these solutions helped to stave off address space exhaustion.
Another key feature was the private address space. This allocated a few address blocks to be used for internal networks that could not be routed to the larger internet. This allows every Local Area Network or LAN to share the same address space, massively reducing the address space pressure.
NAT
The problem with using a private addressing scheme for internal networks is that you can’t directly communicate with the internet. Any packet you transmit from your local network will have your private IP address. No one else will know which network to send the response back to.
To get around this issue, NAT or Network Address Translation was designed. NAT allows a device, typically the edge router, to edit all network traffic. This sounds sketchy, but the only part that it can change is the source and destination IP address and port number. The router then keeps a table tracking all connections and address translations allowing it to identify relevant responses and redirect them to the appropriate device.
Note: Technically, NAT can also edit the checksum of a packet. The important thing is it can’t edit the actual data, just the addressing.
NAT can be configured one-to-one, giving each device its public IP. NAT is, however, generally deployed in a many-to-one topology where the entire network shares one public IP address. This technically involves the use of the related PAT or Port Address Translation. As you might guess this refers to translating and keeping track of port numbers, again by the router. While it’s technically more correct to specify that you mean both NAT and PAT. NAT is generally assumed to be both, as almost all deployments of NAT use both NAT and PAT.
How Does NAT Actually Work?
Let’s consider an example home network. It has a few devices on it as well as the router. The router is issued a public IP address by the ISP. A computer in the network then wants to load a Technipages article. The computer sends its request via the router with its private IP address. The router then changes the source address in the network packet, to be the public IP address and an unused port number. Critically, the router keeps track of this translation.
A little later, the router receives the reply from Technipages to the same port number. It then checks its translation table to determine which local device to forward the traffic to. Suppose the router finds a match in the translation table. In that case, it then replaces the destination IP address and port in the packet with the computer’s original IP and port number.
There are three main advantages here. First, devices on a privately addressed network can communicate with the public internet. Secondly, NAT acts as a sort of firewall, any unexpected communication into the network, doesn’t map to an entry in the translation table and is simply dropped. Finally, all this happens transparently to the user. They don’t need to know it even happens.
There are some issues, though. For example, if you have a server that you want other people from the internet to be able to access, this isn’t possible with just NAT. There is a solution to this, however, called port forwarding.
https://docs.microsoft.com/en-
https://make.wordpress.org/
http://www.emro.who.int/
https://make.wordpress.org/
https://community.godaddy.com/
https://www.mysql.com/cn/
https://official-blog-tw.line.
https://squareup.com/us/en/
https://www.iubenda.com/blog/
https://www.xing.com/
https://newsroom.pinterest.
https://woocommerce.com/
https://www.intuit.com/blog/
https://lists.w3.org/Archives/
https://about.usps.com/postal-
https://pear.php.net/manual/
https://pt.wix.com/blog/2016/
https://soundcloud.com/
https://docs.google.com/
https://www-archive.mozilla.
https://pages.ebay.com/cr/en-
https://www.snapchat.com/add/
https://www.dreamhost.com/
https://blogs.opera.com/india/
https://blog.developer.
https://drexel.edu/cci/
https://phabricator.wikimedia.
https://www.surveymonkey.com/
https://elections.
https://store.steampowered.
https://elearning.adobe.com/
https://www.dailymail.co.uk/
https://www.nsf.gov/pubs/2006/
https://en.wikipedia.org/wiki/
https://www.usenix.org/legacy/
https://dribbble.com/shots/
http://www.ks.uiuc.edu/
https://forums.cpanel.net/
https://www.bluehost.com/blog/
https://www.klarna.com/
https://www.ugr.es/~jfernand/
https://www-archive.mozilla.
https://icl.utk.edu/ctwatch/
https://zims-en.kiwix.
https://fr.wikipedia.org/wiki/
https://www.washingtonpost.
https://www.businessinsider.
https://ethnobiomed.
https://www.e-ir.info/2021/07/
https://www.scirp.org/html/3-
https://www.businessinsider.
https://en.wikipedia.org/wiki/
https://fi.wikipedia.org/wiki/
https://www.oecd.org/daf/
https://www.ftc.gov/news-
https://
https://uokik.gov.pl/
https://dev.
https://github.com/
https://bitcointalk.org/index.
https://www.sec.gov/enforce/
https://codemirror.net/3/doc/
https://www.crunchbase.com/
https://unpkg.com/xml-lite@0.
http://edition.cnn.com/2004/
https://www.netmums.com/
https://www.personneltoday.
http://www.pbs.org/wgbh/
https://foreignpolicy.com/
https://www.elegantthemes.com/
https://docs.google.com/forms/
https://forum.icann.org/lists/
https://bugs.mysql.com/bug.
https://bugs.php.net/bug.php?
https://coaches.xing.com/
https://evernote.com/blog/7-
https://blakesmalltalkblog.
https://people.com/human-
https://www.inquirer.com/
https://www.yahoo.com/
https://philly.eater.com/2016/
https://www.phillymag.com/
https://bugs.mysql.com/bug.
https://www.addthis.com/blog/
https://www.ics.uci.edu/~
http://blogs.harvard.edu/
https://listserv.acm.org/
https://blogs.lse.ac.uk/polis/
http://www.demtech.qmul.ac.uk/
https://www.vice.com/en/
http://www.slate.fr/story/
https://blog.patreon.com/
https://www.buzzsprout.com/
https://exclaim.ca/music/
https://www.thelineofbestfit.
https://ag.hyperxgaming.com/
https://www.stitcher.com/show/
https://www.spreaker.com/user/
https://www.livechat.com/
https://livechat-success.
https://www.thedrum.com/news/
https://www.gnu.org/software/
https://directory.fsf.org/
https://www.popsci.com/story/
https://www.popsugar.com/
https://toptohigh.com/why-the-
https://getpocket.com/explore/
https://www.popsugar.co.uk/
https://www.privacyshield.gov/
https://www.export.gov/apex/
http://s263974156.websitehome.
https://news.sky.com/story/
https://democracy.wirral.gov.
https://www.kunstundjustiz.
https://digg.com/2017/hiv-
https://mosaicscience.com/
https://goodmenproject.com/
https://science.thewire.in/
https://churchleaders.com/
https://vimeo.com/15023300
https://go.indiegogo.com/blog/
https://zims-en.kiwix.
https://www.ece.rutgers.edu/~
https://www.cyber.t.u-tokyo.
https://staff.aist.go.jp/t.
http://pbl.cc.gatech.edu/ael/
https://www.lsi.usp.br/~
http://www.hvrl.ics.keio.ac.
https://mmt.inf.tu-dresden.de/
https://www.cs.drexel.edu/~
https://www.riec.tohoku.ac.jp/
https://www.evl.uic.edu/
https://lists.w3.org/Archives/
https://contently.com/2012/05/
https://www.govloop.com/
https://www.mdpi.com/1996-
https://us1.campaign-archive.
https://geospatial.blogs.com/
https://www.eoportal.org/
https://www.ogc.org/pressroom/
