Date: Wed, 25 Jul 2001 07:20:42 +0400 From: Yar Tikhiy <yar@freebsd.org> To: audit@freebsd.org Subject: vlan(4) manpage Message-ID: <20010725072042.A24573@comp.chem.msu.su>
next in thread | raw e-mail | index | archive | help
Hi there, It seems we don't have the vlan(4) manpage yet. Here's its first approximation. Please review it. Thank you. -- Yar .\" .\" $FreeBSD$ .\" .Dd July 25, 2001 .Dt VLAN 4 .Os .Sh NAME .Nm vlan .Nd IEEE 802.1Q VLAN network interface .Sh SYNOPSIS .Cd pseudo-device vlan Op Ar count .Sh DESCRIPTION The .Nm driver demultiplexes frames tagged according to the IEEE 802.1Q standard into logical .Nm network interfaces, which allows for routing/bridging between multiple VLANs through a single switch trunk port. .Pp To function, a .Nm interface must be assigned a parent interface and numeric VLAN tag using .Xr ifconfig 8 . A single parent can be assigned to multiple .Nm interfaces provided they have different tags. The parent interface is likely to be an ethernet one connected to a properly configured switch port. The VLAN tag should match one of those set up in the switched network. .Sh SEE ALSO .Xr ifconfig 8 .Sh BUGS Most ethernet NICs supported by FreeBSD lack the capability of transmitting and/or receiving oversized frames. Using such a NIC as a parent interface for .Nm implies reduced MTU on the corresponding .Nm interfaces. In the modern Internet, the latter is likely to cause .Xr tcp 4 connectivity problems due to massive, inadequate .Xr icmp 4 filtering that breaks the Path MTU Discovery mechanism. .Pp No 802.1Q features except VLAN tagging are implemented. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010725072042.A24573>