When people talk about securing internet connections today, it's usually about: IP addresses to be avoided from the outset. It's true that avoiding... IP addresses has some advantages - for example, it's much harder to track people - but there are also some major disadvantages. And unfortunately, these disadvantages are greater than people realize. For example, while it may be much harder to track people now, what about the future? So what really happened?
The investigation of the History of IPv4 is not just a look back at the past of the Internet. The point is to examine how this happens Internet has developed over the years and what could happen if we leave the current IP protocol behind. As you probably know, there is no such thing as a “safe” IP, meaning every Network can theoretically be vulnerable to monitoring by other network users. As you may also know, researchers have found that any Internet connection can easily be disrupted if there is a vulnerability in the Safety gives.
This raises two questions: First, why IPv4 introduced at all? There are many theories, but the simplest goes back to the beginnings of the World Wide Website back. At the time, there was concern about the large amounts of data being sent back and forth over wireless connections. (In retrospect, Wi-Fi is actually much better than wireless!) Part of this meant designing a way for IP addresses to communicate with specific ones computers could be connected – to a specific “network” of addresses.
In the remaining field part of the original draft for IPv4 There are essentially seven different classes of IP addresses. The first group, ranging from zero to seven, is called “broadcast” addresses. These are typically found on Wi-Fi networks. The next five, ranging from one to nine, are called “class” addresses. The last three, ranging from zero to nine, are classified as “unicast” or “unicast/broadcast” addresses.
With the “Classful” approach to IP addressing The same set of IP addresses can be used for a variety of purposes. However, this means that there is a limit to how many there can be at any given time. this is that “ipv4 address exhaustion” problem. Once this limit is reached, a user - for example an online advertiser who advertises his products on a Website want to sell to customers – stop sending any further requests for addresses from that particular company.
On the positive side, there is a way to solve the problem of exhaustion IP addresses to avoid. There are two ways to do this. First, the IP packet can only The IP address and contain the ICMP header, which itself is reserved for use with other IP packets. Secondly, the entire ICMP header can be sent in a single IP packet, which then contains the The IP address has as a goal. (ICMP Echo Request is a different type of request and requires a different type of response). Another method to solve the problem IP address exhaustion To avoid this is called “Multi Protocol Label” or MLPL, which was developed by Cisco to enable IP-based traffic control.
IP packages have some big advantages. For example, they transmit data very fast, allowing downloads to occur in a fraction of the time a regular connection would take. They can also be used in conjunction with other types of protocols, such as the RTP protocol or the ICMPv6 protocol. Beyond that, they are not through firewalls which can often hinder the transmission of confidential information. After all, they are the preferred form of networking in many metropolitan areas.
Unfortunately, there are also some significant disadvantages with IPv4 addresses. For example, there are only seven bits used to encode one IP address used can be. If that Network has many different subnets, each with its own IP address, then the IP addresses become too crowded and difficult to manage. This is called an “IP collision”. Even if a router can recognize the seven-bit code, it may not be able to IP addresses into the IP addresses required by the real world. Finally, because it can only identify IPs in a numeric format, it does not provide, and does not guarantee, a useful means of distinguishing between local and remote traffic Integrity of packages even.
