|
|
| nero64 2005-01-05, 1:49 am |
| Like many things my book fails to explain this properly. Can anybody explain this in simplified terms. | |
| perfectionist 2005-01-21, 12:06 am |
| Ok, a quick and brief explanation.
Native VLAN exist only when you are using 802.1q intead of ISL. This is the default VLAN with a VLAN id of "1". Packets originating from this VLAN is not tagged with the 802.1q header, when it traverse across VLANs.
Hope you understand my explanation. | |
| nero64 2005-01-21, 1:34 am |
| So If there is a Vlan 1 as default then your always running dot 1q. But just say you don't have trunking enabled what is the deal then, because I didn't have trunking enabled and when I did show vlan it still has Vlan 1. | |
| JimmyD 2005-01-21, 1:53 am |
| quote:
Originally posted by perfectionist
Native VLAN exist only when you are using 802.1q intead of ISL.
That is actually backwards. In 802.1q, the native VLAN is always 1. ISL allows you to choose a "native" VLAN. | |
|
|
| perfectionist 2005-01-21, 4:57 am |
| quote:
So If there is a Vlan 1 as default then your always running dot 1q. But just say you don't have trunking enabled what is the deal then, because I didn't have trunking enabled and when I did show vlan it still has Vlan 1.
The default VLAN will be there regardless of the type of trunking protocol used. It will only behave as a native VLAN when you turn on 802.1q. In other words, the default VLAN will only become a native VLAN if u turn on 802.1q.
For your information, some people assign an ip address to the default VLAN so that they can ping the switch. | |
| darthfeces 2005-01-21, 5:31 pm |
| the difference is :
in isl
a frame received on an isl trunk that is not isl encapsulated is dropped.
in dot1q a frame received on a dot1q trunk that does not have a dot1q header (or encapsulated dot1q) is in the native vlan1.
default vlan1
can be reconfigured. |
|
|
|