Unmanaged Switch Vlan Tags

As the following figure shows the switch connects to two different groups.

Unmanaged switch vlan tags.

Well in my mind either the native vlan. Neither will it have knowledge of what vlan is the native the only one on the trunk that is not tagged vlan. For example a broadcast may be received on vlan 10. You have two options either connect the ap directly to the 3560 or buy a managed switch as said.

So what would happen if one put it in on a trunk. Here you can see this process in action. What an unmanaged switch that doesn t understand vlan tags will do with frames which have vlan tags a trunk link is really undefined. If a port is a member of a link aggregation group lag or you plan to add it to a lag do not add it to a vlan or tag it individually.

Some switches will drop the frames as garbled some switches will pass them on as they are and some switches will strip the vlan tags. For more information see what is a management vlan. Running tags over a dumb switch just amounts to running multiple layer 3 on the layer 2 there is zero lack of. The receiving switch will see the vlan tag and if the vlan is allowed it will forward the frame as required.

Simply put the unmanaged switch would not be able to know what vlans it would or would not send over the link that might or might not be a trunk. Vlan 1 is also the management vlan on switches that support management vlans. Here are two configuration examples for 802 1q vlan. Vlan virtual local area network is a technology that can solve broadcasting issues.

Can afford to get a 30 switch that can understand vlans. In this case the switch will flood the frame to all other ports configured with vlan 10. The sender will send a frame with a vlan tag. A lan can be divided into several vlans logically and only the hosts in a same vlan can communicate with each other.

If all of the things plugged into an unmanaged switch are on the same vlan then you can do that.