forum.lissyara.su

Код: Выделить всё

Serv# ifconfig 
sis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=80008<VLAN_MTU,LINKSTATE>
	ether 4c:00:10:54:db:46
	inet 192.168.0.8 netmask 0xffffff00 broadcast 192.168.0.255
	inet 10.0.21.2 netmask 0xffffff80 broadcast 10.0.21.127
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8<VLAN_MTU>
	ether 00:50:fc:a1:91:9d
	inet 192.168.2.50 netmask 0xffffff00 broadcast 192.168.2.255
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
rl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8<VLAN_MTU>
	ether 4c:00:10:54:db:46
	inet 10.254.254.254 netmask 0xffffffff broadcast 10.254.254.254
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=3<RXCSUM,TXCSUM>
	inet 127.0.0.1 netmask 0xff000000 
vlan707: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	ether 4c:00:10:54:db:46
	inet 10.248.1.56 netmask 0xfffffff0 broadcast 10.248.1.63
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
	vlan: 707 parent interface: rl1

Код: Выделить всё

Serv# netstat -nr
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            *.*.*.*     UGS         0  8155362   tun0
10.0.21.0/25       link#1             U           0        0   sis0
10.0.21.2          link#1             UHS         0       78    lo0
10.248.0.0/16      10.0.21.1          UGS        20  5128355   sis0
10.248.1.0/24      10.0.21.1          UGS         4 16964443   sis0
10.248.1.48/28     link#12            U           1      179 vlan70
10.248.1.56        link#12            UHS         0       88    lo0
10.254.254.254     link#3             UHS         0        0    lo0 =>
10.254.254.254/32  link#3             U           0        0    rl1
*.*.*.*     link#7             UHS         0        0   tun0
127.0.0.1          link#5             UH          0      555    lo0
*.*.*.*     127.0.0.1          UH          0        0    lo0
192.168.0.0/24     192.168.0.8        U           3 36719826   sis0
192.168.0.8        link#1             UHS         0        4    lo0
192.168.0.199      127.0.0.1          UH          0        0    lo0
192.168.1.100      127.0.0.1          UH          1        0    lo0
192.168.2.0/24     link#2             U           0        5    rl0
192.168.2.50       link#2             UHS         0        0    lo0

Код: Выделить всё

10.248.1.0/24      10.0.21.1          UGS         4 16964443   sis0

Код: Выделить всё

cat /etc/rc.conf | grep infconfig

Код: Выделить всё

Serv# cat /etc/rc.conf | grep ifconfig
ifconfig_sis0="inet 192.168.0.8  netmask 255.255.255.0"
ifconfig_rl1_alias1="10.0.21.2 netmask 255.255.255.128"
ifconfig_vlan707="inet 10.248.1.56 netmask 255.255.255.240 vlan 707 vlandev rl1"
ifconfig_rl0="inet 192.168.2.50  netmask 255.255.255.0"

Код: Выделить всё

Serv# netstat -nr
Routing tables
Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            *.*.*.*      UGS         0 36830869   tun0
10.0.21.0/25       link#3             U           0        0    rl1
10.0.21.2          link#3             UHS         0        0    lo0
10.248.0.0/16      10.0.21.1          UGS         4 21201133    rl1
10.248.1.48/28     link#6             U           0        0 vlan70
10.248.1.56        link#6             UHS         0        0    lo0
127.0.0.1          link#5             UH          0     2776    lo0
*.*.*.*      link#7             UHS         0        0   tun0
*.*.*.*     127.0.0.1          UH          0        0    lo0
192.168.0.0/24     link#1             U           1 37796720   sis0
192.168.0.8        link#1             UHS         0        0    lo0

Код: Выделить всё

HARDWARE
     The vlan driver supports efficient operation over parent interfaces that
     can provide help in processing VLANs.  Such interfaces are automatically
     recognized by their capabilities.  Depending on the level of sophistica?
     tion 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 capabilities may be user-con?
     trolled by the respective parameters to ifconfig(8), vlanhwtag and
     vlanmtu.  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 particular device and its
     driver.

     By now, the list of physical interfaces able of full VLAN processing in
     the hardware is limited to the following devices: ae(4), age(4), alc(4),
     ale(4), bce(4), bge(4), cxgb(4), em(4), ixgb(4), jme(4), msk(4), nge(4),
     re(4), sge(4), stge(4), ti(4), txp(4), and vge(4).

     The rest of the Ethernet interfaces can run VLANs using software emula?
     tion in the vlan driver.  However, some of them lack the capability of
     transmitting and receiving long frames.  Assigning such an interface as
     the parent to vlan will result in a reduced MTU on the corresponding vlan
     interfaces.  In the modern Internet, this is likely to cause tcp(4) con?
     nectivity problems due to massive, inadequate icmp(4) filtering that
     breaks the Path MTU Discovery mechanism.

     The following interfaces support long frames for vlan natively: bfe(4),
     cas(4), dc(4), fwe(4), fxp(4), gem(4), hme(4), le(4), nfe(4), nve(4),
     rl(4), sf(4), sis(4), sk(4), ste(4), tl(4), tx(4), vr(4), and xl(4).

     The vlan driver automatically recognizes devices that natively support
     long frames for vlan use and calculates the appropriate 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 abil?
     ity of theirs.  The MTU setting on vlan can be corrected manually if used
     in conjunction with such a parent interface.

SEE ALSO
     ifconfig(8), sysctl(8)

BUGS
     No 802.1Q features except VLAN tagging are implemented.

FreeBSD 8.1                     April 14, 2010                     FreeBSD 8.1