svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
vlan(4)
To compile this driver into the kernel, place the following line
in your kernel configuration file: Alternatively, to load the
driver as a module at boot time, place the following line in
if_vlan_load="YES" The driver demultiplexes frames tagged accord‐
ing to the IEEE 802.1Q standard into logical network interfaces,
which allows routing/bridging between multiple VLANs through a
single switch trunk port. Each interface is created at runtime
using interface cloning. This is most easily done with the com‐
mand or using the variable in To function, a interface must be
assigned a parent interface and numeric VLAN tag using A single
parent can be assigned to multiple interfaces provided they have
different tags. The parent interface is likely to be an Ethernet
card connected to a properly configured switch port. The VLAN
tag should match one of those set up in the switched network.
initially assumes the same minimum length for tagged and untagged
frames. This mode is selected by setting the variable to 0 How‐
ever, there are network devices that fail to adjust frame length
when it falls below the allowed minimum due to untagging. Such
devices should be able to interoperate with after changing the
value of to 1. In the latter mode, will pad short frames before
tagging them so that their length is not less than the minimum
value after untagging by the non-compliant devices. The driver
supports efficient operation over parent interfaces that can pro‐
vide help in processing VLANs. Such interfaces are automatically
recognized by their capabilities. Depending on the level of so‐
phistication found in a physical interface, it may do full VLAN
processing or just be able to receive and transmit long frames
(up to 1522 bytes including an Ethernet header and FCS). The ca‐
pabilities may be user-controlled by the respective parameters to
and However, a physical interface is not obliged to react to
them: It may have either capability enabled permanently without a
way to turn it off. The whole issue is very specific to a par‐
ticular device and its driver. At present, these devices are ca‐
pable of full VLAN processing in hardware: and Other Ethernet in‐
terfaces can run VLANs using software emulation in the driver.
However, some lack the capability of transmitting and receiving
long frames. Assigning such an interface as the parent to will
result in a reduced MTU on the corresponding interfaces. In the
modern Internet, this is likely to cause connectivity problems
due to massive, inadequate filtering that breaks the Path MTU
Discovery mechanism. These interfaces natively support long
frames for and The driver automatically recognizes devices that
natively support long frames for use and calculates the appropri‐
ate frame MTU based on the capabilities of the parent interface.
Some other interfaces not listed above may handle long frames,
but they do not advertise this ability. The MTU setting on can
be corrected manually if used in conjunction with such a parent
interface.