Autosave: 2024-08-16 16:00:03
This commit is contained in:
parent
b0ccc33056
commit
3ca0ed8962
5 changed files with 48 additions and 11 deletions
BIN
.zk/notebook.db
BIN
.zk/notebook.db
Binary file not shown.
6
Untitled.canvas
Normal file
6
Untitled.canvas
Normal file
|
@ -0,0 +1,6 @@
|
|||
{
|
||||
"nodes":[
|
||||
{"id":"b0831d37c4411c6a","x":-404,"y":-370,"width":250,"height":60,"type":"text","text":""}
|
||||
],
|
||||
"edges":[]
|
||||
}
|
33
zk/IP_addresses.md
Normal file
33
zk/IP_addresses.md
Normal file
|
@ -0,0 +1,33 @@
|
|||
---
|
||||
title: IP_addresses
|
||||
tags: [network, internet]
|
||||
created: Friday, August 16, 2024
|
||||
---
|
||||
|
||||
# IP addresses
|
||||
|
||||
## IPv4 vs IPv6
|
||||
|
||||
IP addresses come in two formats and bit-lengths depending on which version of
|
||||
the [Internet Protocol](Internet_Layer_of_Internet_Protocol.md) is being used.
|
||||
|
||||
- IPv4 addresses are 32-bits in length
|
||||
- IPv6 addresses are 128-bits in length
|
||||
|
||||
The larger the bit-length, the more unique addresses that can be generated. Thus
|
||||
IPv6 can create more addresses that IPv4.
|
||||
|
||||
This entry focuses on IPv4 addresses.
|
||||
|
||||
## Anatomy of an IPv4 address
|
||||
|
||||
Each of the 32 bits are divided into four groups which are each 8 bits (a byte)
|
||||
in length. Each group therefore comprises an octet and is separated by dots.
|
||||
|
||||
The decimal number system, rather than binary is used to represent the values.
|
||||
Thus each octet comprises three decimal digits as 8-bits = 2^3.
|
||||
|
||||
The 32 bits form two sections:
|
||||
|
||||
- the **network prefix**
|
||||
- the **host**
|
|
@ -13,16 +13,16 @@ In order for the data to get from a machine on one local network to a machine on
|
|||
another local network, each machine must have a way of identifying and
|
||||
interfacing with the other.
|
||||
|
||||
The Internet Layer utilises the Internet Protocol to determine how devices will
|
||||
be publicly identified to devices on other networks and how different devices on
|
||||
the same local network will be distinguished from outside of this network. This
|
||||
is achieved through Internet Protocol (IP) addresses.
|
||||
The Internet Layer utilises the **Internet Protocol** to determine how devices
|
||||
will be publicly identified to devices on other networks and how different
|
||||
devices on the same local network will be distinguished from outside of this
|
||||
network. This is achieved through Internet Protocol (IP) addresses.
|
||||
|
||||
## Packets
|
||||
|
||||
Data is sent accross the internet between hosts as _packets_. These packets,
|
||||
when sent and received within the
|
||||
 on the local network, are
|
||||
[Link Layer](Link_Layer_of_Internet_Protocol.md) on the local network, are
|
||||
enclosed within a Link Layer frame (in its payload section):
|
||||
|
||||

|
||||
|
|
|
@ -27,17 +27,15 @@ protocols. From the top:
|
|||
|
||||

|
||||
|
||||
- The  concerns communication
|
||||
- The [Link Layer](Link_Layer_of_Internet_Protocol.md) concerns communication
|
||||
between devices on the same local network. The transfer of information once it
|
||||
has been received from the internet or its transfer between devices before it
|
||||
sent out into the internet. Ethernet and WiFi are two core protocols utilised
|
||||
at this layer.
|
||||
|
||||
- The
|
||||

|
||||
is concerned with communication accross networks. It is responsible for
|
||||
identifying hosts on the inter-network by their addresses and routing data
|
||||
from network to network.
|
||||
- The [Internet Layer](Internet_Layer_of_Internet_Protocol.md) is concerned with
|
||||
communication accross networks. It is responsible for identifying hosts on the
|
||||
inter-network by their addresses and routing data from network to network.
|
||||
|
||||
- The **Transport Layer** come back to this
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue