What is the use of IPv4 Subnetting?

 During the early stages of the internet, organizations assigned IP addresses like crazy until we nearly ran out. Luckily, the designers of IP addressing came up with a way to end this wasteful practice: Dividing networks using subnetting.


The process of taking an extensive network and splitting into smaller networks is known as subnetting — and it’s freeing up more public IPv4 addresses.

There are two parts to an IP address: The network portion and the host portion.

It’s like the address for a house. The network portion is like the city, state, and zip code. The host portion is like the house and street number.

A subnet defines the number of bits, out of 32, used for the “network portion” of the address. Subnet masks can also be defined in a more common ‘slash’ representation, known as CIDR notation. In the following table, the red digits represent the bits used for the network. The black digits will be used for device IP addresses. Note that the 255.0.0.0 mask can also be represented as a ‘/8’ because it reserves 8 bits of the overall 32 bits used to describe an IPv4 address as the network portion.


Comments

Post a Comment

Popular posts from this blog

Implementing Core Cisco ASA Security (SASAC)

  ASA uses a security level associated with each interface. It is a number between 0 to 100 that defines the trustworthiness of the network that the interface is connected to; the bigger the number, the more trust you have in the network. For example, the most secure network, such as the inside LAN, should have the security level of 100. The outside network connected to an untrusted network (such as the Internet) should have the level of 0. The interface connected to the DMZ should have the security level set to somewhere between 1 and 99 (usually 50). Security levels are used to define how traffic initiated from one interface is allowed to return from another interface. By default, the higher level security interfaces can initiate traffic to a lower level. The stateful inspection determines whether the reply traffic is allowed to make it back through. The following picture illustrates the concept: level 100 for the inside network level 50 for the DMZ network level 0 for the outside ne
Read more

Netware Makes a Splash

During this period, several operating systems were developed, like IBM's MVS operating system, which still dealt with SNA. However, the development of another operating system, dubbed UNIX, really paved the way for NOS everywhere. After a project to develop a large and complex system called Multics failed to get off the ground at Bell Labs in 1969, a group of Bell researchers, led by Ken Thompson and Dennis Ritchie, started work on a less ambitious but no less powerful computing system. After a rocky first few years, Ritchie developed the C programming language, which allowed UNIX to become the first "portable" operating system, meaning it could be implemented on any computer system. The relative simplicity of the system's design and the availability of its source code turned UNIX into a darling of the academic world and a fixture on many university computer networks. Many versions of UNIX were developed, but the Berkeley Software Distribution (BSD) version, develo
Read more

How CrackStation Works

CrackStation uses massive pre-computed lookup tables to crack password hashes. These tables store a mapping between the hash of a password, and the correct password for that hash. The hash values are indexed so that it is possible to quickly search the database for a given hash. If the hash is present in the database, the password can be recovered in a fraction of a second. This only works for "unsalted" hashes. For information on password hashing systems that are not vulnerable to pre-computed lookup tables, see our hashing security page. Crackstation's lookup tables were created by extracting every word from the Wikipedia databases and adding with every password list we could find. We also applied intelligent word mangling (brute force hybrid) to our wordlists to make them much more effective. For MD5 and SHA1 hashes, we have a 190GB, 15-billion-entry lookup table, and for other hashes, we have a 19GB 1.5-billion-entry lookup table. Read more :  lm hash generator
Read more