diff options
Diffstat (limited to 'static/netbsd/man4/urtwn.4 3.html')
| -rw-r--r-- | static/netbsd/man4/urtwn.4 3.html | 222 |
1 files changed, 0 insertions, 222 deletions
diff --git a/static/netbsd/man4/urtwn.4 3.html b/static/netbsd/man4/urtwn.4 3.html deleted file mode 100644 index 5a9becd5..00000000 --- a/static/netbsd/man4/urtwn.4 3.html +++ /dev/null @@ -1,222 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">URTWN(4)</td> - <td class="head-vol">Device Drivers Manual</td> - <td class="head-rtitle">URTWN(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">urtwn</code> — <span class="Nd">Realtek - RTL8188CU/RTL8188EU/RTL8192CU/RTL8192EU USB IEEE 802.11b/g/n 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">urtwn* 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">urtwn</code> driver supports USB 2.0 wireless - network devices based on Realtek RTL8188CUS, RTL8188CE-VAU, RTL8188EUS, - RTL8188RU, RTL8192CU and RTL8192EU chipsets.</p> -<p class="Pp">The RTL8188CUS and RTL8188EUS are highly integrated 802.11n - adapters that combine a MAC, a 1T1R capable baseband and an RF in a single - chip. They operate in the 2GHz spectrum only. The RTL8188RU is a high-power - variant of the RTL8188CUS. The RTL8188CE-VAU is a PCI Express Mini Card - adapter that attaches to the USB interface.</p> -<p class="Pp">The RTL8192CU and RTL8192EU are highly integrated multiple-in, - multiple-out (MIMO) 802.11n adapters that combine a MAC, a 2T2R capable - baseband and an RF in a single chip. It operates in the 2GHz spectrum - only.</p> -<p class="Pp">These are the modes the <code class="Nm">urtwn</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 id="IEEE">IBSS mode</dt> - <dd>Also known as <a class="permalink" href="#IEEE"><i class="Em">IEEE - ad-hoc</i></a> mode or - <a class="permalink" href="#peer-to-peer"><i class="Em" id="peer-to-peer">peer-to-peer</i></a> - mode. This is the standardized method of operating without an access - point. Stations associate with a service set. However, actual connections - between stations are peer-to-peer.</dd> - <dt>Host AP</dt> - <dd>In this mode the driver acts as an access point (base station) for other - cards.</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">The <code class="Nm">urtwn</code> driver can be configured to use - Wired Equivalent Privacy (WEP) or Wi-Fi Protected Access (WPA-PSK and - WPA2-PSK). WPA is the de facto encryption standard for wireless networks. It - is strongly recommended that WEP not be used as the sole mechanism to secure - wireless communication, due to serious weaknesses in it.</p> -<p class="Pp">The <code class="Nm">urtwn</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>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1> -<p class="Pp">The driver needs the following firmware files, which are loaded - when an interface is attached:</p> -<p class="Pp"></p> -<div class="Bd-indent"> -<dl class="Bl-tag Bl-compact"> - <dt>/libdata/firmware/if_urtwn/rtl8188eufw.bin</dt> - <dd style="width: auto;"> </dd> - <dt>/libdata/firmware/if_urtwn/rtl8192cfw.bin</dt> - <dd style="width: auto;"> </dd> - <dt>/libdata/firmware/if_urtwn/rtl8192cfwU.bin</dt> - <dd style="width: auto;"> </dd> - <dt>/libdata/firmware/if_urtwn/rtl8192efw.bin</dt> - <dd style="width: auto;"> </dd> -</dl> -</div> -</section> -<section class="Sh"> -<h1 class="Sh" id="HARDWARE"><a class="permalink" href="#HARDWARE">HARDWARE</a></h1> -<p class="Pp">The following adapters should work:</p> -<p class="Pp"></p> -<div class="Bd-indent"> -<dl class="Bl-tag Bl-compact"> - <dt>Airlink101 AWLL5088</dt> - <dd style="width: auto;"> </dd> - <dt>Aus. Linx AL-9604R1S</dt> - <dd style="width: auto;"> </dd> - <dt>ASUSTeK USB-N10 NANO</dt> - <dd style="width: auto;"> </dd> - <dt>B-Link BL-LW05-5R</dt> - <dd style="width: auto;"> </dd> - <dt>Belkin F7D1102 Surf Wireless Micro</dt> - <dd style="width: auto;"> </dd> - <dt>D-Link DWA-121</dt> - <dd style="width: auto;"> </dd> - <dt>D-Link DWA-125</dt> - <dd style="width: auto;"> </dd> - <dt>D-Link DWA-131</dt> - <dd style="width: auto;"> </dd> - <dt>D-Link DWA-133</dt> - <dd style="width: auto;"> </dd> - <dt>D-Link DWA-135</dt> - <dd style="width: auto;"> </dd> - <dt>Digitus DN-7042</dt> - <dd style="width: auto;"> </dd> - <dt>Edimax EW-7811Un</dt> - <dd style="width: auto;"> </dd> - <dt>EDUP EP-N8508</dt> - <dd style="width: auto;"> </dd> - <dt>ELECOM WDC-150SU2M</dt> - <dd style="width: auto;"> </dd> - <dt>Full River FR-W100NUL</dt> - <dd style="width: auto;"> </dd> - <dt>Hercules Wireless N USB Pico HWNUp-150</dt> - <dd style="width: auto;"> </dd> - <dt>IO-DATA WN-G150UMW</dt> - <dd style="width: auto;"> </dd> - <dt>Mercusys MW150US v2</dt> - <dd style="width: auto;"> </dd> - <dt>Netgear WNA1000A</dt> - <dd style="width: auto;"> </dd> - <dt>Planex GW-USEco300</dt> - <dd style="width: auto;"> </dd> - <dt>Planex GW-USNano2</dt> - <dd style="width: auto;"> </dd> - <dt>Planex GW-USValue-EZ</dt> - <dd style="width: auto;"> </dd> - <dt>Planex GW-USWExtreme</dt> - <dd style="width: auto;"> </dd> - <dt>POWCHIP POW-N18</dt> - <dd style="width: auto;"> </dd> - <dt>Sitecom N300 USB (WLA-2102 v1)</dt> - <dd style="width: auto;"> </dd> - <dt>Sitecom WL-365</dt> - <dd style="width: auto;"> </dd> - <dt>Solwise NET-WL-UMD-606N</dt> - <dd style="width: auto;"> </dd> - <dt>TP-LINK TL-WN722N v2</dt> - <dd style="width: auto;"> </dd> - <dt>TP-LINK TL-WN723N v3</dt> - <dd style="width: auto;"> </dd> - <dt>TP-LINK TL-WN725N v2</dt> - <dd style="width: auto;"> </dd> - <dt>TP-LINK TL-WN821N</dt> - <dd style="width: auto;"> </dd> - <dt>TP-LINK TL-WN822N v4</dt> - <dd style="width: auto;"> </dd> - <dt>TP-LINK TL-WN823N v2</dt> - <dd style="width: auto;"> </dd> - <dt>TRENDnet TEW-648UBM</dt> - <dd style="width: auto;"> </dd> -</dl> -</div> -</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 - urtwn0 to join whatever network is available on boot, using WEP key - “0x1deadbeef1”, channel 11, obtaining an IP address using - DHCP:</p> -<div class="Bd Pp Bd-indent Li"> -<pre>nwkey 0x1deadbeef1 chan 11 -dhcp</pre> -</div> -<p class="Pp">Join an existing BSS network, “my_net”:</p> -<div class="Bd Pp Bd-indent Li"> -<pre># ifconfig urtwn0 192.168.1.1 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>urtwn%d: error %d, could not read firmware %s</dt> - <dd>For some reason, the driver was unable to read the microcode file from the - filesystem. The file might be missing or corrupted.</dd> - <dt>urtwn%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">netintro(4)</a>, - <a class="Xr">usb(4)</a>, <a class="Xr">ifconfig.if(5)</a>, - <a class="Xr">wpa_supplicant.conf(5)</a>, <a class="Xr">ifconfig(8)</a>, - <a class="Xr">wpa_supplicant(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">urtwn</code> device driver first appeared in - <span class="Ux">OpenBSD 4.9</span> and in <span class="Ux">NetBSD - 6.0</span>.</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">urtwn</code> driver was written by - <span class="An">Damien Bergamini</span> ⟨damien@openbsd.org⟩ - for <span class="Ux">OpenBSD</span> and ported to - <span class="Ux">NetBSD</span> by <span class="An">NONAKA Kimihiro</span> - ⟨nonaka@NetBSD.org⟩.</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">urtwn</code> driver does not support any of - the 802.11n capabilities offered by the adapters. Additional work is - required in <a class="Xr">ieee80211(9)</a> before those features can be - supported.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">May 26, 2024</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |