So... I have studied for CCNA and such and been working with IP networking at the least the past 8 years or so. I have always seen and been told that the network address for a subnet is not a valid host address. Now first I will start by saying I know this is true. My question is more... is there a technical reason it can not be used or was it just arbitrarily agreed upon when the specification was designed? I understand why a broadcast address can not be used (because it is ACTUALLY used). The thing is when I see a network address used it is normally only in routing which is specifically using NETWORK addresses. This being the case, (network addresses being used only when you are expecting a network address) is there some technical reason that they could not have the network address be an actual valid host address?
As far as I understand, "network address" as a special address is an artifact from the classful IP networks from the past. Today, we use Classless Inter-domain Routing (CIDR) on the Internet, which does not have the concept of a network address (if you look at the RFC 4632 linked above, you'll see that it lists 256 possible IP addresses per legacy "C" block, e.g. no reserved addresses for either network or broadcast address (although broadcasts are defined as essential in other RFCs).
This being said, you still should not assign a network address to any specific host in a network: Network address is essential for routing. This concept is used extensively in RFCs (RFC 1812). Just look at the routing tables (
Even worse: it is better not to assign IP addresses ending in zero even if this address is not a network address. E.g. if your network is 10.10.0.0/255.255.0.0, IP address 10.10.5.0 is not your network address, but you'd better not assign such IP even though it is completely valid even on classful IP networks. Some legacy software/IP stacks may have problems with it.
UPDATE: by goblinlord
According to RFC 1812 (Section 188.8.131.52) what we call a network address was originally used for "directed broadcasts" which would send a broadcast packet to the desired network. This function was made obsolete because of SMURF attacks. The function was officially changed in RFC 2644. Subsequently, further implementations should silently drop packets with a source address as described (the network address). While this is what should happen I am curious as to how many implementations actually do so.
This is further added to in RFC 3021 when /31 subnetting was addressed.
So the practical answer is: It really depends. It depends on:
I've not delved very deep into this but it seems that most ISPs do not block you from assigning and using your network address and I have not run into any problems accessing any sites in testing this; it seems that ultimately it's all left up to the network administrators' whims.
I'm sure there are security analysts and hackers out there who have insanely detailed stats on exactly how many variants of TCP-IP stack implementations are out there and what the do and do not accommodate or allow and exactly how and where they miss their mark.
Matter of fact, I'm browsing and posting this from my network address.
Don't call me a bad netizen unless you have a better solution to fixing this house of cards: the reality is that if it's possible, it will happen. The reality is that nobody really smart enough sat down and thought this whole thing through in all its possible iterations in order to come up with a completely fool-proof design. The result? Standards where a lot of things don't add up and/or get lost in translation.
Welcome to the real world. Don't let that dissuade you from chasing the ever elusive optimal ideals... Just don't expect support from the "official" channels or forums unless you are willing to get your hands dirty and dedicate your time and life to it.
So, I think what the other posters were trying to say: If you want to make this official policy and use it in production, you're on your own. (But aren't you anyways?) Maybe we'll strike it lucky and have a computer intelligence design us an IPv8 that's backwards compatible with IPv4 and IPv6 and all their broken implementations.
I'm new to network but I'll give my 2 cents as well.
If I have a /28 subnetwork from x.x.x.0 - x.x.x.15 According to the predefined rules we would have 14 usable hosts and 2 remaining. the remaining are for network and broadcast.
Lets, instead of following the rule above, actually use all 16 hosts. Then in that case all would be ok, no problems. But if communucation was needed outside the network then it would not be possible because of lack of resources to send or recieve the information.
I'm not great at explaining but to put it another way.
If I lived in a house on a street and the street contained 14 houses. A laneway in and out for access to the main road.
My mailing address would range from 1-14 Personal Street, Off Network Road.
That would be no problem for the mail man. Now lets assume the developers got greedy and added 2 more house and got rid of the laneways.
Then my new mailing address would range from 1-16 Personal Street
In this instance the mail man would be in trouble.
This is a guess, let me know if I'm talking bull.
The network address allows you to build route tables with fixed-size (4-bytes IPv4) destination column and fixed-size binary operations so that host routing and network routing is actually the same thing.
Imagine a routing table like this: (this PC has a parallel connection with another PC and a network card)
The AND between the IP address and the netmask gives you exactly what you need, a 4 bytes number which can be compared against each line without further calculations.
So the host number zero is special in the sense that after the AND operation its address naturally represents the whole network.
If you decided to use the network number as a host number it would result in a table like this:
This seems legit, so I suppose the concept of network address is used for routing reasons and thus it was decided arbitrarily to mark it as a special address and prohibit its use as a host address.
Well... actually it's not that simple. I decided to give it a try (!!!):
At present the network programs don't allow me to use a network number as a normal address.
Whilst searching for the answer to this question I came across this article from Cisco. The following quote from that article sums it up nicely I think.
Avoiding confusion is a good enough reason for me.
RFC 1122 ("Requirements for Internet Hosts -- Communication Layers") prohibits it:
A network address is not considered a host address but it is just a number. In address limited areas such as point-to-point networks a /30 mask is used often, yet still utilizes the host addresses. A lesser practice, but achieves the same principle is to use a /31 mask and use one end as the network address and the other as the broadcast.