Vlan 1 is also the management vlan on switches that support management vlans.
Unmanaged switch vlan tags.
A lan can be divided into several vlans logically and only the hosts in a same vlan can communicate with each other.
What happens is when a trunk is confgured a header aka tag which varies in size depending on what encapsulation is used is added to the front of the a frame by doing this the destination knows which vlan it belongs when it arrives.
Neither will it have knowledge of what vlan is the native the only one on the trunk that is not tagged vlan.
So what would happen if one put it in on a trunk.
As the following figure shows the switch connects to two different groups.
In this case the switch will flood the frame to all other ports configured with vlan 10.
Running tags over a dumb switch just amounts to running multiple layer 3 on the layer 2 there is zero lack of.
Here are two configuration examples for 802 1q vlan.
The sender will send a frame with a vlan tag.
Well in my mind either the native vlan.
If all of the things plugged into an unmanaged switch are on the same vlan then you can do that.
You must add the lag to the vlan as a single unit.
For example a broadcast may be received on vlan 10.
For more information see what is a management vlan.
However if you have a mix of vlans on a switch it needs to be managed.
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.
What an unmanaged switch that doesn t understand vlan tags will do with frames which have vlan tags a trunk link is really undefined.
Here you can see this process in action.
Vlan virtual local area network is a technology that can solve broadcasting issues.
Can afford to get a 30 switch that can understand vlans.