LoneWolf 157 Posted June 29, 2015 Share Posted June 29, 2015 (edited) Yeah, I never used VLANs for performance, unless by that you mean using QoS to prioritize one VLANs traffic over another. When I've used VLANs, it is largely for organization and security. For example, I worked in education. I didn't want a student with computer skills to be able to figure out they might be able to scan IP ranges for security cameras, and then attempt to log into them via Web UI. So the cameras were on a separate VLAN, with a route for them to the server, but no option for students to get to them. In an environment that needs a much higher number of IP addresses (like where I was) it was nice to organize IP projectors into a VLAN. I had two VLANs for the wireless access points; one for the IP range and private LAN SSID, and one for the student SSID. This meant students traffic could only go to the Internet, and couldn't touch staff computers, or the server (which they didn't need access to). However, most of this stuff is pointless for a home network, and you don't have to use VLANs to use QoS. Also, VLANs will require static routes if you need a bunch of devices on one VLAN to communicate with a server or other device on another, which gets complicated in a home environment. Edited June 29, 2015 by LoneWolf Link to post Share on other sites
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now