|
|---|
|
|
|
|
|
|
x*********n
发帖数: 28013 | 1 看配置。
interface FastEthernet0/0.1
description *** Data VLAN ***
encapsulation dot1Q 1 native
ip address 198.233.36.65 255.255.255.224 secondary
ip address 192.168.25.1 255.255.255.0
ip nat inside
ip virtual-reassembly
no ip route-cache
!
interface FastEthernet0/0.2
description *** Voice VLAN ***
encapsulation dot1Q 2
ip address 192.168.32.1 255.255.255.0
ip mtu 1420
ip nat inside
ip virtual-reassembly
no ip route-cache
ip tcp adjust-mss 1380
!
interface FastEthernet0/0.3
description *** External Device VLAN ***
encapsulation dot1Q 3
ip address 192.168.158.1 255.255.255.0
ip mtu 1420
ip nat inside
ip virtual-reassembly
no ip route-cache
ip tcp adjust-mss 1380
shutdown
我的问题是，为啥有encapsulation dot1Q 1 native出现。可以理解1个circuit需要
tag一下才能区分traffic，但是802.1Q不是应该用在trunk，而trunk应该是switch和
switch之间的么？为啥router也行？
多谢指教。 | s*****g
发帖数: 1055 | 2 802.1q in Cisco's term is a trunk, it can be configured on a router or a
switch, on IOS router it is called sub-interface, on IOS switch it can
either be configured as sub-interfaces or VLANs. Each trunk has to have a
native VLAN which is not tagged, in your case the native VLAN is 1, you can
move interface FastEthernet0/0.1's configuration to physical interface F0/0
to have the same functionality. | x*********n
发帖数: 28013 | 3 多谢弯曲大侠啊。哈哈。原来是这样。
can
0
【在 s*****g 的大作中提到】
: 802.1q in Cisco's term is a trunk, it can be configured on a router or a
: switch, on IOS router it is called sub-interface, on IOS switch it can
: either be configured as sub-interfaces or VLANs. Each trunk has to have a
: native VLAN which is not tagged, in your case the native VLAN is 1, you can
: move interface FastEthernet0/0.1's configuration to physical interface F0/0
: to have the same functionality.
|
|
|
|
|
|
|
|
