Subnet Mask Help

We have IP range of 172.16.16.0 - 172.16.27.255 with mask of 255.255.254.0.
In this case, what would the broadcast address be? Is it 172.16.27.255,
or 512 nodes of 172.16.17.255, if gateway is 172.16.16.1??

Help is very appreciated.

Ste

 

:We have IP range of 172.16.16.0 - 172.16.27.255 with mask of 255.255.254.0.
:In this case, what would the broadcast address be? Is it 172.16.27.255,
r 512 nodes of 172.16.17.255, if gateway is 172.16.16.1??

That's not a valid continuous IP range: that's two ranges stuck
together, 172.16.16/21 and 172.16.24/22. There is no valid broadcast
address for it.

If you were using a valid range, then the broadcast address would always
be the last address in the range.

 

Bonjour,

I try to reply that.

In your range, all addresses are not in the same network. So, the broadcast
also depends on the configuration of the routers .
If the mask was 255.255.240.0, the network broadcast will be 172.16.31.255 !

Angelot

 

Hi,

I assume you've made a typing error in the 172.16.27.255 address, otherwise
the network range doesn't fit the netmask you describe. I'll assume you've
meant to type 172.16.17.255.

In that case;
172.16.16.0 will be your network address (not assignable/usable for hosts
orother equipment)
172.16.16.1 will be the first usable address
172.16.17.254 will be the last usable address
172.16.17.255 will be your broadcast address (not assignable/usable for
hosts orother equipment)

You can chose any address in the range from 172.16.16.1 - 172.16.17.254 to
be your gateway address. On all networks I've setup I used the last address
of the range to be the gateway address, but that's just my way of doing it.

Erik

 

Thanks for the help.

But there is no laughing matter, someone does give us range from
172.16.16.0 -- 172.16.27.0 with that mask of 255.255.254.0.

I am pulling my hair about how to implement these nettings.

Please HELP!

Libes

 

Well, the first thought is that it just won't work, since you can't have a
broadcast address that is within that range. The real broadcast address is
172.16.127.255. It would of course work with all the equipment with the
same network/subnet mask, but any other equipment would have problems and
couldn't communicate via broadcast w/you. Not sure why they'd assign this
to you. I'm curious though.... These are private ip addresses. Why are
you restricted to that block? Or is this an internal thing where your group
has that range to use, but still needs to access the rest of the corporate
network?

But, that aside - it is a very big address space. You apparently have the
option of using all those addresses, but you don't have to. So, what I
would suggest is to break it into at least two subnets. 172.16.16.0/21
(255.255.248) would give you 172.16.16.0-172.16.23.255. Throw away the
rest, or use them as smaller subnets.

Hope that helps,

Jim

 

:Thanks for the help.

:But there is no laughing matter, someone does give us range from
:172.16.16.0 -- 172.16.27.0 with that mask of 255.255.254.0.

:I am pulling my hair about how to implement these nettings.

You cannot impliment that, those are not correct settings.

I agree with the previous poster who suggested that you have a typo.
If the 27 is really a 17, 172.16.16.0 -- 172.16.17.255, then
255.255.254.0 would be the correct subnet for that, and the broadcast
address would be 172.16.17.255.

 

:Well, the first thought is that it just won't work, since you can't have a
:broadcast address that is within that range. The real broadcast address is
:172.16.127.255.

How do you get that particular address as the "real" broadcast address?
The minimum broadcast address that covers the range from 172.16.16.0 to
172.16.27.255 is 172.16.31.255 . Why would 172.16.127.255 be any more
"real" than 172.16.31.255 or 172.16.255.255 ?

 

Based on the subnet mask given (255.255.254.0), the address block would be
172.16.0.0-172.16.127.255. Thus, the real broadcast for that block is
172.16.127.255. Yes, you are correct for the minimum to cover that range,
but that wasn't the question.

 

If you have 172.16.16.0 through 172.16.27.255
and a mask of 255.255.254.0,
that means there are 6 different subnets in your range.

Your third octet is subnetted this way:

172.16.sssssss-h.hhhhhhhh

0001000-h hhhhhhhh
0001001-h hhhhhhhh
0001010-h hhhhhhhh
0001011-h hhhhhhhh
0001100-h hhhhhhhh
0001101-h hhhhhhhh

So there are six different broadcast addresses, one for each subnet.

They are:


0001000-1 11111111
Net = 172.16.16.0 Broadcast = 172.16.17.255

0001001-1 11111111
Net = 172.16.18.0 Broadcast = 172.16.19.255

0001010-1 11111111
Net = 172.16.20.0 Broadcast = 172.16.21.255

0001011-1 11111111
Net = 172.16.22.0 Broadcast = 172.16.23.255

0001100-1 11111111
Net = 172.16.24.0 Broadcast = 172.16.25.255

0001101-1 11111111
Net = 172.16.26.0 Broadcast = 172.16.27.255

 

Yes, that is correct, but just to be clear - that would require the subnet
mask to be changed to 255.255.248.0 for each of those subnets.

 

:Based on the subnet mask given (255.255.254.0), the address block would be
:172.16.0.0-172.16.127.255.

No, you are describing what it would be if the subnet mask were
255.255.128.0.

 

Doh, I shouldn't try to think early in the morning - it always get me into
trouble. Back to subnet basics for me. You are right - forget everything
I've said on this topic.

 

Your data is inconsistent:

- A base address of 172.16.16.0 and a netmask of 255.255.254.0 result
in an address range of 172.16.16.0 - 172.16.17.255, with a broadcast
address of 172.16.17.255.

- If you have indeed been assigned an address range of 172.16.16.0 -
172.16.27.255 with a netmask of 255.255.254.0, that would result in
six disjoint IP nets, each with its own broadcast address, and each of
them requiring its own gateway:
172.16.16.0 - 172.16.17.255
172.16.17.0 - 172.16.19.255
172.16.20.0 - 172.16.21.255
172.16.22.0 - 172.16.23.255
172.16.24.0 - 172.16.25.255
172.16.26.0 - 172.16.27.255

- If you have been assigned the range of 172.16.16.0 - 172.16.27.255
and you get to choose your own netmasks, that would result in at least
two disjoint IP nets:
172.16.16.0 - 172.16.23.255 (netmask 255.255.248.0)
172.16.24.0 - 172.16.27.255 (netmask 255.255.252.0)
or three if you want to use the same netmask everywhere:
172.16.16.0 - 172.16.29.255 (netmask 255.255.252.0)
172.16.20.0 - 172.16.23.255 (netmask 255.255.252.0)
172.16.24.0 - 172.16.27.255 (netmask 255.255.252.0)

HTH

 

No, I think you're wrong there, buddy.
Or perhaps not explaining yourself well.

My response is specifically in response to the "ranges"
originally posted.

 

You are right - I just didn't have my thinking cap on this morning. I
really do understand subnetting, but looking back, I can't believe the posts
I made this morning. Thinking and responding too quick without taking time
to do the math. I'll blame it on the lack of sleep this week

 

And in all these cases Ste could use the One True Broadcast Address(TM)
- 255.255.255.255. Since this is a Cisco group then we should point
out that that's what s/he'll get by default on an IOS device (I don't
have experience of non-IOS Cisco routing-things).

Sam