[Midnightbsd-cvs] src: man/man4: add nfe(4), zyd(4).
laffer1 at midnightbsd.org
laffer1 at midnightbsd.org
Wed Dec 10 12:54:41 EST 2008
Log Message:
-----------
add nfe(4), zyd(4). Remove kame and worm as the former is complete and the latter never existed in MidnightBSD.
Modified Files:
--------------
src/share/man/man4:
Makefile (r1.8 -> r1.9)
ipfirewall.4 (r1.1.1.1 -> r1.2)
ipsec.4 (r1.2 -> r1.3)
isp.4 (r1.1.1.2 -> r1.2)
ispfw.4 (r1.1.1.1 -> r1.2)
iwi.4 (r1.1.1.2 -> r1.2)
ixgb.4 (r1.1.1.1 -> r1.2)
joy.4 (r1.1.1.1 -> r1.2)
kbdmux.4 (r1.2 -> r1.3)
xe.4 (r1.1.1.2 -> r1.2)
xl.4 (r1.1.1.2 -> r1.2)
Added Files:
-----------
src/share/man/man4:
nfe.4 (r1.1)
zyd.4 (r1.1)
Removed Files:
-------------
src/share/man/man4:
kame.4
worm.4
-------------- next part --------------
--- share/man/man4/kame.4
+++ /dev/null
@@ -1,206 +0,0 @@
-.\" Copyright (C) 1995, 1996, 1997, 1998 and 1999 WIDE Project.
-.\" All rights reserved.
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\" 3. Neither the name of the project nor the names of its contributors
-.\" may be used to endorse or promote products derived from this software
-.\" without specific prior written permission.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
-.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-.\" ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
-.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
-.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
-.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
-.\" SUCH DAMAGE.
-.\"
-.\" $Id: kame.4,v 1.4 1999/10/07 04:01:15 itojun Exp $
-.\" $FreeBSD: src/share/man/man4/kame.4,v 1.14 2005/02/09 18:07:16 ru Exp $
-.\"
-.Dd April 13, 1999
-.Dt KAME 4
-.Os
-.Sh NAME
-.Nm KAME
-.Nd introduction and roadmap to KAME IPv6 software package
-.Sh DESCRIPTION
-.Nm
-software package is a result of joint work of several IPv6 researchers
-in Japan, to provide reference implementation of IPv6 to
-Berkeley Software Distribution
-.Pq Bx
-derived system such as
-.Bsx ,
-.Fx ,
-.Nx
-and
-.Ox
-(in alphabetical order).
-.Pp
-.\" Package consists of set of patches and additions to kernel,
-.\" modification to application, daemons, header files and libraries.
-KAME kit consists of IPv6/IPsec-ready kernel, application, daemons,
-header files and libraries.
-.Sh HIGHLIGHTS
-Following are some of highlights of this implementation.
-.Pp
-Note: features not yet integrated into
-.Fx
-are marked with the
-.Pq -
-sign.
-.\"
-.Ss Kernel
-IPv6 and IPsec protocol stacks are implemented and available.
-See below for conformance to standards and/or internet drafts.
-.\"
-.Ss Plug and Play and protocol stack/interface configuration
-.Xr ndp 8 ,
-.Xr rrenumd 8 ,
-.Xr rtadvd 8 ,
-.Xr rtsol 8 ,
-.Xr rtsold 8 .
-.\"
-.Ss Routing
-.Xr rip6query 8 ,
-.Xr route6d 8 .
-.\"
-.Ss Multicast (includes routing and utilities)
-.Xr mchat 1
-.Pq - ,
-.Xr ifmcstat 8 ,
-.Xr pim6dd 8 Pq Pa ports/net/pim6dd ,
-.Xr pim6sd 8 Pq Pa ports/net/pim6sd ,
-.Xr pim6stat 8 .
-.\"
-.Ss Transition Tools
-Two IPv4 to IPv6 transition tools are available.
-TCP relay translator, FAITH
-.Pq Xr faithd 8
-and SIIT IPv6-to-v4 header translator implementation
-.Pq Xr ptrconfig 8 .
-.Xr ptrconfig 8
-is not yet integrated into
-.Fx .
-.\"
-.Ss IPsec and tunnelling
-.Xr ipsec 4 ,
-.Xr racoon 8 Pq Pa ports/security/racoon ,
-.Xr setkey 8 .
-.Pp
-Dozen of existing tools are modified for IPsec support, like
-.Xr ping 8 .
-.\"
-.Ss Utilities/Diagnosis
-.Xr v6test 1
-.Pq - ,
-.Xr ping6 8 ,
-.Xr traceroute6 8 .
-.Pp
-Dozen of existing utilities are modified for IPv6/IPsec support, like
-.Xr ftp 1
-and/or
-.Xr telnet 1 .
-.\"
-.Ss Application Daemons
-.Xr inetd 8
-modified for IPv4/v6 support, or
-IPv6-only
-.Xr inet6d 8
-.Pq -
-is supplied.
-.Pp
-Dozen of existing daemons are modified for IPv6/IPsec support, like
-.Xr ftpd 8
-and/or
-.Xr telnetd 8 .
-.\"
-.Sh DOCUMENTATION
-Although some of documentations have not modified yet, program itself
-may be heavily modified.
-Following lists are not complete, but give you some idea what kind of
-new software modules are available, or, modifications are made.
-Please refer to each manual page for detail.
-.\"
-.Ss Installation and basic usage documentations
-Please read the following files in the directories
-.Pa /usr/share/doc/IPv6
-and
-.Pa /usr/share/examples/IPv6
-to get a basic idea of (and installation methods for
-.Nm .
-You also can check out the IPv6 and IPsec chapters in the
-.Fx
-handbook.
-Also check latest status of project at web page:
-.Pa http://www.kame.net/ .
-(Hope you can see a
-.Dq Dancing Turtle
-.Li :-) )
-.\"
-.Ss APIs introduced or modified
-.Xr if_indextoname 3 ,
-.Xr getipnodebyname 3 ,
-.Xr gethostbyname 3 ,
-.Xr rresvport_af 3 ,
-.Xr hosts_ctl 3 ,
-.Xr ipsec_get_policylen 3 ,
-.Xr getnameinfo 3 ,
-.Xr freeaddrinfo 3 ,
-.Xr getaddrinfo 3 ,
-.Xr pcap 3 ,
-.Xr getipnodebyaddr 3 ,
-.Xr resolver 3 ,
-.Xr ipsec_strerror 3 ,
-.Xr gai_strerror 3 ,
-.Xr hosts_access 3 ,
-.Xr request_set 3 ,
-.Xr request_init 3 ,
-.Xr freehostent 3 ,
-.Xr if_nameindex 3 ,
-.Xr if_freenameindex 3 ,
-.Xr if_nametoindex 3 ,
-.Xr ipsec_dump_policy 3 ,
-.Xr ipsec_set_policy 3
-.\"
-.Ss Added/modified/renamed features and tools
-Please consult the manpages referred above.
-.\"
-.Sh SEE ALSO
-To understand
-.Nm
-protocol stack conformance, please refer to
-.Pa /usr/share/doc/IPv6/IMPLEMENTATION .
-.Pp
-Bug reporting form, user mailing list, frequently asked questions list,
-latest packages, related software, and more information can be found at
-.Pa http://www.kame.net/ .
-.\"
-.Ss "Related project"
-TAHI project who is providing verification technology for IPv6, is
-heavily related with KAME project.
-You can get current verification
-status of KAME software at following TAHI project web page:
-.Pa http://www.tahi.org/
-.\"
-.Sh HISTORY
-The
-.Nm
-project started in April 1999.
-.Nm
-kit was mostly integrated into
-.Fx
-by
-.An Youshinobu Inoue Aq shin at FreeBSD.org
-in January 2000.
Index: isp.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/isp.4,v
retrieving revision 1.1.1.2
retrieving revision 1.2
diff -L share/man/man4/isp.4 -L share/man/man4/isp.4 -u -r1.1.1.2 -r1.2
--- share/man/man4/isp.4
+++ share/man/man4/isp.4
@@ -27,19 +27,29 @@
.\"
.\" Additional Copyright (c) 2006 by Marcus Alves Grando
.\"
-.\" $FreeBSD: src/share/man/man4/isp.4,v 1.20.2.1 2006/02/07 22:01:59 mjacob Exp $
+.\" $FreeBSD: src/share/man/man4/isp.4,v 1.26 2007/03/01 09:07:04 brueffer Exp $
.\"
-.Dd February 6, 2006
+.Dd February 28, 2007
.Dt ISP 4
.Os
.Sh NAME
.Nm isp
.Nd Qlogic based SCSI and FibreChannel SCSI Host Adapters
.Sh SYNOPSIS
+To compile this driver into the kernel,
+place the following lines in your
+kernel configuration file:
+.Bd -ragged -offset indent
+.Cd "device scbus"
.Cd "device isp"
+.Ed
.Pp
-For one or more SCSI busses:
-.Cd device scbus0
+Alternatively, to load the driver as a
+module at boot time, place the following line in
+.Xr loader.conf 5 :
+.Bd -literal -offset indent
+isp_load="YES"
+.Ed
.Sh DESCRIPTION
This driver provides access to
.Tn SCSI
@@ -59,19 +69,24 @@
3 only, minor patches to the Qlogic 2200 to force Class 2 mode).
Support is available for Public and Private loops, and for
point-to-point connections (Qlogic 2200 only).
-The newer 2-Gigabit cards (2300, 2312) are also supported.
+The newer 2-Gigabit cards (2300, 2312, 2322) and 4-Gigabit (2422, 2432)
+are also supported.
Command tagging is
supported for all (in fact,
.Tn FibreChannel
requires tagging).
-Fabric support is enabled by default (but may
-be contingent upon the correct firmware being loaded).
+Fabric support is enabled by default for other than 2100 cards.
+Fabric
+support for 2100 cards has been so problematic and these cards are so
+old now that it is just not worth your time to try it.
.Sh FIRMWARE
-Firmware is now available if the
+Firmware is available if the
.Xr ispfw 4
module is loaded during bootstrap (q.v.).
.Pp
-It is very strongly recommended that you use the firmware available
+It is
+.Ar strongly
+recommended that you use the firmware available
from
.Xr ispfw 4
as it is the most likely to have been tested with this driver.
@@ -115,9 +130,13 @@
.It Qlogic 234X
Qlogic 234X Optical Fibre Channel PCI cards (2312 chipset, single and dual attach).
.It Qlogic 2322
-Qlogic 2322 Optical Fibre Channel PCI cards.
+Qlogic 2322 Optical Fibre Channel PCIe cards.
.It Qlogic 200
Dell Branded version of the QLogic 2312 Fibre Channel PCI cards.
+.It Qlogic 2422
+Qlogic 2422 Optical Fibre Channel PCI cards (4 Gigabit)
+.It Qlogic 2432
+Qlogic 2432 Optical Fibre Channel PCIe cards (4 Gigabit)
.El
.Sh CONFIGURATION OPTIONS
.Pp
@@ -131,40 +150,37 @@
.Pa /boot/device.hints .
.Pp
They are:
-.Pp
.Bl -tag -width indent
.It Va hint.isp.0.disable
A hint value to disable driver in kernel.
-.It Va hint.iso.0.fwload_disable
+.It Va hint.isp.0.fwload_disable
A hint value to disable loading of firmware
-.Cd ispfw(4) .
+.Xr ispfw 4 .
.It Va hint.isp.0.prefer_memmap
-A hint value to use PCI Memory space instead of I/O space
+A hint value to use PCI memory space instead of I/O space
access for.
.It Va hint.isp.0.prefer_iomap
A hint value to use PCI I/O space instead of Memory space
access for.
.It Va hint.isp.0.ignore_nvram
-A hint value to ignore board NVRAM settings for. Otherwise
-use NVRAM settings.
+A hint value to ignore board NVRAM settings for.
+Otherwise use NVRAM settings.
.It Va hint.isp.0.fullduplex
A hint value to set full duplex mode.
.It Va hint.isp.0.topology
-A hint value to select topology of connection. Supported
-values are:
-.Pp
-.Cd lport
-(Prefer loopback and fallback to point to point).
-.Pp
-.Cd nport
-(Prefer point to point and fallback to loopback).
-.Pp
-.Cd lport-only
-(Loopback only).
-.Pp
-.Cd nport-only
-(Point to point only).
+A hint value to select topology of connection.
+Supported values are:
.Pp
+.Bl -tag -width ".Li lport-only" -compact
+.It Li lport
+Prefer loopback and fallback to point to point.
+.It Li nport
+Prefer point to point and fallback to loopback.
+.It Li lport-only
+Loopback only.
+.It Li nport-only
+Point to point only.
+.El
.It Va hint.isp.0.portwwn
This should be the full 64 bit World Wide Port Name you would like
to use, overriding the value in NVRAM for the card.
@@ -172,12 +188,36 @@
This should be the full 64 bit World Wide Node Name you would like
to use, overriding the value in NVRAM for the card.
.It Va hint.isp.0.iid
-A hint to override or set the Initiator ID (principally for SPI SCSI).
+A hint to override or set the Initiator ID or Loop ID.
+For Fibre Channel
+cards in Local Loop topologies it is
+.Ar strongly
+recommended that you set this value to non-zero.
.It Va hint.isp.0.role
A hint to define default role for isp instance (target, initiator, both).
.It Va hint.isp.0.debug
-A hint value for a driver debug level (values from 0 through 7).
-Default is 0.
+A hint value for a driver debug level (see the file
+.Pa /usr/src/sys/dev/isp/ispvar.h
+for the values.
+.El
+.Sh SYSCTL OPTIONS
+.Pp
+.Bl -tag -width indent
+.It Va dev.isp.N.loop_down_limit
+This value says how long to wait in seconds after loop has gone down before
+giving up and expiring all of the devices that were visible.
+The default is 300 seconds (5 minutes).
+A seperate (nonadjustable) timeout is used when
+booting to not stop booting on lack of FC connectivity.
+.It Va dev.isp.N.gone_device_time
+This value says how long to wait for devices to reappear if they (temporarily)
+disappear due to loop or fabric events.
+While this timeout is running, I/O
+to those devices will simply be held.
+.It Va dev.isp.N.wwnn
+This is the readonly World Wide Node Name value for this port.
+.It Va dev.isp.N.wwpn
+This is the readonly World Wide Port Name value for this port.
.El
.Sh SEE ALSO
.Xr da 4 ,
@@ -188,28 +228,13 @@
.Sh AUTHORS
The
.Nm
-driver was written by Matthew Jacob for NASA/Ames Research Center.
+driver was written by Matthew Jacob originally for NetBSD at
+NASA/Ames Research Center.
.Sh BUGS
The driver currently ignores some NVRAM settings.
.Pp
-The driver currently does not do error recovery for timed out commands
-very gracefully.
-.Pp
-Target mode support is not completely debugged yet.
+Target mode support is not completely reliable yet.
It works reasonably
well for Fibre Channel, somewhat well for Qlogic 1040 cards, but
does not yet work for the other cards (due to last minute unannounced
changes in firmware interfaces).
-.Pp
-Sometimes, when booting, the driver gets stuck waiting for the
-Fibre Channel f/w to tell it that the loop port database is ready,
-or waiting for a good loop to be seen (this does not yet support
-booting without being connected to a fibre channel device).
-To
-unwedge the system, unplug and replug the fibre channel connection,
-or otherwise cause a LIP (Loop Initialization Primitive sequence)-
-this will kick the f/w into getting unstuck.
-.Pp
-QLogic 2322 support is limited to platforms where the BIOS can
-enable firmware as there is no code yet to do the 3 stage loading
-for 2322 firmware.
--- /dev/null
+++ share/man/man4/zyd.4
@@ -0,0 +1,205 @@
+.\" $OpenBSD: zyd.4,v 1.22 2007/05/24 02:49:57 cnst Exp $
+.\" $NetBSD: zyd.4,v 1.1 2007/06/09 11:20:55 kiyohara Exp $
+.\" $FreeBSD: src/share/man/man4/zyd.4,v 1.3 2007/09/06 20:13:27 brueffer Exp $
+.\"
+.\" Copyright (c) 1997, 1998, 1999
+.\" Bill Paul <wpaul at ctr.columbia.edu>. All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\" notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\" notice, this list of conditions and the following disclaimer in the
+.\" documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\" must display the following acknowledgement:
+.\" This product includes software developed by Bill Paul.
+.\" 4. Neither the name of the author nor the names of any co-contributors
+.\" may be used to endorse or promote products derived from this software
+.\" without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
+.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
+.\" THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd September 6, 2007
+.Dt ZYD 4
+.Os
+.Sh NAME
+.Nm zyd
+.Nd ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network device
+.Sh SYNOPSIS
+To compile this driver into the kernel,
+place the following lines in your
+kernel configuration file:
+.Bd -ragged -offset indent
+.Cd "device ehci"
+.Cd "device uhci"
+.Cd "device ohci"
+.Cd "device usb"
+.Cd "device zyd"
+.Cd "device wlan"
+.Cd "device wlan_amrr"
+.Ed
+.Pp
+Alternatively, to load the driver as a
+module at boot time, place the following line in
+.Xr loader.conf 5 :
+.Bd -literal -offset indent
+if_zyd_load="YES"
+.Ed
+.Sh DESCRIPTION
+The
+.Nm
+driver provides support for wireless network adapters based around
+the ZyDAS ZD1211 and ZD1211B USB chips.
+.Pp
+These are the modes the
+.Nm
+driver can operate in:
+.Bl -tag -width "IBSS-masterXX"
+.It BSS mode
+Also known as
+.Em infrastructure
+mode, this is used when associating with an access point, through
+which all traffic passes.
+This mode is the default.
+.It monitor mode
+In this mode the driver is able to receive packets without
+associating with an access point.
+This disables the internal receive filter and enables the card to
+capture packets from networks which it wouldn't normally have access to,
+or to scan for access points.
+.El
+.Pp
+.Nm
+supports software WEP.
+Wired Equivalent Privacy (WEP) is the de facto encryption standard
+for wireless networks.
+It can be typically configured in one of three modes:
+no encryption; 40-bit encryption; or 104-bit encryption.
+Unfortunately, due to serious weaknesses in WEP protocol
+it is strongly recommended that it not be used as the
+sole mechanism to secure wireless communication.
+WEP is not enabled by default.
+.Sh HARDWARE
+The following devices are known to be supported by the
+.Nm
+driver:
+.Pp
+.Bl -tag -width Ds -offset indent -compact
+.It 3COM 3CRUSB10075
+.It Acer WLAN-G-US1
+.It Airlink+ AWLL3025
+.It Airlink 101 AWLL3026
+.It AOpen 802.11g WL54
+.It Asus A9T integrated wirless
+.It Asus WL-159g
+.It Belkin F5D7050 v.4000
+.It Billion BiPAC 3011G
+.It Buffalo WLI-U2-KG54L
+.It CC&C WL-2203B
+.It DrayTek Vigor 550
+.It Edimax EW-7317UG
+.It Edimax EW-7317LDG
+.It Fiberline Networks WL-43OU
+.It iNexQ UR055g
+.It Linksys WUSBF54G
+.It Longshine LCS-8131G3
+.It MSI US54SE
+.It Philips SNU5600
+.It Planet WL-U356
+.It Planex GW-US54GZ
+.It Planex GW-US54GZL
+.It Planex GW-US54Mini
+.It Safecom SWMULZ-5400
+.It Sagem XG 760A
+.It Sagem XG 76NA
+.It Sandberg Wireless G54 USB
+.It Sitecom WL-113
+.It SMC SMCWUSB-G
+.It Sweex wireless USB 54 Mbps
+.It Tekram/Siemens USB adapter
+.It Telegent TG54USB
+.It Trendnet TEW-424UB
+.It Trendnet TEW-429UB
+.It TwinMOS G240
+.It Unicorn WL-54G
+.It US Robotics 5423
+.It X-Micro XWL-11GUZX
+.It Yakumo QuickWLAN USB
+.It Zonet ZEW2501
+.It ZyXEL ZyAIR G-220
+.El
+.Sh EXAMPLES
+The following
+examples configures zyd0 to join whatever network is available on boot,
+using WEP key
+.Dq 0x1deadbeef1 ,
+channel 11:
+.Bd -literal -offset indent
+inet 192.168.1.1 netmask 255.255.255.0 wepkey 0x1deadbeef1 channel 11
+.Ed
+.Pp
+Configure zyd0 for WEP, using hex key
+.Dq 0x1deadbeef1 :
+.Bd -literal -offset indent
+# ifconfig zyd0 wepkey 0x1deadbeef1
+.Ed
+.Pp
+Join an existing BSS network,
+.Dq my_net :
+.Bd -literal -offset indent
+# ifconfig zyd0 192.168.0.2 netmask 0xffffff00 ssid my_net
+.Ed
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "zyd%d: could not load firmware (error=%d)"
+An error occurred while attempting to upload the firmware to the onboard
+microcontroller unit.
+.It "zyd%d: could not send command (error=%s)"
+An attempt to send a command to the firmware failed.
+.It "zyd%d: sorry, radio %s is not supported yet"
+Support for the specified radio chip is not yet implemented in the driver.
+The device will not attach.
+.It "zyd%d: device version mismatch: 0x%x (only >= 43.30 supported)"
+Early revisions of the ZD1211 chipset are not supported by this driver.
+The device will not attach.
+.It "zyd%d: device timeout"
+A frame dispatched to the hardware for transmission did not complete in time.
+The driver will reset the hardware.
+This should not happen.
+.El
+.Sh SEE ALSO
+.Xr arp 4 ,
+.Xr intro 4 ,
+.Xr netintro 4 ,
+.Xr usb 4 ,
+.Xr wlan 4 ,
+.Xr wlan_amrr 4 ,
+.Xr ifconfig 8
+.Sh AUTHORS
+.An -nosplit
+The
+.Nm
+driver was written by
+.An Florian Stoehr Aq ich at florian-stoehr.de ,
+.An Damien Bergamini Aq damien at openbsd.org ,
+and
+.An Jonathan Gray Aq jsg at openbsd.org .
+.Sh CAVEATS
+The
+.Nm
+driver does not support a lot of the functionality available in the hardware.
+More work is required to properly support the IBSS and power management
+features.
Index: kbdmux.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/kbdmux.4,v
retrieving revision 1.2
retrieving revision 1.3
diff -L share/man/man4/kbdmux.4 -L share/man/man4/kbdmux.4 -u -r1.2 -r1.3
--- share/man/man4/kbdmux.4
+++ share/man/man4/kbdmux.4
@@ -1,14 +1,14 @@
.\" $Id: kbdmux.4,v 1.1 2005/07/14 20:32:10 max Exp $
-.\" $FreeBSD: src/share/man/man4/kbdmux.4,v 1.1.2.3 2006/03/04 00:08:20 emax Exp $
+.\" $FreeBSD: src/share/man/man4/kbdmux.4,v 1.5 2006/05/17 09:33:06 phk Exp $
.\"
.Dd July 12, 2005
.Os
-.Dt kbdmux 4
+.Dt KBDMUX 4
.Sh NAME
.Nm kbdmux
-.Nd keyboard multiplexer
+.Nd "keyboard multiplexer"
.Sh SYNOPSIS
-.Cd device kbdmux
+.Cd "device kbdmux"
.Pp
In
.Pa /boot/device.hints :
@@ -18,8 +18,10 @@
.Nm
keyboard driver provides support for basic keyboard multiplexing.
It is built around the idea of a
-.Dq super keyboard .
+.Dq "super keyboard" .
+The
.Nm
+driver
acts as a master keyboard consuming input from all slave keyboards attached to
it.
.Pp
@@ -31,7 +33,6 @@
.Sh SEE ALSO
.Xr kbdcontrol 1 ,
.Xr atkbd 4 ,
-.Xr pcvt 4 ,
.Xr syscons 4 ,
.Xr ukbd 4
.Sh CAVEATS
Index: ixgb.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/ixgb.4,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -L share/man/man4/ixgb.4 -L share/man/man4/ixgb.4 -u -r1.1.1.1 -r1.2
--- share/man/man4/ixgb.4
+++ share/man/man4/ixgb.4
@@ -29,26 +29,35 @@
.\"
.\" * Other names and brands may be claimed as the property of others.
.\"
-.\" $FreeBSD: src/share/man/man4/ixgb.4,v 1.9 2005/01/02 18:26:13 krion Exp $
+.\" $FreeBSD: src/share/man/man4/ixgb.4,v 1.11 2006/08/29 19:15:59 brueffer Exp $
.\"
-.Dd November 24, 2004
+.Dd August 18, 2006
.Dt IXGB 4
.Os
.Sh NAME
.Nm ixgb
.Nd "Intel(R) PRO/10GbE Ethernet driver for the FreeBSD operating system"
.Sh SYNOPSIS
+To compile this driver into the kernel,
+place the following line in your
+kernel configuration file:
+.Bd -ragged -offset indent
.Cd "device ixgb"
+.Ed
+.Pp
+Alternatively, to load the driver as a
+module at boot time, place the following line in
+.Xr loader.conf 5 :
+.Bd -literal -offset indent
+if_ixgb_load="YES"
+.Ed
.Sh DESCRIPTION
The
.Nm
-driver provides support for PCI gigabit Ethernet adapters based on
+driver provides support for PCI Gigabit Ethernet adapters based on
the Intel 82597EX Ethernet controller chips.
The driver supports Transmit/Receive checksum offload
and Jumbo Frames.
-For a list of supported adapters, see the
-.Pa README
-included with the driver.
.Pp
For questions related to hardware requirements,
refer to the documentation supplied with your Intel PRO/10GbE adapter.
@@ -62,8 +71,8 @@
The maximum MTU size for Jumbo Frames is 16114.
.Pp
This driver version supports VLANs.
-For information on enabling VLANs, see the
-.Pa README .
+For information on enabling VLANs, see
+.Xr ifconfig 8 .
.Sh HARDWARE
The
.Nm
@@ -86,10 +95,6 @@
the network connection (cable).
.El
.Sh SUPPORT
-For additional information regarding building and installation,
-see the
-.Pa README
-included with the driver.
For general information and support,
go to the Intel support website at:
.Pa http://support.intel.com .
Index: ispfw.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/ispfw.4,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -L share/man/man4/ispfw.4 -L share/man/man4/ispfw.4 -u -r1.1.1.1 -r1.2
--- share/man/man4/ispfw.4
+++ share/man/man4/ispfw.4
@@ -20,7 +20,7 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.\" $FreeBSD: src/share/man/man4/ispfw.4,v 1.6 2005/02/09 18:07:16 ru Exp $
+.\" $FreeBSD: src/share/man/man4/ispfw.4,v 1.7 2006/05/20 09:39:28 brueffer Exp $
.\"
.Dd July 20, 2000
.Dt ISPFW 4
@@ -29,7 +29,19 @@
.Nm ispfw
.Nd "Firmware Module for Qlogic based SCSI and FibreChannel SCSI Host Adapters"
.Sh SYNOPSIS
+To compile this driver into the kernel,
+place the following line in your
+kernel configuration file:
+.Bd -ragged -offset indent
.Cd "device ispfw"
+.Ed
+.Pp
+Alternatively, to load the driver as a
+module at boot time, place the following line in
+.Xr loader.conf 5 :
+.Bd -literal -offset indent
+ispfw_load="YES"
+.Ed
.Sh DESCRIPTION
This trivial driver provides access to firmware sets for the Qlogic
based SCSI and FibreChannel SCSI Host Adapters.
--- share/man/man4/worm.4
+++ /dev/null
@@ -1,110 +0,0 @@
-.\"
-.\" Copyright (C) 1996
-.\" interface business GmbH
-.\" Tolkewitzer Strasse 49
-.\" D-01277 Dresden
-.\" F.R. Germany
-.\"
-.\" All rights reserved.
-.\"
-.\" Written by Joerg Wunsch <joerg_wunsch at interface-business.de>
-.\"
-.\"
-.\" Redistribution and use in source and binary forms, with or without
-.\" modification, are permitted provided that the following conditions
-.\" are met:
-.\" 1. Redistributions of source code must retain the above copyright
-.\" notice, this list of conditions and the following disclaimer.
-.\" 2. Redistributions in binary form must reproduce the above copyright
-.\" notice, this list of conditions and the following disclaimer in the
-.\" documentation and/or other materials provided with the distribution.
-.\"
-.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR(S) ``AS IS'' AND ANY
-.\" EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR(S) BE LIABLE
-.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
-.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
-.\" OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
-.\" BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-.\" LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
-.\" USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
-.\" DAMAGE.
-.\"
-.\" $FreeBSD: src/share/man/man4/worm.4,v 1.29 2005/02/13 22:25:17 ru Exp $
-.\" "
-.Dd October 15, 1998
-.Dt WORM 4
-.Os
-.Sh NAME
-.Nm worm
-.Nd write-once (CD-R) disk driver
-.Sh SYNOPSIS
-None.
-.Sh DESCRIPTION
-The
-.Nm
-driver was provided under
-.Fx
-releases prior to
-.Fx 3.0 .
-.Pp
-The
-.Fx
-.Tn SCSI
-layer was replaced for
-.Fx 3.0
-by a CAM-compliant
-.Tn SCSI
-layer.
-The new
-.Tn SCSI
-layer does not include a
-.Nm
-driver, and is not likely to include one in the future.
-Future in-kernel
-support for CD-R/CD-RW/DVD drives will likely be implemented through the
-.Xr cd 4
-driver.
-Users who wish to write CDs on a WORM, CD-R, or CD-RW drive should use
-.Nm cdrtools ,
-which is in the
-.Fx
-ports collection.
-.Pp
-The
-.Xr cd 4
-driver provides read-only access to CD, CD-R, and CD-RW drives, as well as
-WORM drives that support the CDROM command set.
-Therefore, users wishing to mount CDs in a WORM drive should use the
-.Xr cd 4
-driver instead.
-.Sh SEE ALSO
-.Xr close 2 ,
-.Xr ioctl 2 ,
-.Xr open 2 ,
-.Xr write 2 ,
-.Xr cd 4 ,
-.Xr pass 4 ,
-.Xr xpt 4
-.Sh HISTORY
-The
-.Nm
-driver appeared in
-.Fx 2.1 ,
-and disappeared in
-.Fx 3.0
-with the advent of the CAM
-.Tn SCSI
-layer.
-.Sh AUTHORS
-.An -nosplit
-The first skeleton for a
-.Nm
-driver has been written by
-.An Peter Dufault
-in May, 1995.
-The driver has then been improved and made actually usable at all by
-.An J\(:org Wunsch
-in January, 1996.
--- /dev/null
+++ share/man/man4/nfe.4
@@ -0,0 +1,195 @@
+.\" $OpenBSD: nfe.4,v 1.7 2006/02/28 08:13:47 jsg Exp $
+.\"
+.\" Copyright (c) 2006 Jonathan Gray <jsg at openbsd.org>
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.\" $FreeBSD: src/share/man/man4/nfe.4,v 1.8.2.1 2007/12/02 08:45:57 remko Exp $
+.\"
+.Dd Nov 27, 2007
+.Dt NFE 4
+.Os
+.Sh NAME
+.Nm nfe
+.Nd "NVIDIA nForce MCP Ethernet driver"
+.Sh SYNOPSIS
+To compile this driver into the kernel,
+place the following lines in your
+kernel configuration file:
+.Bd -ragged -offset indent
+.Cd "device miibus"
+.Cd "device nfe"
+.Ed
+.Pp
+Alternatively, to load the driver as a
+module at boot time, place the following line in
+.Xr loader.conf 5 :
+.Bd -literal -offset indent
+if_nfe_load="YES"
+.Ed
+.Sh DESCRIPTION
+The
+.Nm
+driver supports PCI Ethernet adapters based on the NVIDIA
+nForce Media and Communications Processors (MCP), such as
+the nForce, nForce 2, nForce 3, CK804, MCP04, MCP51, MCP55,
+MCP61, MCP65 and MCP67 Ethernet controller chips.
+.Pp
+Supported features include (hardware support provided):
+.Pp
+.Bl -bullet -compact
+.It
+Receive/Transmit IP/TCP/UDP checksum offload
+.It
+Hardware VLAN tag insertion/stripping
+.It
+TCP segmentation offload (TSO)
+.It
+MSI/MSI-X
+.It
+Jumbo Frames
+.El
+.Pp
+Support for Jumbo Frames is provided via the interface MTU setting.
+Selecting an MTU larger than 1500 bytes with the
+.Xr ifconfig 8
+utility configures the adapter to receive and transmit Jumbo Frames.
+.Pp
+The
+.Nm
+driver supports the following media types:
+.Bl -tag -width "10baseT/UTP"
+.It Cm autoselect
+Enable autoselection of the media type and options.
+.It Cm 10baseT/UTP
+Set 10Mbps operation.
+.It Cm 100baseTX
+Set 100Mbps (Fast Ethernet) operation.
+.It Cm 1000baseT
+Set 1000Mbps (Gigabit Ethernet) operation (recent models only).
+.El
+.Pp
+The
+.Nm
+driver supports the following media options:
+.Bl -tag -width ".Cm 10baseT/UTP"
+.It Cm half-duplex
+Force half duplex operation.
+.It Cm full-duplex
+Force full duplex operation.
+.El
+.Pp
+For more information on configuring this device, see
+.Xr ifconfig 8 .
+.Sh HARDWARE
+The
+.Nm
+driver supports the following NVIDIA MCP onboard adapters:
+.Pp
+.Bl -bullet -compact
+.It
+NVIDIA nForce MCP Networking Adapter
+.It
+NVIDIA nForce MCP04 Networking Adapter
+.It
+NVIDIA nForce 430 MCP12 Networking Adapter
+.It
+NVIDIA nForce 430 MCP13 Networking Adapter
+.It
+NVIDIA nForce MCP51 Networking Adapter
+.It
+NVIDIA nForce MCP55 Networking Adapter
+.It
+NVIDIA nForce MCP61 Networking Adapter
+.It
+NVIDIA nForce MCP65 Networking Adapter
+.It
+NVIDIA nForce MCP67 Networking Adapter
+.It
+NVIDIA nForce2 MCP2 Networking Adapter
+.It
+NVIDIA nForce2 400 MCP4 Networking Adapter
+.It
+NVIDIA nForce2 400 MCP5 Networking Adapter
+.It
+NVIDIA nForce3 MCP3 Networking Adapter
+.It
+NVIDIA nForce3 250 MCP6 Networking Adapter
+.It
+NVIDIA nForce3 MCP7 Networking Adapter
+.It
+NVIDIA nForce4 CK804 MCP8 Networking Adapter
+.It
+NVIDIA nForce4 CK804 MCP9 Networking Adapter
+.El
+.Sh LOADER TUNABLES
+Tunables can be set at the
+.Xr loader 8
+prompt before booting the kernel or stored in
+.Xr loader.conf 5 .
+.Bl -tag -width indent
+.It Va hw.nfe.msi_disable
+Whether or not MSI support is enabled in the driver.
+The default value is 0.
+.It Va hw.nfe.msix_disable
+Whether or not MSI-X support is enabled in the driver.
+The default value is 0.
+.El
+.Sh SYSCTL VARIABLES
+The following
+.Xr sysctl 8
+variables can be used to modify or monitor
+.Nm
+behavior.
+.Bl -tag -width indent
+.It Va dev.nfe.%d.process_limit
+Maximum number of Rx events to be processed in the event loop
+before rescheduling a taskqueue.
+The accepted range is 50 to 255, the default value is 192.
+The interface does not need to be brought down and up again
+before a change takes effect.
+.El
+.Sh SEE ALSO
+.Xr altq 4 ,
+.Xr arp 4 ,
+.Xr intro 4 ,
+.Xr miibus 4 ,
+.Xr netintro 4 ,
+.Xr pci 4 ,
+.Xr polling 4 ,
+.Xr sysctl 8 ,
+.Xr ifconfig 8
+.Sh HISTORY
+The
+.Nm
+device driver first appeared in
+.Ox 3.9 ,
+and then in
+.Fx 7.0 .
+.Sh AUTHORS
+.An -nosplit
+The
+.Nm
+driver was written by
+.An Jonathan Gray
+.Aq jsg at openbsd.org
+and
+.An Damien Bergamini
+.Aq damien at openbsd.org .
+The
+.Nm
+driver was ported to
+.Fx
+by
+.An Shigeaki Tagashira
+.Aq shigeaki at se.hiroshima-u.ac.jp .
Index: ipsec.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/ipsec.4,v
retrieving revision 1.2
retrieving revision 1.3
diff -L share/man/man4/ipsec.4 -L share/man/man4/ipsec.4 -u -r1.2 -r1.3
--- share/man/man4/ipsec.4
+++ share/man/man4/ipsec.4
@@ -27,48 +27,79 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $FreeBSD: src/share/man/man4/ipsec.4,v 1.16.2.1 2006/03/09 12:41:34 gnn Exp $
+.\" $FreeBSD: src/share/man/man4/ipsec.4,v 1.22 2007/08/05 16:16:14 bz Exp $
.\"
-.Dd February 14, 2006
+.Dd August 5, 2007
.Dt IPSEC 4
.Os
.Sh NAME
-.Nm ipsec
-.Nd IP security protocol
+.Nm IPsec
+.Nd Internet Protocol Security protocol
.Sh SYNOPSIS
+.Cd "options IPSEC"
+.Cd "options IPSEC_FILTERTUNNEL"
+.Cd "device crypto"
+.Pp
.In sys/types.h
.In netinet/in.h
-.In netinet6/ipsec.h
+.In netipsec/ipsec.h
+.In netipsec/ipsec6.h
.Sh DESCRIPTION
.Nm
is a security protocol implemented within the Internet Protocol layer
-of the TCP/IP stack.
+of the networking stack.
.Nm
is defined for both IPv4 and IPv6
.Xr ( inet 4
and
.Xr inet6 4 ) .
.Nm
-contains two protocols,
-ESP, the encapsulated security payload protocol and
-AH, the authentication header protocol.
-ESP prevents unauthorized parties from reading the payload of an IP packet
-by encrypting it using
-secret key cryptography algorithms.
-AH both authenticates guarantees the integrity of an IP packet
+is a set of protocols,
+.Tn ESP
+(for Encapsulating Security Payload)
+.Tn AH
+(for Authentication Header),
+and
+.Tn IPComp
+(for IP Payload Compression Protocol)
+that provide security services for IP datagrams.
+AH both authenticates and guarantees the integrity of an IP packet
by attaching a cryptographic checksum computed using one-way hash functions.
+ESP, in addition, prevents unauthorized parties from reading the payload of
+an IP packet by also encrypting it.
+IPComp tries to increase communication performance by compressing IP payload,
+thus reducing the amount of data sent.
+This will help nodes on slow links but with enough computing power.
.Nm
-has operates in one of two modes: transport mode or tunnel mode.
+operates in one of two modes: transport mode or tunnel mode.
Transport mode is used to protect peer-to-peer communication between end nodes.
Tunnel mode encapsulates IP packets within other IP packets
and is designed for security gateways such as VPN endpoints.
+.Pp
+System configuration requires the
+.Xr crypto 4
+subsystem.
+.Pp
+The packets can be passed to a virtual
+.Xr enc 4
+interface,
+to perform packet filtering before outbound encryption and after decapsulation
+inbound.
+.Pp
+To properly filter on the inner packets of an
+.Nm
+tunnel with firewalls, add
+.Cd "options IPSEC_FILTERTUNNEL"
+to the kernel configuration file.
.\"
.Ss Kernel interface
.Nm
is controlled by a key management and policy engine,
-that reside in the operating system kernel. Key management
+that reside in the operating system kernel.
+Key management
is the process of associating keys with security associations, also
-know as SAs. Policy management dictates when new security
+know as SAs.
+Policy management dictates when new security
associations created or destroyed.
.Pp
The key management engine can be accessed from userland by using
@@ -88,8 +119,9 @@
The kernel implements
an extended version of the
.Dv PF_KEY
-interface, and allows the programmer to define IPsec policies
-which are similar to the per-packet filters. The
+interface and allows the programmer to define IPsec policies
+which are similar to the per-packet filters.
+The
.Xr setsockopt 2
interface is used to define per-socket behavior, and
.Xr sysctl 3
@@ -103,40 +135,42 @@
.Nm APIs.
.\"
.Ss Policy management
-IPsec policies can be managed in one of two ways, either by
+IPsec policies can be managed in one of two ways, either by
configuring per-socket policies using the
-.Xr setsockopt 2
+.Xr setsockopt 2
system calls, or by configuring kernel level packet filter-based
policies using the
.Dv PF_KEY
interface, via the
-.Xr setkey 8
-command.
-In either case, IPsec policies must be specified using the syntax described in
-.Xr ipsec_set_policy 3 .
-Please refer to the
.Xr setkey 8
-man page for instructions on its use.
+you can define IPsec policies against packets using rules similar to packet
+filtering rules.
+Refer to
+.Xr setkey 8
+on how to use it.
.Pp
When setting policies using the
.Xr setkey 8
-command the
+command, the
.Dq Li default
-option you can have the system use its default policy, explained
-below, for processing packets.
+option instructs the system to use its default policy, as
+explained below, for processing packets.
The following sysctl variables are available for configuring the
-system's IPsec behavior. The variables can have one of two values.
+system's IPsec behavior.
+The variables can have one of two values.
A
.Li 1
means
.Dq Li use ,
which means that if there is a security association then use it but if
-there is not then the packets are not processed by IPsec. The value
+there is not then the packets are not processed by IPsec.
+The value
.Li 2
is synonymous with
.Dq Li require ,
which requires that a security association must exist for the packets
-to move, and not be dropped. These terms are defined in
+to move, and not be dropped.
+These terms are defined in
.Xr ipsec_set_policy 8 .
.Bl -column net.inet6.ipsec6.esp_trans_deflev integerxxx
.It Sy "Name Type Changeable"
@@ -151,7 +185,8 @@
.El
.Pp
If the kernel does not find a matching, system wide, policy then the
-default value is applied. The system wide default policy is specified
+default value is applied.
+The system wide default policy is specified
by the following
.Xr sysctl 8
variables.
@@ -169,7 +204,19 @@
.El
.\"
.Ss Miscellaneous sysctl variables
-The following variables are accessible via
+When the
+.Nm
+protocols are configured for use, all protocols are included in the system.
+To selectively enable/disable protocols, use
+.Xr sysctl 8 .
+.Bl -column net.inet.ipcomp.ipcomp_enable
+.It Sy "Name Default"
+.It "net.inet.esp.esp_enable On"
+.It "net.inet.ah.ah_enable On"
+.It "net.inet.ipcomp.ipcomp_enable Off"
+.El
+.Pp
+In addition the following variables are accessible via
.Xr sysctl 8 ,
for tweaking the kernel's IPsec behavior:
.Bl -column net.inet6.ipsec6.inbonud_call_ike integerxxx
@@ -235,12 +282,13 @@
and
.Xr inet6 4
protocols and therefore supports most of the protocols defined upon
-those IP-layer protocols. The
+those IP-layer protocols.
+The
.Xr icmp 4
and
-.Xr icmp6 4
+.Xr icmp6 4
protocols may behave differently with
-.Nm
+.Nm
because
.Nm
can prevent
@@ -253,6 +301,8 @@
.Xr ioctl 2 ,
.Xr socket 2 ,
.Xr ipsec_set_policy 3 ,
+.Xr crypto 4 ,
+.Xr enc 4 ,
.Xr icmp6 4 ,
.Xr intro 4 ,
.Xr ip6 4 ,
@@ -289,12 +339,42 @@
.%O work in progress material
.Re
.Sh HISTORY
-The implementation described herein appeared in WIDE/KAME IPv6/IPsec stack.
-.Sh BUGS
-The IPsec support is subject to change as the IPsec protocols develop.
+The original
+.Nm
+implementation appeared in the WIDE/KAME IPv6/IPsec stack.
.Pp
+For
+.Fx 5.0
+a fully locked IPsec implementation called fast_ipsec was brought in.
+The protocols drew heavily on the
+.Ox
+implementation of the
+.Tn IPsec
+protocols.
+The policy management code was derived from the
+.Tn KAME
+implementation found
+in their
+.Tn IPsec
+protocols.
+The fast_ipsec implementation lacked
+.Xr ip6 4
+support but made use of the
+.Xr crypto 4
+subsystem.
+.Pp
+For
+.Fx 7.0
+.Xr ip6 4
+support was added to fast_ipsec.
+After this the old KAME IPsec implementation was dropped and fast_ipsec
+became what now is the only
+.Nm
+implementation in
+.Fx .
+.Sh BUGS
There is no single standard for the policy engine API,
-so the policy engine API described herein is just for KAME implementation.
+so the policy engine API described herein is just for this implementation.
.Pp
AH and tunnel mode encapsulation may not work as you might expect.
If you configure inbound
@@ -320,5 +400,12 @@
.Dv SADB_SPDDUMP
operations on
.Dv PF_KEY
-sockets may fail due to lack of space. Increasing the socket buffer
+sockets may fail due to lack of space.
+Increasing the socket buffer
size may alleviate this problem.
+.Pp
+The
+.Tn IPcomp
+protocol support is currently broken.
+.Pp
+This documentation needs more review.
Index: xl.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/xl.4,v
retrieving revision 1.1.1.2
retrieving revision 1.2
diff -L share/man/man4/xl.4 -L share/man/man4/xl.4 -u -r1.1.1.2 -r1.2
--- share/man/man4/xl.4
+++ share/man/man4/xl.4
@@ -28,7 +28,7 @@
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
.\" THE POSSIBILITY OF SUCH DAMAGE.
.\"
-.\" $FreeBSD: src/share/man/man4/xl.4,v 1.34.2.2 2006/02/02 07:50:01 trhodes Exp $
+.\" $FreeBSD: src/share/man/man4/xl.4,v 1.38 2007/01/30 08:40:04 brueffer Exp $
.\"
.Dd July 16, 2005
.Dt XL 4
@@ -246,6 +246,7 @@
the author considers it a manufacturing defect.
.El
.Sh SEE ALSO
+.Xr altq 4 ,
.Xr arp 4 ,
.Xr cardbus 4 ,
.Xr miibus 4 ,
Index: ipfirewall.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/ipfirewall.4,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -L share/man/man4/ipfirewall.4 -L share/man/man4/ipfirewall.4 -u -r1.1.1.1 -r1.2
--- share/man/man4/ipfirewall.4
+++ share/man/man4/ipfirewall.4
@@ -1,12 +1,39 @@
.\"
-.\" $FreeBSD: src/share/man/man4/ipfirewall.4,v 1.31 2004/08/27 15:16:20 andre Exp $
+.\" $FreeBSD: src/share/man/man4/ipfirewall.4,v 1.33 2006/10/16 07:56:36 danger Exp $
.\"
-.Dd October 28, 2002
+.Dd September 1, 2006
.Dt IPFW 4
.Os
.Sh NAME
.Nm ipfw
.Nd IP packet filter and traffic accounting
+.Sh SYNOPSIS
+To compile
+.Ns Nm
+into the kernel, place the following option in the kernel configuration
+file:
+.Bd -ragged -offset indent
+.Cd "options IPFIREWALL"
+.Ed
+.Pp
+Other kernel options related to
+.Ns Nm
+which may also be useful are:
+.Bd -ragged -offset indent
+.Cd "options IPFIREWALL_DEFAULT_TO_ACCEPT"
+.Cd "options IPFIREWALL_FORWARD"
+.Cd "options IPFIREWALL_VERBOSE"
+.Cd "options IPFIREWALL_VERBOSE_LIMIT=100"
+.Ed
+.Pp
+To load
+.Ns Nm
+as a module at boot time, add the following line into the
+.Xr loader.conf 5
+file:
+.Bd -literal -offset indent
+ipfw_load="YES"
+.Ed
.Sh DESCRIPTION
The
.Nm
@@ -16,6 +43,41 @@
packets travelling through
network interfaces.
.Pp
+The default behavior of
+.Nm
+is to block all incoming and outgoing traffic.
+This behavior can be modified, to allow all traffic through the
+.Nm
+firewall by default, by enabling the
+.Dv IPFIREWALL_DEFAULT_TO_ACCEPT
+kernel option.
+This option may be useful when configuring
+.Nm
+for the first time.
+If the default
+.Nm
+behavior is to allow everything, it is easier to cope with
+firewall-tuning mistakes which may accidentally block all traffic.
+.Pp
+To enable logging of packets passing through
+.Nm ,
+enable the
+.Dv IPFIREWALL_VERBOSE
+kernel option.
+The
+.Dv IPFIREWALL_VERBOSE_LIMIT
+option will prevent
+.Xr syslogd 8
+from flooding system logs or causing local Denial of Service.
+This option may be set to the number of packets which will be logged on
+a per-entry basis before the entry is rate-limited.
+.Pp
+Policy routing and transparent forwarding features of
+.Nm
+can be enabled by
+.Dv IPFIREWALL_FORWARD
+kernel option.
+.Pp
The user interface for
.Nm
is implemented by the
@@ -25,28 +87,6 @@
manpage for a complete description of the
.Nm
capabilities and how to use it.
-.Ss Kernel Options
-The following options in the kernel configuration file are related to
-.Nm
-operation:
-.Pp
-.Bl -tag -width ".Dv IPFIREWALL_VERBOSE_LIMIT" -compact
-.It Dv IPFIREWALL
-enable
-.Nm
-.It Dv IPFIREWALL_VERBOSE
-enable
-.Nm
-logging
-.It Dv IPFIREWALL_VERBOSE_LIMIT
-limit
-.Nm
-logging
-.It Dv IPDIVERT
-enable
-.Xr divert 4
-sockets
-.El
.Sh SEE ALSO
.Xr setsockopt 2 ,
.Xr divert 4 ,
Index: xe.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/xe.4,v
retrieving revision 1.1.1.2
retrieving revision 1.2
diff -L share/man/man4/xe.4 -L share/man/man4/xe.4 -u -r1.1.1.2 -r1.2
--- share/man/man4/xe.4
+++ share/man/man4/xe.4
@@ -23,7 +23,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $FreeBSD: src/share/man/man4/xe.4,v 1.9.2.2 2006/02/02 07:50:01 trhodes Exp $
+.\" $FreeBSD: src/share/man/man4/xe.4,v 1.13 2005/11/18 10:52:22 ru Exp $
.\"
.Dd July 16, 2005
.Dt XE 4
Index: iwi.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/iwi.4,v
retrieving revision 1.1.1.2
retrieving revision 1.2
diff -L share/man/man4/iwi.4 -L share/man/man4/iwi.4 -u -r1.1.1.2 -r1.2
--- share/man/man4/iwi.4
+++ share/man/man4/iwi.4
@@ -1,4 +1,4 @@
-.\" Copyright (c) 2004, 2005
+.\" Copyright (c) 2004-2006
.\" Damien Bergamini <damien.bergamini at free.fr>. All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
@@ -23,9 +23,9 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $FreeBSD: src/share/man/man4/iwi.4,v 1.4.2.2 2006/02/02 07:50:00 trhodes Exp $
+.\" $FreeBSD: src/share/man/man4/iwi.4,v 1.18 2007/03/06 13:17:05 brueffer Exp $
.\"
-.Dd July 16, 2005
+.Dd March 6, 2007
.Os
.Dt IWI 4
.Sh NAME
@@ -39,13 +39,25 @@
.Cd "device iwi"
.Cd "device pci"
.Cd "device wlan"
+.Cd "device firmware"
.Ed
.Pp
Alternatively, to load the driver as a
-module at boot time, place the following line in
+module at boot time, place the following lines in
.Xr loader.conf 5 :
.Bd -literal -offset indent
if_iwi_load="YES"
+wlan_load="YES"
+firmware_load="YES"
+.Ed
+.Pp
+In both cases, place the following lines in
+.Xr loader.conf 5
+to load the firmware modules:
+.Bd -literal -offset indent
+iwi_bss_load="YES"
+iwi_ibss_load="YES"
+iwi_monitor_load="YES"
.Ed
.Sh DESCRIPTION
The
@@ -63,12 +75,18 @@
.Xr ifconfig 8 .
.Pp
This driver requires firmware to be loaded before it will work.
-You need to obtain
-.Xr iwicontrol 8
-from the IWI web page listed below to accomplish loading the firmware
-before
-.Xr ifconfig 8
-will work.
+For the loaded firmware to work the license at
+.Pa /usr/share/doc/legal/intel_iwi/LICENSE
+must be agreed to and the following line be added to
+.Xr loader.conf 5 :
+.Pp
+.Dl "legal.intel_iwi.license_ack=1"
+.Sh FILES
+.Bl -tag -width ".Pa /usr/share/doc/legal/intel_iwi/LICENSE" -compact
+.It Pa /usr/share/doc/legal/intel_iwi/LICENSE
+.Nm
+firmware license
+.El
.Sh EXAMPLES
Join an existing BSS network (i.e., connect to an access point):
.Pp
@@ -82,40 +100,52 @@
Join a specific BSS network with 64-bit WEP encryption:
.Bd -literal -offset indent
ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
- wepmode on wepkey 0x1234567890
+ wepmode on wepkey 0x1234567890 weptxkey 1
.Ed
.Pp
Join a specific BSS network with 128-bit WEP encryption:
.Bd -literal -offset indent
ifconfig iwi0 inet 192.168.0.20 netmask 0xffffff00 ssid my_net \e
- wepmode on wepkey 0x01020304050607080910111213
+ wepmode on wepkey 0x01020304050607080910111213 weptxkey 1
.Ed
.Sh DIAGNOSTICS
.Bl -diag
.It "iwi%d: device timeout"
The driver will reset the hardware.
This should not happen.
-.It "iwi%d: Please load firmware"
-The required firmware has not been loaded into the card, and therefore
-the card cannot operate.
-Load the firmware with
-.Xr iwicontrol 8
-before proceeding.
+.It "iwi%d: firmware error"
+The onboard microcontroller crashes for some reason.
+The driver will reset the hardware.
+This should not happen.
+.It "iwi%d: timeout waiting for firmware initialization to complete"
+The onboard microcontroller failed to initialize in time.
+This should not happen.
+.It "iwi%d: could not load firmware image '%s'"
+The driver failed to load the firmware image using the
+.Xr firmware 9
+subsystem.
+Verify that the necessary firmware modules are loaded and the
+license agreement
+.Xr loader 8
+tunable has been set.
+.It "iwi%d: could not load boot firmware"
+An attempt to upload the boot firmware image to the onboard microcontroller
+failed.
+This should not happen.
+.It "iwi%d: could not load microcode"
+An attempt to upload the microcode image to the onboard microcontroller failed.
+This should not happen.
+.It "iwi%d: could not load main firmware"
+An attempt to upload the main firmware image to the onboard microcontroller
+failed.
+This should not happen.
.El
.Sh SEE ALSO
-.Xr an 4 ,
-.Xr ath 4 ,
+.Xr altq 4 ,
.Xr ipw 4 ,
.Xr pci 4 ,
-.Xr wi 4 ,
.Xr wlan 4 ,
-.Xr ifconfig 8 ,
-.Xr iwicontrol 8 ,
-.Xr wicontrol 8
-.Rs
-.%T The IWI Web Page
-.%O http://damien.bergamini.free.fr/ipw/
-.Re
+.Xr ifconfig 8
.Sh AUTHORS
The
.Nm
Index: Makefile
===================================================================
RCS file: /home/cvs/src/share/man/man4/Makefile,v
retrieving revision 1.8
retrieving revision 1.9
diff -L share/man/man4/Makefile -L share/man/man4/Makefile -u -r1.8 -r1.9
--- share/man/man4/Makefile
+++ share/man/man4/Makefile
@@ -126,7 +126,6 @@
iwi.4 \
ixgb.4 \
joy.4 \
- kame.4 \
kbdmux.4 \
keyboard.4 \
kld.4 \
@@ -172,6 +171,7 @@
ncv.4 \
netgraph.4 \
netintro.4 \
+ nfe.4 \
ng_async.4 \
ng_atm.4 \
ngatmbase.4 \
@@ -384,11 +384,11 @@
wlan_tkip.4 \
wlan_wep.4 \
wlan_xauth.4 \
- worm.4 \
xe.4 \
xl.4 \
xpt.4 \
- zero.4
+ zero.4 \
+ zyd.4
MLINKS= agp.4 agpgart.4
MLINKS+=altq.4 ALTQ.4
Index: joy.4
===================================================================
RCS file: /home/cvs/src/share/man/man4/joy.4,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -L share/man/man4/joy.4 -L share/man/man4/joy.4 -u -r1.1.1.1 -r1.2
--- share/man/man4/joy.4
+++ share/man/man4/joy.4
@@ -1,5 +1,5 @@
.\"
-.\" $FreeBSD: src/share/man/man4/joy.4,v 1.26 2005/01/21 08:36:37 ru Exp $
+.\" $FreeBSD: src/share/man/man4/joy.4,v 1.30 2007/02/12 20:58:32 brueffer Exp $
.\"
.Dd January 23, 1995
.Dt JOY 4
@@ -8,16 +8,26 @@
.Nm joy
.Nd joystick device driver
.Sh SYNOPSIS
-To link into the kernel:
-.Cd device joy
+To compile this driver into the kernel,
+place the following lines in your
+kernel configuration file:
+.Bd -ragged -offset indent
+.Cd "device joy"
+.Ed
.Pp
-To load as a kernel loadable module:
-.Dl kldload joy
+Alternatively, to load the driver as a
+module at boot time, place the following line in
+.Xr loader.conf 5 :
+.Bd -literal -offset indent
+joy_load="YES"
+.Ed
.Pp
In
.Pa /boot/device.hints :
.Cd hint.joy.0.at="isa"
.Cd hint.joy.0.port="0x201"
+.Cd hint.joy.1.at="isa"
+.Cd hint.joy.1.port="0x201"
.Pp
.In sys/joystick.h
.Sh DESCRIPTION
@@ -94,7 +104,7 @@
.Ed
.Pp
Pots are normally 0-150k variable resistors (0-100k sometimes), and
-according to the IBM techref, the time is given by
+according to the IBM technical reference, the time is given by
Time = 24.2e-6s + 0.011e-6s * R/Ohms
.Sh FILES
.Bl -tag -width /dev/joy?
@@ -102,7 +112,9 @@
joystick device files
.El
.Sh HISTORY
-The joystick driver appeared in
+The
+.Nm
+driver appeared in
.Fx 2.0.5 .
.Sh AUTHORS
.An Jean-Marc Zucconi Aq jmz at cabri.obs-besancon.fr
More information about the Midnightbsd-cvs
mailing list