Vlan setup
Hi,
Before purchasing and implementing these switches into a VLAN setup. I wanted to confirm a couple of point.
In the photo below, the first switch port where the PC is connected to has a native network and an untagged network of 1 (LAN.) The trunk ports have the same Lan1 native network and untagged network but surely the PC has already been tagged by the first switch so now won't pass through the 'All' Profile as it does not have Lan in tagged? Or does it mean it untags everything not in the tagged list and retags again on the native network?
Also if my switches are on the subnet of the main Lan network, am I always going to have to allow the Lan network through for the switches to communicate?
Thankyou for the support.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Anthony1001
Thanks for posting in our business forum.
Anthony1001 wrote
In the photo below, the first switch port where the PC is connected to has a native network and an untagged network of 1 (LAN.) The trunk ports have the same Lan1 native network and untagged network but surely the PC has already been tagged by the first switch so now won't pass through the 'All' Profile as it does not have Lan in tagged? Or does it mean it untags everything not in the tagged list and retags again on the native network
The PC is not tagged because it is not using any tagged network based on your picture.
I think you first need to understand why there is a tag and untag. Please refer to the wiki of 802.1Q VLAN.
Native Networks on the Controller means PVID. Tagged and untagged network, the literal meaning of it.
I am having trouble understanding your questions. My apology. If you are creating VLAN interfaces, you have access to each VLAN interface because they are routed.
If you want to block, based on the VLAN interface scheme, use ACL.
If you are looking for the old-fashion way, the 802.1Q VLAN, for isolation, then configure it as VLAN for purpose. Don't use the VLAN interface as "purpose".
So, three profiles you have there. I'll just explain the first two.
#1 VLAN ID = LAN(untag), PVID = LAN, no tagged network. This is the profile and is usually for PC.
#2 VLAN ID = LAN(untag), Camera(tag), Guest(tag), PVID = LAN. This port will get an IP of LAN. If connected with a switch, the switch can further distribute VLAN Guest and Camera.
- Copy Link
- Report Inappropriate Content
Hi @Anthony1001
Thanks for posting in our business forum.
Anthony1001 wrote
In the photo below, the first switch port where the PC is connected to has a native network and an untagged network of 1 (LAN.) The trunk ports have the same Lan1 native network and untagged network but surely the PC has already been tagged by the first switch so now won't pass through the 'All' Profile as it does not have Lan in tagged? Or does it mean it untags everything not in the tagged list and retags again on the native network
The PC is not tagged because it is not using any tagged network based on your picture.
I think you first need to understand why there is a tag and untag. Please refer to the wiki of 802.1Q VLAN.
Native Networks on the Controller means PVID. Tagged and untagged network, the literal meaning of it.
I am having trouble understanding your questions. My apology. If you are creating VLAN interfaces, you have access to each VLAN interface because they are routed.
If you want to block, based on the VLAN interface scheme, use ACL.
If you are looking for the old-fashion way, the 802.1Q VLAN, for isolation, then configure it as VLAN for purpose. Don't use the VLAN interface as "purpose".
So, three profiles you have there. I'll just explain the first two.
#1 VLAN ID = LAN(untag), PVID = LAN, no tagged network. This is the profile and is usually for PC.
#2 VLAN ID = LAN(untag), Camera(tag), Guest(tag), PVID = LAN. This port will get an IP of LAN. If connected with a switch, the switch can further distribute VLAN Guest and Camera.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 428
Replies: 1
Voters 0
No one has voted for it yet.