K

Kathleen Martin

Guest
IPv4 is the fourth generation of Internet Protocol. Since 1983, it has been the primary network layer protocol used to power the internet and other packet-switched networks. Its defining characteristic is its use of 32-bit addresses (Example: 192.0.2.38) that allow devices to connect to the internet by sending data to and receiving data from websites, file servers, and other network devices, via their respective individual IP addresses.
While IPv4 has become ubiquitous with the internet, it was originally designed for small-scale networks. As the internet has grown beyond all expectations, the limits of IPv4’s address space have presented some technical challenges. A newer version of Internet Protocol, IPv6, was designed to alleviate some of these issues. But does that mean you should choose IPv6 over IPv4 for your IoT solution? The short answer is not really. Either protocol (or even both) is fine for IoT. The key is to configure the interfaces and network properly and securely. 
Though that may sound surprising, given the tens of billions of devices that are currently connected to the Internet. Let’s take a look at why.
IPv4’s Limited Address Space
When IPv4 was embraced as the foundation of the internet, the fact that its 32-bit address space would only yield around 4.3 billion unique IP addresses was a non-issue. As time moved on, however, more and more users began connecting to the internet, resulting in a boom in the number of smartphones, tablets, and other connected devices. As all of these devices require an IP address, the end result is that the number of addresses available under IPv4 infrastructure has been completely exhausted.
To help address this issue, a number of IP address ranges have been dedicated for use within private networks. These private IP addresses can be used by each network without a conflict with any global IP address employed elsewhere. Network administrators can assign addresses in these ranges as they like, provided that a private IP address assigned to a specific device still remains unique within its own private network. 
In order for devices with private IP addresses to be able to communicate with the internet (or an external network in global IP address space), private networks need to employ Network Address Translation (NAT). NAT is a function, commonly handled by a gateway or router, that takes a packet from a device within the private network, translates its source IP address to a global IP address before sending it out to an external network. It then keeps track of which private IP address the response packet should be forwarded to once received. NAT allows users to connect multiple devices to the internet or an external network using a single public IP address. It is used just about everywhere, from homes to businesses, and even public WiFi at cafes and libraries.
Continue reading: https://www.iotforall.com/role-of-private-networks-in-securing-ipv4-vs-ipv6-deployments
 

Attachments

  • p0006672.m06321.the_role_of_private_networks_in_securing_ipv4_vs_ipv6_deployments_1_1024x768.jpg
    p0006672.m06321.the_role_of_private_networks_in_securing_ipv4_vs_ipv6_deployments_1_1024x768.jpg
    229.4 KB · Views: 5
  • Like
Reactions: Kathleen Martin