diff options
Diffstat (limited to 'static/freebsd/man4/run.4 3.html')
| -rw-r--r-- | static/freebsd/man4/run.4 3.html | 233 |
1 files changed, 233 insertions, 0 deletions
diff --git a/static/freebsd/man4/run.4 3.html b/static/freebsd/man4/run.4 3.html new file mode 100644 index 00000000..3d23fe58 --- /dev/null +++ b/static/freebsd/man4/run.4 3.html @@ -0,0 +1,233 @@ +<table class="head"> + <tr> + <td class="head-ltitle">RUN(4)</td> + <td class="head-vol">Device Drivers Manual</td> + <td class="head-rtitle">RUN(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">run</code> — <span class="Nd">Ralink + Technology USB IEEE 802.11a/g/n wireless network driver</span></p> +</section> +<section class="Sh"> +<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1> +<p class="Pp">To compile this driver into the kernel, place the following lines + in your kernel configuration file:</p> +<div class="Bd Pp Bd-indent"><code class="Cd">device ehci</code> +<br/> +<code class="Cd">device uhci</code> +<br/> +<code class="Cd">device ohci</code> +<br/> +<code class="Cd">device usb</code> +<br/> +<code class="Cd">device run</code> +<br/> +<code class="Cd">device wlan</code> +<br/> +<code class="Cd">device wlan_amrr</code></div> +<p class="Pp">Firmware is also needed, and provided by:</p> +<div class="Bd Pp Bd-indent"><code class="Cd">device runfw</code></div> +<p class="Pp">Alternatively, to load the driver as a module at boot time, place + the following lines in <a class="Xr">loader.conf(5)</a>:</p> +<div class="Bd Pp Bd-indent Li"> +<pre>if_run_load="YES" +runfw_load="YES"</pre> +</div> +</section> +<section class="Sh"> +<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> +<p class="Pp">The <code class="Nm">run</code> driver supports USB 2.0 wireless + adapters based on the Ralink RT2700U, RT2800U, RT3000U and RT3900E + chipsets.</p> +<p class="Pp">The RT2700U chipset consists of two integrated chips, an RT2770 + MAC/BBP and an RT2720 (1T2R) or RT2750 (dual-band 1T2R) radio + transceiver.</p> +<p class="Pp">The RT2800U chipset consists of two integrated chips, an RT2870 + MAC/BBP and an RT2820 (2T3R) or RT2850 (dual-band 2T3R) radio + transceiver.</p> +<p class="Pp">The RT3000U is a single-chip solution based on an RT3070 MAC/BBP + and an RT3020 (1T1R), RT3021 (1T2R) or RT3022 (2T2R) single-band radio + transceiver.</p> +<p class="Pp">The RT3900E is a single-chip USB 2.0 802.11n solution. The + MAC/Baseband Processor can be an RT3593, RT5390, RT5392 or an RT5592. The + radio can be an RT3053, RT5370, RT5372 or an RT5572. The RT3053 chip + operates in the 2GHz and 5GHz spectra and supports up to 3 transmit paths + and 3 receiver paths (3T3R). The RT5370 chip operates in the 2GHz spectrum + and supports 1 transmit path and 1 receiver path (1T1R). The RT5372 chip + operates in the 2GHz spectrum and supports up to 2 transmit paths and 2 + receiver paths (2T2R). The RT5572 chip operates in the 2GHz and 5GHz spectra + and supports up to 2 transmit paths and 2 receiver paths (2T2R).</p> +<p class="Pp">These are the modes the <code class="Nm">run</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>Host AP mode</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">run</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. The + <code class="Nm">run</code> driver offloads both encryption and decryption + of data frames to the hardware for the WEP40, WEP104, TKIP(+MIC) and CCMP + ciphers.</p> +<p class="Pp">The <code class="Nm">run</code> driver can be configured at + runtime with <a class="Xr">ifconfig(8)</a>.</p> +</section> +<section class="Sh"> +<h1 class="Sh" id="HARDWARE"><a class="permalink" href="#HARDWARE">HARDWARE</a></h1> +<p class="Pp">The <code class="Nm">run</code> driver supports the following + wireless adapters:</p> +<p class="Pp"></p> +<ul class="Bl-bullet Bd-indent Bl-compact"> + <li>Airlink101 AWLL6090</li> + <li>ASUS USB-N11</li> + <li>ASUS USB-N13 ver. A1</li> + <li>ASUS USB-N14</li> + <li>ASUS USB-N66</li> + <li>ASUS WL-160N</li> + <li>Belkin F5D8051 ver 3000</li> + <li>Belkin F5D8053</li> + <li>Belkin F5D8055</li> + <li>Belkin F6D4050 ver 1</li> + <li>Belkin F9L1103</li> + <li>Buffalo WLI-UC-AG300N</li> + <li>Buffalo WLI-UC-G300HP</li> + <li>Buffalo WLI-UC-G300N</li> + <li>Buffalo WLI-UC-G301N</li> + <li>Buffalo WLI-UC-GN</li> + <li>Buffalo WLI-UC-GNM</li> + <li>Buffalo WLI-UC-GNM2</li> + <li>Corega CG-WLUSB2GNL</li> + <li>Corega CG-WLUSB2GNR</li> + <li>Corega CG-WLUSB300AGN</li> + <li>Corega CG-WLUSB300GNM</li> + <li>D-Link DWA-130 rev B1</li> + <li>D-Link DWA-130 rev F1</li> + <li>D-Link DWA-140 rev B1, B2, B3, D1</li> + <li>D-Link DWA-160 rev B2</li> + <li>D-Link DWA-162</li> + <li>DrayTek Vigor N61</li> + <li>Edimax EW-7711UAn</li> + <li>Edimax EW-7711UTn</li> + <li>Edimax EW-7717Un</li> + <li>Edimax EW-7718Un</li> + <li>Edimax EW-7733UnD</li> + <li>Gigabyte GN-WB30N</li> + <li>Gigabyte GN-WB31N</li> + <li>Gigabyte GN-WB32L</li> + <li>Hawking HWDN1</li> + <li>Hawking HWUN1</li> + <li>Hawking HWUN2</li> + <li>Hercules HWNU-300</li> + <li>Linksys WUSB54GC v3</li> + <li>Linksys WUSB600N</li> + <li>Logitec LAN-W150N/U2</li> + <li>Mvix Nubbin MS-811N</li> + <li>Panda Wireless PAU06</li> + <li>Planex GW-USMicroN</li> + <li>Planex GW-US300MiniS</li> + <li>Sitecom WL-182</li> + <li>Sitecom WL-188</li> + <li>Sitecom WL-301</li> + <li>Sitecom WL-302</li> + <li>Sitecom WL-315</li> + <li>Sitecom WL-364</li> + <li>SMC SMCWUSBS-N2</li> + <li>Sweex LW303</li> + <li>Sweex LW313</li> + <li>TP-LINK TL-WDN3200</li> + <li>TP-LINK TL-WN321G v4</li> + <li>TP-LINK TL-WN727N v3</li> + <li>Unex DNUR-81</li> + <li>Unex DNUR-82</li> + <li>ZyXEL NWD2705</li> + <li>ZyXEL NWD210N</li> + <li>ZyXEL NWD270N</li> +</ul> +</section> +<section class="Sh"> +<h1 class="Sh" id="EXAMPLES"><a class="permalink" href="#EXAMPLES">EXAMPLES</a></h1> +<p class="Pp">Join an existing BSS network (i.e., connect to an access + point):</p> +<p class="Pp"></p> +<div class="Bd Bd-indent"><code class="Li">ifconfig wlan create wlandev run0 + inet 192.0.2.20/24</code></div> +<p class="Pp">Join a specific BSS network with network name + <var class="Ar">my_net</var>:</p> +<p class="Pp"></p> +<div class="Bd Bd-indent"><code class="Li">ifconfig wlan create wlandev run0 + ssid my_net up</code></div> +<p class="Pp">Join a specific BSS network with 64-bit WEP encryption:</p> +<div class="Bd Pp Bd-indent Li"> +<pre>ifconfig wlan create wlandev run0 ssid my_net \ + wepmode on wepkey 0x1234567890 weptxkey 1 up</pre> +</div> +<p class="Pp">Join a specific BSS network with 128-bit WEP encryption:</p> +<div class="Bd Pp Bd-indent Li"> +<pre>ifconfig wlan create wlandev run0 wlanmode adhoc ssid my_net \ + wepmode on wepkey 0x01020304050607080910111213 weptxkey 1</pre> +</div> +</section> +<section class="Sh"> +<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> +<dl class="Bl-diag"> + <dt>run%d: failed load firmware of file runfw</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>run%d: could not load 8051 microcode</dt> + <dd>An error occurred while attempting to upload the microcode to the onboard + 8051 microcontroller unit.</dd> + <dt>run%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">intro(4)</a>, <a class="Xr">netintro(4)</a>, + <a class="Xr">runfw(4)</a>, <a class="Xr">usb(4)</a>, + <a class="Xr">wlan(4)</a>, <a class="Xr">wlan_amrr(4)</a>, + <a class="Xr">wlan_ccmp(4)</a>, <a class="Xr">wlan_tkip(4)</a>, + <a class="Xr">wlan_wep(4)</a>, <a class="Xr">wlan_xauth(4)</a>, + <a class="Xr">networking(7)</a>, <a class="Xr">hostapd(8)</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">run</code> driver first appeared in + <span class="Ux">OpenBSD 4.5</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">run</code> driver was written by + <span class="An">Damien Bergamini</span> + <<a class="Mt" href="mailto:damien@openbsd.org">damien@openbsd.org</a>>.</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">run</code> driver supports some of the 11n + capabilities found in the RT2800, RT3000 and RT3900 chipsets.</p> +</section> +</div> +<table class="foot"> + <tr> + <td class="foot-date">April 1, 2025</td> + <td class="foot-os">FreeBSD 15.0</td> + </tr> +</table> |