At this point, the question is mainly about VLAN tagging.
For example, I want to set up VLAN 1 for my general home network, VLAN 2 for Internet/WiFi-connected gadgets, and VLAN 3 for IP camera system.
In the garage I have a managed switch with POE ports for cameras and also I want general network. So, for the trunk line that connects the router in the house to the switch in the garage, I will need to turn on VLAN 1 and VLAN 3 tagging to the ports used for the trunk line connection. As well, assign the access/device ports of the switch to the respective VLANs without tagging, then exclude any remaining ports I don't want on any given VLAN.
On the other hand, I will also have another managed POE switch in the house, but the trunk to that switch will only carry VLAN 3, so I do not need to set up tagging in that case. Taking it one step further (or perhaps backward) if I never had any requirement beyond VLAN 3 to this switch, it wouldn't even need to be a managed switch/have VLAN capability.
Correct so far?
For example, I want to set up VLAN 1 for my general home network, VLAN 2 for Internet/WiFi-connected gadgets, and VLAN 3 for IP camera system.
In the garage I have a managed switch with POE ports for cameras and also I want general network. So, for the trunk line that connects the router in the house to the switch in the garage, I will need to turn on VLAN 1 and VLAN 3 tagging to the ports used for the trunk line connection. As well, assign the access/device ports of the switch to the respective VLANs without tagging, then exclude any remaining ports I don't want on any given VLAN.
On the other hand, I will also have another managed POE switch in the house, but the trunk to that switch will only carry VLAN 3, so I do not need to set up tagging in that case. Taking it one step further (or perhaps backward) if I never had any requirement beyond VLAN 3 to this switch, it wouldn't even need to be a managed switch/have VLAN capability.
Correct so far?
Last edited: