The 802.1q standard introduces the concept of "native" vlan, that is a VLAN not tagged. If you put on the other side a switch with configured access port , the frames transmitted are not tagged and belongs to native vlan.
then i suppose since 802.1q doesnt tag the native vlan and the data goes untagged so i dont think the other switch will hav a problem understanding the data for native vlan,,,, as for other vlan since they r tagged i dont think they communicate unless both r trunk ports,,, plz correct me if im wrong,,,,
When you connect a 802.1 trunk and an access port, the following happens:
The access port transmits frames untagged. The dot1q port understands untagged frames and interprets them as frames from the native vlan and forwards them on the native vlan.
If you set the native vlan on the dot1q trunk to 5, then the traffic from the access port will be forwarded to vlan 5 by the switch with dot1q trunk port.
Vlan 0 can be used to tag frames with dot1p CoS information (in quality of service configurations with IP phones), when the intention is that the frames are forwarded on the same vlan where the specific access port is located.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.