2. If the data frame into the interface is the access interface, view the vlan tag of a data frame, and binding, receiving, if not, are not received, if there is no label, on the access port binding tag to the corresponding interface (receiving stage, inside the switch)
If data frame into the interface is the trunk interface, then check the vlan tag, of a data frame within the release list, release, not at, refused to accept, if not, then play on trunk mouth binding vlan tag (receiving stage, inside the switch)
3. If the Mac address for the purpose of a data frame switch of a pair of side (not the receiver), but data frame carry vlan tag (or after interface on the vlan tag) can't corresponding with switches on any vlan tag (or corresponding error), switches do not forward the data frame
4. If you receive the broadcast message (select) after receiving, view the vlan tag table, from all the binding to the same vlan tag the access port forwarding, if put in trunk at the mouth of the list of switches is the label, also from the trunk port forwarding, received ARP broadcast messages, for example, only to the relevant access ports and trunk transmission (with tag)
In the access, exchange opportunities to peel the label above, if the mouth binding on receiving end switches vlan tag, tag to the
When out of the trunk, not for stripping label operation, according to oneself circumstance to end switches (step 1, 2, 3) choose to accept or reject
Switches, for example, to send no label, the access type interface won't tag (access mouth out of traffic without any tags), trunk interface can play on the interface binding of vlan tag (if the client is a PC, the PC cannot identify, will not respond)
Based on the vlan tag choose whether to receive data frames is actually determined by the switch view vlan tags after table, not interface
Personal understanding, please correct me, every mistake, thank you (fuels)
CodePudding user response:
Your understanding is wrong