Need help defining hardware for home network

crschil

Honorable
May 5, 2013
13
0
10,520
While doing some home renovations, I took the opportunity to with the house with CAT6.

So instead of 2 LAN computers and 1 printer, and everything else on wireless, I need to accommodate 19 LAN connections plus wireless clients. Initially, I was just planning on adding an inexpensive unmanaged switch and connecting to my current D-Link DIR-655, but I am sensing an opportunity to deploy a more robust solution and define a couple of VLANs for access control and to isolate different parts of the network. Ideally, I'd like to be able to restrict access to the Media Server to a few rooms, set up a separate VLAN for VoIP, and another for network management. I've never gotten involved in networking to this level before, so I need some guidance on hardware selection and letting me know what I need to consider.

My biggest question surrounds the VLANs and what equipment might be required to support them.

Are VLANs defined by IP address or by the port on the switch? And can you use DHCP with VLANs, or do I need to define static IP's for everything?

And this is probably related to the previous questions, but would the router or the switch define the VLAN? In what info I have found so far, it sounds like both are options, so if that is the case, which is preferable?

And lastly, what should I be looking for in terms of a router in addition to the VLAN question? Would a consumer-grade router be sufficient, or should I get a SOHO router? I do not need a modem as I have FIOS and connecting directly to ONT box.
 
I'm not certain on the following, but I'm fairly sure it's mostly correct:

Each port on a switch has to be a member of a VLAN (by default all are VLAN 1). Trunks between switches that follow VLAN standards can contain multiple VLANs, and be split back up at the other end of the link. As devices on a VLAN can't talk to other VLANs except through a router, you'll need a DHCP server per VLAN, or to use static IPs.

Not sure what you need router wise - VLANs would usually be getting into serious enterprise area at a guess. In a small office, you'd generally want everything to be able to talk directly to everything else.

I'm not sure why you'd want to limit access to your media server - it will likely end up being used as a file server too, and what's the problem with watching movies/listening to music from other areas of the house.

I can sort of understand separating out the VoIP though. Subnetting may be more useful there though - put a filter on your PBX.
 
I'm not certain on the following, but I'm fairly sure it's mostly correct:

Each port on a switch has to be a member of a VLAN (by default all are VLAN 1). Trunks between switches that follow VLAN standards can contain multiple VLANs, and be split back up at the other end of the link. As devices on a VLAN can't talk to other VLANs except through a router, you'll need a DHCP server per VLAN, or to use static IPs.

Not sure what you need router wise - VLANs would usually be getting into serious enterprise area at a guess. In a small office, you'd generally want everything to be able to talk directly to everything else.

I'm not sure why you'd want to limit access to your media server - it will likely end up being used as a file server too, and what's the problem with watching movies/listening to music from other areas of the house.

I can sort of understand separating out the VoIP though. Subnetting may be more useful there though - put a filter on your PBX.
 

crschil

Honorable
May 5, 2013
13
0
10,520


We also building an in-law suite as part of the aforementioned renovations that I wanted to keep on a separate VLAN (as in the near term) we'll likely have non-family guests and/or tenets there until my in-laws are old enough to move in.

I also have a few other items, such as security/home monitoring/client control that I want to limit access and thought they would be best on a separate VLAN as well.