>Спасибо за оперативный ответ, но.... всё же (поподробней) каким образом я на
>Cisco 3508G должен настроить маршрутизацию. И что значит обучить сетевуху понимать
>VLAN.
Рассмотрю пример для FBSD станции:
компилишь я дро с поддержкой vlan:
man vlan
NAME
vlan -- IEEE 802.1Q VLAN network interface
SYNOPSIS
device miibus
device vlan
Ищешь там же интерфейс, который поддерживает организацию vlan на сетевухе:
The interfaces that support oversized frames are as follows:
bfe(4) supports long frames for vlan natively.
dc(4) supports long frames for vlan natively.
de(4) requires defining BIG_PACKET in the
/usr/src/sys/pci/if_de.c source file and rebuilding the
kernel or module. The hack works only for the 21041,
21140, and 21140A chips.
fxp(4) supports long frames for vlan natively.
hme(4) supports long frames for vlan natively.
rl(4) supports long frames for vlan natively.
sis(4) supports long frames for vlan natively.
ste(4) supports long frames for vlan natively.
tl(4) has support for long frames.
tx(4) supports long frames for vlan natively.
xl(4) supports long frames only if the card is built on a newer
chip (Cyclone and above).
Потом изучаем man ifconfig на vlan
man ifconfig
.....
vlan vlan_tag
If the interface is a vlan(4) pseudo interface, set the VLAN tag
value to vlan_tag. This value is a 16-bit number which is used
to create an 802.1Q VLAN header for packets sent from the vlan(4)
interface. Note that vlan and vlandev must both be set at the
same time.
vlandev iface
If the interface is a vlan(4) pseudo device, associate physical
interface iface with it. Packets transmitted through the vlan(4)
interface will be diverted to the specified physical interface
iface with 802.1Q VLAN encapsulation. Packets with 802.1Q encap-
sulation received by the parent interface with the correct VLAN
tag will be diverted to the associated vlan(4) pseudo-interface.
The vlan(4) interface is assigned a copy of the parent inter-
face's flags and the parent's ethernet address. The vlandev and
vlan must both be set at the same time. If the vlan(4) interface
already has a physical interface associated with it, this command
will fail. To change the association to another physical inter-
face, the existing association must be cleared first.
Note: if the hardware tagging capability is set on the parent
interface, the vlan(4) pseudo interface's behavior changes: the
vlan(4) interface recognizes that the parent interface supports
insertion and extraction of VLAN tags on its own (usually in
firmware) and that it should pass packets to and from the parent
unaltered.
-vlandev iface
If the driver is a vlan(4) pseudo device, disassociate the physi-
cal interface iface from it. This breaks the link between the
vlan(4) interface and its parent, clears its VLAN tag, flags and
its link address and shuts the interface down.
vlanmtu, vlanhwtag
If the driver offers user-configurable VLAN support, enable
reception of extended frames or tag processing in hardware,
respectively. Note that this must be issued on a physical inter-
face associated with vlan(4), not on a vlan(4) interface itself.
-vlanmtu, -vlanhwtag
If the driver offers user-configurable VLAN support, disable
reception of extended frames or tag processing in hardware,
respectively.
Настраиваем интерфейс и вуаля - комп может работать с двумя vlan-ами
Вариант для распечатки
OpenNET: Виртуальная конференция (Public)
(ok) on
15-Ноя-05, 11:48 (MSK)
