This is an old revision of the document!
Table of Contents
Expensive
Technology
Why didn't stone age people invent this, were they stupid?
Artificial Intelligence
Juice Jacking
It's a Layer 8 Problem
Internet
IP Address
Malware
Antimalware Software
Escape Character
Information Technology/Networking/
IP Address
While IP addresses aren't necessarily connected to the internet, much of what you are about to read might make more sense to you if you read about the internet first: See Internet (>click<).
An IP (Internet Protocol) address is a numerical identifier assigned to a network interface, allowing it to be identified and communicate with other devices over an IP network.
Any device that wants to communicate with other devices over an IP network (such as LAN, WLAN or even WAN) needs an appropriately configured IP address. This can be your phone, your Laptop, PC, console, your printer, perhaps your smart lights or smart fridge. However, even servers on the internet, serving websites (like this one!) or otherwise, use IP addresses to communicate. While you may be used to opening websites in your browser by entering a domain (such as ultracomfy.net), this domain really just resolves to an IP address in a process called a DNS Lookup.
IP addresses are used by other devices for routing (ie. deciding where to send data). In most cases, especially home networks, a central router provides a DHCP (Dynamic Host Configuration Protocol) server that allows automatic IP negotiation. Automatic IP negotiation means the DHCP server can assign IP addresses to newly connecting devices without requiring manual configuration each time a (new) device connects. However, neither a router nor a DHCP server are strictly necessary, and manual configuration on the hosts can set them up with an IP address and enable communication between them (though it's a bog to deal with). The rest of this page will talk largely about DHCP setups.
Fundamentals
A classical IP address, as you might find in the wild, can look something like this:
217.154.217.127
In fact, this is the IP address that the domain ultracomfy.net resolves to. A very nice example of a standard IPv4 address: A set of four numbers, each between 0 and 2551), separated by a dot. The lowest possible IP Address therefore is 0.0.0.0, and the highest is 255.255.255.2552).
The reason this is so is because of math. As you may know, computers in the 21st century work with ones and zeroes. This is the binary system and individual ones and zeroes are called “bits” (or one “bit”). Eight of these in a row form a “byte”. As an example in the decimal system, given 8 digits the biggest number you can express is 99999999 (to get to 100000000 you would need another digit). In binary, the maximum number you can express with eight digits is 11111111 (to get to 100000000 you would need another digit). This number, converted to the decimal system, is 255, which is the reason numbers in IP addresses never exceed 255. Expressed in binary, 217.154.217.127 looks something like this:
11011001.10011010.11011001.01111111
This is the binary notation (as opposed to the dot-decimal notation we're used to seeing) that shows us what an IP address really is: A set of 32 bits (32 ones or zeroes), divided into four groups of bits called octets (…in networking. We can just think of them as Bytes). When your device wants to send data somewhere, it will send its data to your router with both the destination IP and the origin IP, like above, and the router will use IP tables to determine where to forward your data to. The computer sends addresses in binary, we humans typically read them as dot-decimal, they're the same thing.
IP Assignment
The IP address a DHCP server assigns to a device isn't (entirely) random. For home networks, three different reserved address spaces exist that routers may use to assign IP addresses. These begin with 10.0.0.0, 172.16.0.0 and 192.168.0.0. For example, my network at home is administered by a FritzBox router. Most FritzBoxes come out of the factory configured to use the 192.168.xxx.xxx space to assign to connecting devices. In my case, the FritzBox assigns itself the address 192.168.172.1 and then counts upward: If I now logged onto that router's WLAN with my phone, the FritzBox will assign my phone the address 192.168.172.2. Any subsequent devices registering on the network will get the lowest available IP that isn't currently assigned (ie. if I power on my PC now it will be assigned .3, and so on). These assignments, however, are only leased and a connected device needs to refresh a lease5) every once in a while if it wants to keep it.
The reason IP addresses are leased is for the sake of recycling. If every device got a new IP address every time it logged on, the router/DHCP server would eventually run out of IP addresses it can assign. Imagine we continue the example from above: My router is .1, my phone is .2 and my PC is .3. Now imagine I leave the house with my phone and I'm gone for so long that my phone's lease expires. The router can then reclaim the leased IP and assign it to new devices logging on. So, if for example my roommate was to log on her phone after mine disconnected, her phone could get .2 even though that was previously assigned to my phone. It was able to recycle .2 and use it for my roommate's phone instead of using up another IP address (.4). Leasing and recycling let the router use less IP addresses while serving the same number of devices. Only if I now came back into the house with my phone, and it tried to log onto the WLAN, the router would see that both .2 and .3 are now in use and will give my phone .4.
Private Addresses
What you just learned is what is called a “private address”. Private addresses are addresses used inside a local network, like your home network. The idea here is that there can be multiple networks with addresses starting with 192.168.xxx.xxx. For example, if you bought your own FritzBox, that FritzBox would assign IP's in 192.168.172.xxx as well. On a global scale, 192.168.172.1 (for example) could potentially point to millions of devices because there's millions of FritzBoxes in operation using these addresses privately. You can think of it like numbering your rooms. You could go into all houses in the world and number the rooms, “Room 1”, “Room 2”, “Room 3”, etc..
Each house would have its own Room 1's and Room 2's and so on, so if you now sent a letter with the destination “Room 3”, the mailman would have absolutely no clue where they're meant to go because there are billions of “Room 3”'s in the world. Of course, if you had a mail system inside your own house and sent mail to room 3 using that, that's when this system becomes useful, and it's exactly what Private Addresses are used for. They have nothing to do with the internet and are used solely by devices on a particular network (like my WLAN) to communicate to other devices on the same or interconnected networks (but not the internet). In that case it is completely irrelevant that there are other networks out there in the world with similar Private Addresses, because that's not who you're talking to anyway.
For this reason, if you tried to ping 192.168.172.2 from your own computer, you would not be reaching my personal computer in my particular home network. If your router assigns 192.168.xxx.xxx then a device on your network might be assigned 192.168.172.2 and you will be reaching that device, not mine, even if they have the same IP address. It is crucial to understand that IP addresses do not uniquely identify a device because the IP address assigned to a device can change and the same private IP addresses may and in most cases are used in other local networks.
Public Addresses
As established, private IP addresses are not useful for talking to other devices across the internet. They are useful within a home network or an intranet (internal network, businesses/companies use these often), but they don't mean the same thing for devices outside of your home network/intranet.
In the case of your home network, your modem (often built into your router) is assigned its own IP address.
Whereas devices on your home network turn to your router for IP assignment, your router is connected to the internet and will turn to your Internet Service Provider (ISP) for IP assignment itself. This gives the router two effective IP addresses: One used inside the network, locally (the Private IP address), and one address the router uses when talking to the internet (called the Public IP address). While I am writing this website, my public IP address is 176.5.60.56. This is my router's Public IP Address which it got from ths ISP and it's the address the router will uses whenever my router sends out data to the internet. So, when I on my phone connect to my router via WLAN, my phone is inside the local network and will get to know the router's private IP address (192.168.172.1) and the phone itself will be given a private IP address as well (192.168.172.4). Only the router has a public IP address, and it is not used in the communication between my phone and the router. When I now, on my phone open the website ultracomfy.net (which resides on 217.154.217.127) it will send the following to the router:
Source IP: 192.168.172.4
Destination: 217.154.217.127
Message Content: Ping!
Basically, “this is me, and this is where I want to go”. The router itself will now pass this information to its gateway using its public IP address. Remember that the router will use the public IP address as the Source IP to send data towards the internet:
Source IP: 176.5.60.56
Destination IP: 217.154.217.127
Message Content: Ping!
Note how devices on the internet don't even see 192.168.172.4. The router specified 176.5.60.56 as the Source IP, even though originally the source IP was the phone's private IP address. So, when you google for something like “What is my IP?” what you will see is the public IP address of your router. Whether I open that site from my phone, my PC, laptop, gaming console or a second phone, if they're connected to the same router, the router will always send out data as 176.5.60.56 regardless of which device inside the home network actually dispatched the request, and websites will show me 176.5.60.56 on every device I checked. Seriously, you can check that right now, they'll all be the same (except in exceptions). You can even try disconnecting from WLAN on your phone, turn on mobile data and reload the page, it will now show you a different IP because you're now accessing the internet via a cell tower and not the router at home you used previously.
Advisory
This is the reason why your IP address is not super sensitive information. I hand out my public IP Address for free here on this website because:
1) My router has leased this IP from my Internet Service Provider, and this lease will eventually run out. At that point it may get a new IP. Depending on your ISP, literally just restarting the router gets you a new IP lease, changing your IP immediately. By the time you read this it has already changed.
2) My public IP, even if it is current, points towards my router, not the end device I'm using. If you tried to mess with anything on my phone (which sits behind the router), you'd need to breach the router AND then infiltrate my phone somehow. As it stands, my public IP only helps you get to my router, no further.
3) A public IP address does give an attacker an approximate geographical information about your location (except in exceptions). That's how Google knows where you are (coarsely) when using their service. Attackers can also scan your router for vulnerabilities. For example, a router lets the owner set up port forwarding, which can be a vulnerability. Unless you configured the router otherwise, it comes shipped with a secure-by-default configuration. In any case, your public IP address is not equivalent to a password or direct access to a computer. Someone cannot just infect your computer with malware by knowing the public IP address of your router.
4) Just being exposed to the internet isn't unnormal. Your router is exposed to the internet all the time, as well as every other router on the world used in the same manner as yours. Similarly, internet servers like webservers (such as this website!) go out of their way to be exposed to the internet and even broadcast their IP address publicly for anyone to see. It's about the configuration of your firewall and the service you're providing (HTTP/S in the case of this server, among others) as well as being up to date. If you leave your network configurations mostly alone and stay up to date then you'll be just fine, like the other billions of devices exposed to the internet.
When ultracomfy.net (still 217.154.217.127, remember that you connect to devices with their IP) receives the data, it will take note of the Source IP (176.5.60.56) for later. That's where the message was sent from and, when ultracomfy.net responds, that will be where ultracomfy.net sends its response to. It will prepare the response and send it off, this time it itself is the Source IP:
Source IP: 217.154.217.127
Destination IP: 176.5.60.56
Message Content: Pong!
When it arrives at my router, the router will run into a problem: The message is addressed to the router (176.5.60.56), but it isn't the one who actually made the request. One of the devices in the network (in this case 192.168.172.4) made the request, and the router needs to forward it to them. To figure out who made the request (and therefore who to forward the message to) the router uses a system called Network Address Translation.
From: 192.168.172.1
To: 192.168.172.4
Message Content: Pong!
This is the end of the journey. My router sent ultracomfy.net's response back to my phone, which means we've done a full round-trip.
Network Address Translation
Network Address Translation (NAT) is the process of mediating between public addresses and private addresses. Your router dispatches information with its own public address, and responses from servers (like 217.154.217.127) will be sent back to your router's public address. But, of course, your router isn't the one who really wants the data, it's my phone that wants it. The router is just an intermediary. Back when my phone contacted the router asking for ultracomfy.net, my router noted down who that request was from, what they requested and a few other indicators. When the response comes back in, it contains extra information that the router can use to determine who the response is really addressed to.
You can think of it as Room 3 sending a letter to, say, Company HQ. Room 3 gives its message to the mailman and the mailman replaces the envelope's Source location (currently “Room 3”) to Residential Road 10 (because that's where you really live), and notes down that Room 3 of your house sent a message to Company HQ. When Company HQ sends a message back, it will be addressed to Residential Road 10. The mailman will arrive at Residential Road 10 and look into his notes, where he will find that it was Room 3 that sent a message to Company HQ. In the real world, of course, we write envelopes with something like “To the hands of” or “to the attention of” if we want someone particular at an address to receive the message. In private/public network communication this doesn't work, though, because devices on the internet never see devices in your router's local network. They don't have the private IP's of these devices and cannot address to it. NAT is a bit more complicated than this because it needs to distinguish in cases where, for example, two rooms send messages to Company HQ at the same time. This can be solved, but the solution (NAPT) exceeds the scope of this page about IP Addresses.
DNS
Numbers are hard to memorize. For example, ultracomfy.net is served to you by a server in Karlsruhe that has the IP 217.154.217.127. Could you memorize that? I certainly can't, and I've been actively trying to for a good while now. In fact, this particular address is actually a particularly easy one to memorize, too. But wouldn't it be nice if, instead of a bunch of random numbers, we could use easily memorizable names instead? This lead to the creation of Domain Names: Instead of typing out IP addresses, the owner of a server can register a domain, like ultracomfy.net, and point it to the desired IP address.
In the case of ultracomfy.net, the domain points at 217.154.217.127. So, you can type the domain into the browser, ultracomfy.net, hit Enter, and you'll arrive at 217.154.217.127 without memorizing the number. It might be the only way you've ever known browsing websites. But, you don't need domains. You can just enter the IP address of a server directly into your browser's URL bar and it will work just like entering the domain. Try copying 217.154.217.127 and paste it into your URL bar directly, then hit Enter. It will take you directly to the ultracomfy.net homepage without you ever seeing the domain name. Every website online has an IP address and you can enter it directly into your browser if you want to. You can even try 217.154.217.127/ip_address#dns which will take you directly to the DNS section of this particular page, instead of just the homepage.
The reason we use DNS is because, for one, domain names are easier to remember, but also because, as discussed, IP addresses change. The IP address(es) under which to reach google.com have changed many a times over the years, but the domain google.com has never changed.
What We've Learned
To sum it all up, we have learned that IP addresses are numbers given to network-capable devices by devices higher up in the chain to enable communication between them. These numbers are handed out temporarily and become invalid after some time unless renewed. This concept is known as “leasing”, and when a lease runs out, a device can request a new lease which may or may not be for a different IP address. A router in the home network is assigned an IP from the ISP (Internet Service Provider) which it uses to communicate upwards, ie. with the internet. Devices below it (ie. connected to it on the local network) use their own IP addresses which are used only amongst those devices to communicate with each other, never to the internet. If a device on the network wants to contact a device on the internet, it makes a request to the router, which will use its Public IP (the one assigned to it by the ISP), instead of the private IP address, to speak to the internet. When a response comes back, the router checks its notes to see which device on the local network originally made the outbound connection. This is called NAT (though this concept is a bit more complicated than just this and if you really want to know more, look up something like Google: NAPT networking). Domain names like ultracomfy.net are used to substitute IP addresses with human-readable text, but underneath it's always IP addresses.
:: [is really just 0000] or :1 [is really just 0001].