IPv4 (Internet Protocol version 4), in former times simply IP, is the fourth version of the Internet Protocols (IP). It was the first version of the Internet Protocols, which was world-wide spread and used and forms an important technical basis of the Internets. One defined in RFC 791 in the year 1981 by Jon Postel.
IPv4 uses 32-Bit-Adressen, therefore maximally 4.294.967.296 clear addresses are possible. IPv4-Adressen are written usually decimally in 4 blocks: for example 207.142.131.235. For each block 8-bits are summarized; thus a range of values from 0 to 255 results for each block. During the advancement IPv6 128-Bit-Adressen are used. It is not yet very much common however today (2006).
A IP address is divided into a network part and a host (address) part. Computers are in the same IP net, if the network part of their address is equal actual that a condition that these computers can communicate directly with one another. In the same net no host address may be doubly assigned.
Needed for communication between different nets rout. The responsible administrator for each participating equipment assigns the address part differently. In nets with many participants the assignment of the address part is often transferred by a DHCP server in such a way specified. The network address assigns the owner or planner of the network. In the Internet the IANA is responsible for the assignment of the network addresses.
A typical network separates the 32-Bit into a 24-Bit network and 8-bits an address part (in former times class C addresses). The exact allocation between power pack and address part is indicated in form of the Subnetmask (e.g. 255.255.255.0). An alternative notation is e.g. 192.68.0.0 /16; it means the "16" that the left 16 bits are equal to 1.
| IP net classes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Bit 0-3 | 4-7 | 8-15 | 16-23 | 24-31 | ||||||
| Class A: Wet 0.0.0.0 /8 to 127.0.0.0 /8 | ||||||||||
| 0" 8-bit net | 24 bits host | |||||||||
| Class B: Wet 128.0.0.0 /16 to 191.255.0.0 /16 | ||||||||||
| 1 0" 16 bits net | 16 bits host | |||||||||
| Class C: Wet 192.0.0.0 /24 to 223.255.255.0 /24 | ||||||||||
| 1 1 0" 24 bits net | 8-bit host | |||||||||
| Class D: Groups of multicast of 224.0.0.0 /4 to 239.0.0.0 /4 | ||||||||||
| 1 1 1 0 | 28 bits multicast group ID | |||||||||
| Class E: Reserved 240.0.0.0 /5 to 255.0.0.0 /5 | ||||||||||
| 1 1 1 1 0 | 27 bits reserves for future applications | |||||||||
In former times there were firmly prescribed organizations for network classes with a firm length. This organization proved however as too inflexible, so that one changed over since 1993 bit-variable to accomplish it in the Classless inter+ Domain Routing procedure. Nowadays one cannot speak strictly speaking no more of class A/B/C networks, however it remained received generally linguistic usage and many networkable operating systems to determine the standard net mask on the basis the old classification.
The maximum number of too assigned host addresses in a net is
Two host addresses are always omitted - the first address (for example 192.168.0.0) designates the net, which is last address (for example 192.168.0.255) for the Broadcast reserved. (All participants are addressed.)
More to it: Net class.
Some classes of network addresses are reserved for special purposes. RFC 3330
| Address block | Use | Reference |
|---|---|---|
| 0.0.0.0 /8 | Current network | RFC 1700 |
| 10.0.0.0 /8 | Private network of the class A | RFC 1918 |
| 14.0.0.0 /8 | Public data network work | RFC 1700 |
| 39.0.0.0 /8 | Reserved | RFC 1797 |
| 127.0.0.0 /8 | Loop-bake (local computer) | RFC 1700 |
| 128.0.0.0 /16 | Reserved | RFC 3330 |
| 169.254.0.0 /16 | Private network (left local) | RFC 3927 |
| 172.16.0.0 /12 | Private network of the class B | RFC 1918 |
| 191.255.0.0 /16 | Reserved | RFC 3330 |
| 192.0.0.0 /24 | Reserved | RFC 3330 |
| 192.0.2.0 /24 | Test networks | RFC 3330 |
| 192.88.99.0 /24 | IPv6 to IPv4 Relay | RFC 3068 |
| 192.168.0.0 /16 | Private network of the class C | RFC 1918 |
| 198.18.0.0 /15 | Network bench mark test | RFC 2544 |
| 223.255.255.0 /24 | Reserved | RFC 3330 |
| 224.0.0.0 /4 | Multicasts (formerly class D network) | RFC 3171 |
| 240.0.0.0 /4 | Reserved (formerly class E network) | RFC 1700 |
| 255.255.255.255 | Broadcast |
IP addresses for local of networks become detailed in the article Private_IP-Adressebehandelt
| Address range | Description of class | Net mask | largest CIDR block | Number of IP addresses |
|---|---|---|---|---|
| 10.0.0.0 - 10.255.255.255 | 1 class A net | 255.0.0.0 | 10.0.0.0 /8 | 224 = 16.777.216 |
| 172.16.0.0 - 172.31.255.255 | 16 class B of nets | 255.240.0.0 | 172.16.0.0 /12 | 16 216 = 1.048.576 |
| 192.168.0.0 - 192.168.255.255 | 256 class C of nets | 255.255.0.0 | 192.168.0.0 /16 | 216 = 65.536 |
| 169.254.0.0 - 169.254.255.255 | left local, 1 class B net | 255.255.0.0 | 169.254.0.0 /16 | 216 = 65.536 |
Example: (/24 (in former times class C net))
| Subnetzmaske | = | 11111111.11111111.11111111.00000000 | (255.255.255.0) |
| The owner specifies the power pack on 192.168.0: | |||
| Power pack | = | 11000000.10101000.00000000 | |
| That leads to the following address distribution: | |||
| Net name | = | 11000000.10101000.00000000.00000000 | (192.168.0.0) |
| First addr. | = | 11000000.10101000.00000000.00000001 | (192.168.0.1) |
| Last addr. | = | 11000000.10101000.00000000.11111110 | (192.168.0.254) |
| Broadcast | = | 11000000.10101000.00000000.11111111 | (192.168.0.255) |
| Number addresses which can be assigned: 2 ^ 8 - 2 = 254 | |||
Example: (Classless)
| Subnetzmask | = | 11111111.11111111.11111000.00000000 | (255.255.248.0) |
| The owner puts the power pack firmly on 192.168.120 (whereby in the third block only the five most significant bits to the power pack to belong): | |||
| Power pack | = | 11000000.10101000.01111 | |
| That leads to the following address distribution: | |||
| Net name | = | 11000000.10101000.01111000.00000000 | (192.168.120.0) |
| First addr. | = | 11000000.10101000.01111000.00000001 | (192.168.120.1) |
| Last addr. | = | 11000000.10101000.01111111.11111110 | (192.168.127.254) |
| Broadcast | = | 11000000.10101000.01111111.11111111 | (192.168.127.255) |
| Number addresses which can be assigned: 2 ^ {11} - 2 = 2046 | |||
A IP package consists of a header and the actual data. The data division contains usually further minutes, usually TCP, a UDP or an ICMP. The maximum length of the data amounts to 65515 bytes (216-1-minimale header length). Normally the transmitter limits the package length to that of the underlying medium with Ethernet amounts to the MTU in such a way specified (maximum transfer unit) 1518 bytes, whereby 18 bytes are occupied by Ethernet themselves. For IP (header and data) only 1500 bytes are thus available. Therefore the length of IP packages is often determined at 1500 bytes.
Other networks can limit the package length further. In this case IP offers the option to fragment IP packages. Each package receives an identification (the fragment ID) from the transmitter. Rout can a long package divide, because the goal network does not transfer packages of this length. The receiver can identify and again join the fragments on the basis the identification and the transmitter address.
We found here 28 articles.
We found here 3 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback