/32 addressing

Generally speaking, /32 means that the network has only a single IPv4 address and all traffic will go directly between the device with that IPv4 address and the default gateway. The device would not be able to communicate with other devices on the network.

There are a couple of possible reasons for this that I've seen. It could be:

• A webserver serving multiple sites with each site bound to a specific IPv4 address


• A loopback address used for testing.


• Isolating a machine from the network to allow only statically set routes to connect. (For decommissioning, for example.)

Network ID

The network ID portion of an IP address is determined by the subnet mask. For example:

• A /24 IPv4 network has a subnet mask of 1111.1111.1111.0000, meaning the first 3 octets are the network ID and the last octet is used for assigning host IDs (256 available IDs, though usually some are reserved).


• A /16 IPv4 network has a subnet mask of 1111.1111.0000.0000, meaning the first 2 octets are the network ID and the last octet is used for assigning host IDs (65536 available IDs, though usually some are reserved).

In the case of /32, this doesn't apply as the address is both a network ID and host ID. /31 addresses are also all host IDs with no reserved 0th address.

It is just CIDR value. You can learn more in here for CIDR.

TL;DR

A CIDR network address looks like this under IPv4:

192.30.250.00/18

The "192.30.250.0" is the network address itself and the "18" says
that the first 18 bits are the network part of the address, leaving
the last 14 bits for specific host addresses.
subnet-mask

easiest thing is web search and read articles related to subnet mask and subnet mask binary shorthand and CIDR

and also check out subnet calculators

the /32 is the CIDR (shorthand) and refers to how many 1's are in the subnet mask. For /32 that is 255.255.255.255 or 11111111.11111111.11111111.1111111

that means you can only have one ip address, on your network before needing a gateway/router to get outside that network. with /32 it's just you.
A subnet mask is a number that defines a range of IP addresses available within a network

CIDR = classless inter-domain routing

what does using /32 mean : I don't believe it is an invalid setting however it effectively turns off networking... or limits the network to just you... you can only talk to yourself if you don't have a gateway set up to reach outside that netmask.

what will its network id be: I assume you mean what will ip address be, and ip address will be whatever you set it to be. The IP address and subnet mask (which is what you are dealing with) are two different although related things.

can a host exist without a network id [ip address?] : can you exist without having a first and last name or without an address? yes the host can exist. kinda need to better define what u mean by exist.

What you're looking at are not subnet masks. They are indications
of the length of the routing table¹ prefixes.

A naïve implementation of a routing table would list every possible IP
address so that, given any IP address, you'd look up that exact one
and get back the routing information² associated with it.

Clearly some sort of compression is needed. The nature of routing
information is that adjacent addresses are likely to use the same
information, so we can use a form of radix tree to compress these
together. Here, briefly, is how it works.

Given the numbers 0-7, we can represent them in binary as so:

0   000

1   001

2   010

3   011

4   100

5   101

6   110

7   111

Now if we have two routing table entries, one for addresses 0 and 1,
and another for addreses 2 and 3, we can store them under the binary
prefixes that these share. If we use a . to indicate the "unused"
bit after the end of the prefix, we have 00. for the range 0-1 and
01. for the range 2-3.

A standard way of representing this is with the lowest number from the
range followed by the length of the prefix; in this case these would
be 0/2 for the range 0-1 and 2/2 for the range 2-3.

But what happens if we want to look up the routing information for
address 6? Normally we'd add a "default" set of routing information
with prefix 0/0, i.e., matching any bits at all and then when we
search we look for the most specific information i.e, the longest
matching prefix, we can find. So the full routing table we've just
described is:

0/2     00.     Matches addresses 1 and 2.

2/2     01.     Matches addresses 3 and 4.

0/0     ...     Matches any address.

Subnet masks can be described with prefixes in the same way, and so
this scheme is often used for that. But keep in mind that just because
this scheme can be used for describing subnets does not mean that
it's used only for describing subnets.

As an example of routing table prefixes not being subnets, you could
have two network interfaces connected to the same network, say,
192.168.2.0/24. (This could be implemented by connecting two separate
network cards to the same switch, each with its own cable.) You could
then set up the routing table to "balance" outgoing traffic across the
two interfaces by using two routing table entries:

192.168.2.0/25      eth0        # range ...2.0   to ...2.127

192.168.2.128/25    eth1        # range ...2.128 to ...2.255

This would send packets destined to addresses 0-127 on that network
out eth0, but packets destined to addresses 128-255 on that network
out eth1. This is a bad way of doing this (for reasons I won't get
into here), but demonstrates how routing prefixes and network
addresses might not match.

¹ _{The Wikipedia article on routing tables unfortunately says
that the prefix field holds the "Network ID." While this may be true
in certain specific implementations of routing tables, it's not
always a network ID in the general case, as seen in both the example
you provide and my example later in this answer.}

² _{This routing information typically includes things like what
interface to use, what router to contact on that interface, if any,
the MAC address of a host for hosts directly reachable through that
interface, what source address we should put on the packet if the
host has multiple source addresses, security information, and so on.
There's a huge variety of data that could be there, but none of that
is important for the purposes of this discussion since we're talking
just about how you look up the correct data set for a given address,
not what's in the data set itself.}