Remove badly outdated information: FDDI and Token Ring are gone,

VLAN tags on transmitted packets have been visible to bpf since
the introduction of bpf_mtap_ether().  ok brad@, henning@

diff --git a/share/man/man4/vlan.4 b/share/man/man4/vlan.4
index 5ded911..a7ac246 100644 (file)
--- a/share/man/man4/vlan.4
+++ b/share/man/man4/vlan.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: vlan.4,v 1.39 2014/04/21 16:21:08 henning Exp $
+.\" $OpenBSD: vlan.4,v 1.40 2014/04/23 11:42:14 naddy Exp $
 .\"
 .\" Copyright (c) 2000 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -27,7 +27,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: April 21 2014 $
+.Dd $Mdocdate: April 23 2014 $
 .Dt VLAN 4
 .Os
 .Sh NAME
@@ -174,18 +174,3 @@ and
 .Re
 .Sh AUTHORS
 Originally wollman@freebsd.org.
-.Sh BUGS
-The 802.1Q specification allows for operation over FDDI and Token Ring
-as well as Ethernet.
-This driver only supports such operation with Ethernet devices.
-.Pp
-When the IFCAP_VLAN_HWTAGGING capability is set on the parent interface,
-.Nm
-does not participate in the actual tagging of Ethernet frames.
-It simply passes the vlan ID on to the parent interface for tagging on transmit.
-The vlan tagged packet is not actually visible to
-.Ox .
-Thus,
-.Xr bpf 4
-will show untagged packets on the parent interface, although frames
-are actually being transmitted with tags on the wire.