summaryrefslogtreecommitdiff
path: root/static/netbsd/man4/zyd.4 4.html
diff options
context:
space:
mode:
Diffstat (limited to 'static/netbsd/man4/zyd.4 4.html')
-rw-r--r--static/netbsd/man4/zyd.4 4.html305
1 files changed, 0 insertions, 305 deletions
diff --git a/static/netbsd/man4/zyd.4 4.html b/static/netbsd/man4/zyd.4 4.html
deleted file mode 100644
index e7153d13..00000000
--- a/static/netbsd/man4/zyd.4 4.html
+++ /dev/null
@@ -1,305 +0,0 @@
-<table class="head">
- <tr>
- <td class="head-ltitle">ZYD(4)</td>
- <td class="head-vol">Device Drivers Manual</td>
- <td class="head-rtitle">ZYD(4)</td>
- </tr>
-</table>
-<div class="manual-text">
-<section class="Sh">
-<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
-<p class="Pp"><code class="Nm">zyd</code> &#x2014; <span class="Nd">ZyDAS
- ZD1211/ZD1211B USB IEEE 802.11b/g wireless network device</span></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
-<p class="Pp"><code class="Cd">zyd* at uhub? port ?</code></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
-<p class="Pp">The <code class="Nm">zyd</code> driver provides support for
- wireless network adapters based around the ZyDAS ZD1211 and ZD1211B USB
- chips.</p>
-<p class="Pp">These are the modes the <code class="Nm">zyd</code> driver can
- operate in:</p>
-<dl class="Bl-tag">
- <dt id="infrastructure">BSS mode</dt>
- <dd>Also known as
- <a class="permalink" href="#infrastructure"><i class="Em">infrastructure</i></a>
- mode, this is used when associating with an access point, through which
- all traffic passes. This mode is the default.</dd>
- <dt>monitor mode</dt>
- <dd>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.</dd>
-</dl>
-<p class="Pp"><code class="Nm">zyd</code> supports software WEP. 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.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="CONFIGURATION"><a class="permalink" href="#CONFIGURATION">CONFIGURATION</a></h1>
-<p class="Pp">The <code class="Nm">zyd</code> driver can be configured at
- runtime with <a class="Xr">ifconfig(8)</a> or on boot with
- <a class="Xr">ifconfig.if(5)</a> using the following parameters:</p>
-<dl class="Bl-tag">
- <dt id="bssid"><a class="permalink" href="#bssid"><code class="Cm">bssid</code></a>
- <var class="Ar">bssid</var></dt>
- <dd>Set the desired BSSID.</dd>
- <dt id="bssid~2"><a class="permalink" href="#bssid~2"><code class="Fl">-bssid</code></a></dt>
- <dd>Unset the desired BSSID. The interface will automatically select a BSSID
- in this mode, which is the default.</dd>
- <dt id="chan"><a class="permalink" href="#chan"><code class="Cm">chan</code></a>
- <var class="Ar">n</var></dt>
- <dd>Set the channel (radio frequency) to be used by the driver based on the
- given channel ID <var class="Ar">n</var>.</dd>
- <dt id="chan~2"><a class="permalink" href="#chan~2"><code class="Fl">-chan</code></a></dt>
- <dd>Unset the desired channel to be used by the driver. The driver will
- automatically select a channel in this mode, which is the default.</dd>
- <dt id="media"><a class="permalink" href="#media"><code class="Cm">media</code></a>
- <var class="Ar">media</var></dt>
- <dd>The <code class="Nm">zyd</code> driver supports the following
- <var class="Ar">media</var> types:
- <p class="Pp"></p>
- <dl class="Bl-tag Bl-compact">
- <dt id="autoselect"><a class="permalink" href="#autoselect"><code class="Cm">autoselect</code></a></dt>
- <dd>Enable autoselection of the media type and options.</dd>
- <dt id="DS1"><a class="permalink" href="#DS1"><code class="Cm">DS1</code></a></dt>
- <dd>Set 802.11b DS 1Mbps operation.</dd>
- <dt id="DS2"><a class="permalink" href="#DS2"><code class="Cm">DS2</code></a></dt>
- <dd>Set 802.11b DS 2Mbps operation.</dd>
- <dt id="DS5"><a class="permalink" href="#DS5"><code class="Cm">DS5</code></a></dt>
- <dd>Set 802.11b DS 5.5Mbps operation.</dd>
- <dt id="DS11"><a class="permalink" href="#DS11"><code class="Cm">DS11</code></a></dt>
- <dd>Set 802.11b DS 11Mbps operation.</dd>
- </dl>
- </dd>
- <dt id="mediaopt"><a class="permalink" href="#mediaopt"><code class="Cm">mediaopt</code></a>
- <var class="Ar">opts</var></dt>
- <dd>The <code class="Nm">zyd</code> driver supports the following media
- options:
- <dl class="Bl-tag">
- <dt id="ibss"><a class="permalink" href="#ibss"><code class="Cm">ibss</code></a></dt>
- <dd>Select Independent Basic Service Set (IBSS) operation.</dd>
- </dl>
- </dd>
- <dt id="mediaopt~2"><a class="permalink" href="#mediaopt~2"><code class="Fl">-mediaopt</code></a>
- <var class="Ar">opts</var></dt>
- <dd>Disable the specified media options on the driver and return it to the
- default mode of operation (BSS).</dd>
- <dt id="nwid"><a class="permalink" href="#nwid"><code class="Cm">nwid</code></a>
- <var class="Ar">id</var></dt>
- <dd>Set the network ID. The <var class="Ar">id</var> can either be any text
- string up to 32 characters in length, or a series of hexadecimal digits up
- to 64 digits. An empty <var class="Ar">id</var> string allows the
- interface to connect to any available access points. By default the
- <code class="Nm">zyd</code> driver uses an empty string. Note that network
- ID is synonymous with Extended Service Set ID (ESSID).</dd>
- <dt id="nwid~2"><a class="permalink" href="#nwid~2"><code class="Fl">-nwid</code></a></dt>
- <dd>Set the network ID to the empty string to allow the interface to connect
- to any available access point.</dd>
- <dt id="nwkey"><a class="permalink" href="#nwkey"><code class="Cm">nwkey</code></a>
- <var class="Ar">key</var></dt>
- <dd>Enable WEP encryption using the specified <var class="Ar">key</var>. The
- <var class="Ar">key</var> can either be a string, a series of hexadecimal
- digits (preceded by &#x2018;0x&#x2019;), or a set of keys of the form
- &#x201C;n:k1,k2,k3,k4&#x201D;, where &#x2018;n&#x2019; specifies which of
- the keys will be used for transmitted packets, and the four keys,
- &#x201C;k1&#x201D; through &#x201C;k4&#x201D;, are configured as WEP keys.
- If a set of keys is specified, a comma (&#x2018;,&#x2019;) within the key
- must be escaped with a backslash. Note that if multiple keys are used,
- their order must be the same within the network.
- <code class="Nm">zyd</code> is capable of using both 40-bit (5 characters
- or 10 hexadecimal digits) or 104-bit (13 characters or 26 hexadecimal
- digits) keys.</dd>
- <dt id="nwkey~2"><a class="permalink" href="#nwkey~2"><code class="Fl">-nwkey</code></a></dt>
- <dd>Disable WEP encryption. This is the default mode of operation.</dd>
-</dl>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="HARDWARE"><a class="permalink" href="#HARDWARE">HARDWARE</a></h1>
-<p class="Pp">The following devices are known to be supported by the
- <code class="Nm">zyd</code> driver:</p>
-<p class="Pp"></p>
-<div class="Bd-indent">
-<dl class="Bl-tag Bl-compact">
- <dt>3COM 3CRUSB10075</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Acer WLAN-G-US1</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Airlink+ AWLL3025</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Airlink 101 AWLL3026</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>AOpen 802.11g WL54</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Asus A9T integrated wirless</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Asus WL-159g</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Belkin F5D7050 v.4000</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Billion BiPAC 3011G</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Buffalo WLI-U2-KG54L</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>CC&amp;C WL-2203B</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>DrayTek Vigor 550</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Edimax EW-7317UG</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Edimax EW-7317LDG</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Fiberline Networks WL-43OU</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>iNexQ UR055g</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Linksys WUSBF54G</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Longshine LCS-8131G3</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>MSI US54SE</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Philips SNU5600</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Planet WL-U356</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Planex GW-US54GZ</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Planex GW-US54GZL</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Planex GW-US54Mini</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Safecom SWMULZ-5400</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Sagem XG 760A</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Sagem XG 76NA</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Sandberg Wireless G54 USB</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Sitecom WL-113</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>SMC SMCWUSB-G</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Sweex wireless USB 54 Mbps</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Tekram/Siemens USB adapter</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Telegent TG54USB</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Trendnet TEW-424UB</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Trendnet TEW-429UB</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>TwinMOS G240</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>US Robotics 5423</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>X-Micro XWL-11GUZX</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Yakumo QuickWLAN USB</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>Zonet ZEW2501</dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt>ZyXEL ZyAIR G-220</dt>
- <dd style="width: auto;">&#x00A0;</dd>
-</dl>
-</div>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1>
-<p class="Pp">The adapter needs some firmware files, which are loaded on demand
- by the driver when a device is attached:</p>
-<p class="Pp"></p>
-<div class="Bd-indent">
-<dl class="Bl-tag Bl-compact">
- <dt><span class="Pa">/libdata/firmware/zyd/zyd-zd1211</span></dt>
- <dd style="width: auto;">&#x00A0;</dd>
- <dt><span class="Pa">/libdata/firmware/zyd/zyd-zd1211b</span></dt>
- <dd style="width: auto;">&#x00A0;</dd>
-</dl>
-</div>
-See <a class="Xr">firmload(9)</a> for how to change this.
-</section>
-<section class="Sh">
-<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1>
-<p class="Pp">The following <a class="Xr">ifconfig.if(5)</a> example configures
- zyd0 to join whatever network is available on boot, using WEP key
- &#x201C;0x1deadbeef1&#x201D;, channel 11:</p>
-<div class="Bd Pp Bd-indent Li">
-<pre>inet 192.168.1.1 netmask 255.255.255.0 nwkey 0x1deadbeef1 chan 11</pre>
-</div>
-<p class="Pp">Configure zyd0 for WEP, using hex key
- &#x201C;0x1deadbeef1&#x201D;:</p>
-<div class="Bd Pp Bd-indent Li">
-<pre># ifconfig zyd0 nwkey 0x1deadbeef1</pre>
-</div>
-<p class="Pp">Return zyd0 to its default settings:</p>
-<div class="Bd Pp Bd-indent Li">
-<pre># ifconfig zyd0 -bssid -chan media autoselect \
- nwid &quot;&quot; -nwkey</pre>
-</div>
-<p class="Pp">Join an existing BSS network, &#x201C;my_net&#x201D;:</p>
-<div class="Bd Pp Bd-indent Li">
-<pre># ifconfig zyd0 192.168.0.2 netmask 0xffffff00 nwid my_net</pre>
-</div>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
-<dl class="Bl-diag">
- <dt>zyd%d: could not read firmware file %s (error=%d)</dt>
- <dd>For some reason, the driver was unable to read the firmware file from the
- filesystem. The file might be missing or corrupted.</dd>
- <dt>zyd%d: could not load firmware (error=%d)</dt>
- <dd>An error occurred while attempting to upload the firmware to the onboard
- microcontroller unit.</dd>
- <dt>zyd%d: could not send command (error=%s)</dt>
- <dd>An attempt to send a command to the firmware failed.</dd>
- <dt>zyd%d: sorry, radio %s is not supported yet</dt>
- <dd>Support for the specified radio chip is not yet implemented in the driver.
- The device will not attach.</dd>
- <dt>zyd%d: device version mismatch: 0x%x (only &gt;= 43.30 supported)</dt>
- <dd>Early revisions of the ZD1211 chipset are not supported by this driver.
- The device will not attach.</dd>
- <dt>zyd%d: device timeout</dt>
- <dd>A frame dispatched to the hardware for transmission did not complete in
- time. The driver will reset the hardware. This should not happen.</dd>
-</dl>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
- ALSO</a></h1>
-<p class="Pp"><a class="Xr">arp(4)</a>, <a class="Xr">ifmedia(4)</a>,
- <a class="Xr">intro(4)</a>, <a class="Xr">netintro(4)</a>,
- <a class="Xr">usb(4)</a>, <a class="Xr">ifconfig.if(5)</a>,
- <a class="Xr">ifconfig(8)</a>, <a class="Xr">firmload(9)</a></p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1>
-<p class="Pp">The <code class="Nm">zyd</code> driver was written by
- <span class="An">Florian Stoehr</span>
- &lt;<a class="Mt" href="mailto:ich@florian-stoehr.de">ich@florian-stoehr.de</a>&gt;,
- <span class="An">Damien Bergamini</span>
- &lt;<a class="Mt" href="mailto:damien@openbsd.org">damien@openbsd.org</a>&gt;,
- and <span class="An">Jonathan Gray</span>
- &lt;<a class="Mt" href="mailto:jsg@openbsd.org">jsg@openbsd.org</a>&gt;.</p>
-</section>
-<section class="Sh">
-<h1 class="Sh" id="CAVEATS"><a class="permalink" href="#CAVEATS">CAVEATS</a></h1>
-<p class="Pp">The <code class="Nm">zyd</code> 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.</p>
-</section>
-</div>
-<table class="foot">
- <tr>
- <td class="foot-date">March 24, 2019</td>
- <td class="foot-os">NetBSD 10.1</td>
- </tr>
-</table>