DHCP and IP Addressing

[BostonDan]

Hi all,
It’s been a long time since I worked in networking and I’m hoping someone with more experience can answer this. Are there any issues setting up a DHCP server such that:
1) Network infrastructure IP addressing is 10.1.1.xxx
2) Printer IP addressing is 10.1.20.xxx
3) Wired PCs are 10.1.10.xxx
4) Wireless tablets/laptops are 10.1.100.xxx
5) Media devices are located at 10.1.50.xxx
Should I use the subnet mask 255.255.0.0 to enable me to view the entire network?
In advance, I appreciate the advice. BostonDan.

 

[jdabbs]

Home or corporate network? How many hosts?

 

[BostonDan]

DHCP & IP Addressing

Hi jdabbs,
Thanks for responding. This is for a home network and I could accomplish everything within 10.1.1.xxx. No justifiable reason for spreading out the addressing other than I think it would be nice to have everything segmented like this. I have somewhere in the neighborhood of 40 devices between laptops, tablets, desktops, printers, NAS's, and media players.
Thanks again for responding - BostonDan

 

[stevech]

segmenting - you mean several subnets?
If your net mask in the router is
255.255.255.0
(which is the default)

Then 10.1.1.x
will be a different subnet than
10.1.2.x

so for the two subnets to interoperate, your router will need to be configured with a static route between the two subnets.
Port forwarding, if you use it on the WAN side, will be more complex.

For a home LAN, I believe it brings no benefit and adds complexity.

If you want to segregate guest users... and restrict them to Interenet-access-only, that's a different story.

 

[coxhaus]

You will want to use Microsoft’s DHCP server. It will handle class b scopes really well. Home routers were not designed to do this; most can’t handle class b scopes. There are a few.

 

[BostonDan]

DHCP & IP Addressing

Thanks all for responding. This is looking like it is more work than it is worth for my experimenting and educational experience. I'm going to keep everything within 10.1.1.xxx. I'm very surprised this isn't more straight forward and supported by consumer routers.

Again, thanks all for your guidance. I'm definitely glad I posted here first before going down a path that would have been more work and frustration than I'm willing to bear.

All the best - BostonDan

 

[theonlyski]

Thanks all for responding. This is looking like it is more work than it is worth for my experimenting and educational experience. I'm going to keep everything within 10.1.1.xxx. I'm very surprised this isn't more straight forward and supported by consumer routers.

Again, thanks all for your guidance. I'm definitely glad I posted here first before going down a path that would have been more work and frustration than I'm willing to bear.

All the best - BostonDan

What kind of router do you have? I don't remember any that I have had in a while that didn't support VLSM (granted I usually have Cisco/Linksys hardware).

Using a 16-bit subnet mask shouldn't be out of the question on pretty much any modern hardware. It's not my preferred solution, but it will probably work just fine with no issues.

The problem comes with the DHCP server, however if you statically assign all of the IP's, it's a null point. Possibly the same if you make DHCP reservations.