Changeset View
Standalone View
share/man/man4/iwm.4
| .\"- | |||||
| .\" SPDX-License-Identifier: BSD-2-Clause | |||||
| .\" | |||||
| .\" Copyright (c) 2004-2006 | .\" Copyright (c) 2004-2006 | ||||
| .\" Damien Bergamini <damien.bergamini@free.fr>. All rights reserved. | .\" Damien Bergamini <damien.bergamini@free.fr>. All rights reserved. | ||||
| .\" | .\" | ||||
| Context not available. | |||||
| .Nd Intel IEEE 802.11ac wireless network driver | .Nd Intel IEEE 802.11ac wireless network driver | ||||
| .Sh SYNOPSIS | .Sh SYNOPSIS | ||||
| To compile this driver into the kernel, | To compile this driver into the kernel, | ||||
| include the following lines in your | include the following lines in your kernel configuration file: | ||||
| kernel configuration file: | |||||
| .Bd -ragged -offset indent | .Bd -ragged -offset indent | ||||
| .Cd "device iwm" | .Cd "device iwm" | ||||
| .Cd "device pci" | .Cd "device pci" | ||||
| Context not available. | |||||
| .Sh DESCRIPTION | .Sh DESCRIPTION | ||||
| The | The | ||||
| .Nm | .Nm | ||||
| driver provides support for: | driver supports | ||||
bz: this is actually not fully correct I believe but probably good enough. I believe it does not… | |||||
| .Pp | |||||
| .Bl -tag -width Ds -offset indent -compact | |||||
| .It Intel Dual Band Wireless AC 3160 | |||||
| .It Intel Dual Band Wireless AC 3165 | |||||
| .It Intel Dual Band Wireless AC 3168 | |||||
| .It Intel Dual Band Wireless AC 7260 | |||||
| .It Intel Dual Band Wireless AC 7265 | |||||
| .It Intel Dual Band Wireless AC 8260 | |||||
| .It Intel Dual Band Wireless AC 8265 | |||||
| .It Intel Dual Band Wireless AC 9260 | |||||
| .It Intel Dual Band Wireless AC 9270 | |||||
| .It Intel Dual Band Wireless AC 946X | |||||
| .It Intel Dual Band Wireless AC 9560 | |||||
| .El | |||||
| .Pp | |||||
| .Nm | |||||
| supports | |||||
| .Cm station | .Cm station | ||||
| mode operation. | mode operation. | ||||
| Only one virtual interface may be configured at any time. | Only one virtual interface may be configured at any time. | ||||
| For more information on configuring this device, see | |||||
| .Xr ifconfig 8 . | |||||
| .Pp | |||||
| This driver requires the firmware built with the | This driver requires the firmware built with the | ||||
| .Nm iwmfw | .Nm iwmfw | ||||
| module to work. | module to work. | ||||
| .Pp | .Pp | ||||
| Currently, | For more information on configuring this device, see | ||||
| .Xr ifconfig 8 . | |||||
| .Sh HARDWARE | |||||
| The | |||||
| .Nm | .Nm | ||||
| only supports 802.11b and 802.11g modes. | driver provides support for: | ||||
| It will not associate to access points that are configured to operate only | .Pp | ||||
| in 802.11n or 802.11ac modes. | .Bl -bullet -compact | ||||
| .It | |||||
| Intel Dual Band Wireless AC 3160 | |||||
Done Inline ActionsAre we going to revert these too like https://github.com/freebsd/freebsd-src/pull/1462 does? I still wonder if that was something of the old script for the website (I should go and dig it up), which liked to parse things this way. bz: Are we going to revert these too like https://github.com/freebsd/freebsd-src/pull/1462 does?
I… | |||||
| .It | |||||
| Intel Dual Band Wireless AC 3165 | |||||
| .It | |||||
| Intel Dual Band Wireless AC 3168 | |||||
| .It | |||||
| Intel Dual Band Wireless AC 7260 | |||||
| .It | |||||
| Intel Dual Band Wireless AC 7265 | |||||
| .It | |||||
| Intel Dual Band Wireless AC 8260 | |||||
| .It | |||||
| Intel Dual Band Wireless AC 8265 | |||||
| .It | |||||
| Intel Dual Band Wireless AC 9260 | |||||
| .It | |||||
| Intel Dual Band Wireless AC 9270 | |||||
| .It | |||||
| Intel Dual Band Wireless AC 946X | |||||
| .It | |||||
| Intel Dual Band Wireless AC 9560 | |||||
| .El | |||||
| .Sh EXAMPLES | .Sh EXAMPLES | ||||
| Join an existing BSS network (i.e., connect to an access point): | Join an existing BSS network (i.e., connect to an access point): | ||||
| .Bd -literal -offset indent | .Bd -literal -offset indent | ||||
| ifconfig wlan create wlandev iwm0 inet 192.168.0.20 \e | # ifconfig wlan create wlandev iwm0 inet 192.0.2.0 \e | ||||
Done Inline Actions192.0.2.20/24 (and we can ditch the netmask line). 192.0.2.0 is the network address. bz: 192.0.2.20/24 (and we can ditch the netmask line). 192.0.2.0 is the network address. | |||||
| netmask 0xffffff00 | netmask 0xffffff00 | ||||
| .Ed | .Ed | ||||
| .Pp | .Pp | ||||
| Join a specific BSS network with network name | Join a specific BSS network with network name | ||||
| .Dq Li my_net : | .Ql my_net : | ||||
| .Pp | .Pp | ||||
| .Dl "ifconfig wlan create wlandev iwm0 ssid my_net up" | .Dl # ifconfig wlan create wlandev iwm0 ssid my_net up | ||||
Done Inline ActionsI don't think that all the # helps things, and it makes it harder to copy&paste commands. (without a #, in my terminal I can triple-click to copy the entire line; when it's there, I need to move the cursor after the # and drag it across) I know that you want to make it clear that this is a root command, but I think that's clear from the context. Also, none (or very few) other man-pages include $ or # chars to indicate whether it's for normal users or root. gperciva_tarsnap.com: I don't think that all the # helps things, and it makes it harder to copy&paste commands. | |||||
| .Pp | .Pp | ||||
| Join a specific BSS network with 64-bit WEP encryption: | Join a specific BSS network with 64-bit WEP encryption: | ||||
| .Bd -literal -offset indent | .Bd -literal -offset indent | ||||
| ifconfig wlan create wlandev iwm0 ssid my_net \e | # ifconfig wlan create wlandev iwm0 ssid my_net \e | ||||
| wepmode on wepkey 0x1234567890 weptxkey 1 up | wepmode on wepkey 0x1234567890 weptxkey 1 up | ||||
| .Ed | .Ed | ||||
| .Pp | .Pp | ||||
| Join a specific BSS network with 128-bit WEP encryption: | Join a specific BSS network with 128-bit WEP encryption: | ||||
| .Bd -literal -offset indent | .Bd -literal -offset indent | ||||
| ifconfig wlan create wlandev iwm0 wlanmode adhoc ssid my_net \e | # ifconfig wlan create wlandev iwm0 wlanmode adhoc ssid my_net \e | ||||
| wepmode on wepkey 0x01020304050607080910111213 weptxkey 1 | wepmode on wepkey 0x01020304050607080910111213 weptxkey 1 | ||||
| .Ed | .Ed | ||||
| .Sh DIAGNOSTICS | .Sh DIAGNOSTICS | ||||
| Context not available. | |||||
| .Xr wlan_ccmp 4 , | .Xr wlan_ccmp 4 , | ||||
| .Xr wlan_tkip 4 , | .Xr wlan_tkip 4 , | ||||
| .Xr wlan_wep 4 , | .Xr wlan_wep 4 , | ||||
| .Xr networking 7 , | |||||
| .Xr ifconfig 8 , | .Xr ifconfig 8 , | ||||
| .Xr wpa_supplicant 8 | .Xr wpa_supplicant 8 | ||||
| .Sh BUGS | |||||
| Currently, | |||||
| .Nm | |||||
| only supports 802.11 b/g modes. | |||||
Done Inline ActionsI would say a/b/g as it does support a bz: I would say a/b/g as it does support a | |||||
| It will not associate to access points that are configured to operate | |||||
| only in 802.11n or 802.11ac modes. | |||||
| Context not available. | |||||
this is actually not fully correct I believe but probably good enough. I believe it does not support all of them. We should probably say "most".
I'll add the word before committing.