en:users:documentation:iw
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:users:documentation:iw [2016/09/05 20:42] Jens Steinhauser revert "corrected type from "mBm" to "dBm"" |
en:users:documentation:iw [2024/05/17 21:28] (current) Jefferson Carpenter |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| iw is a new [[en/developers/Documentation/nl80211|nl80211]] based CLI configuration utility for wireless devices. It supports all new drivers that have been added to the kernel recently. The old tool iwconfig, which uses Wireless Extensions interface, is deprecated and it's strongly recommended to switch to iw and nl80211. | iw is a new [[en/developers/Documentation/nl80211|nl80211]] based CLI configuration utility for wireless devices. It supports all new drivers that have been added to the kernel recently. The old tool iwconfig, which uses Wireless Extensions interface, is deprecated and it's strongly recommended to switch to iw and nl80211. | ||
| - | Like rest of Linux kernel, iw is still under development. Features are added 'as we go'. The only documentation for iw is this page and output from 'iw help'. Please help expand this page. | + | Like the rest of the Linux kernel, iw is still under development. Features are added 'as we go'. The only documentation for iw is this page and output from 'iw help'. Please help expand this page. |
| There is a page listing use cases with iwconfig and iw: [[en/users/Documentation/iw/replace-iwconfig|replacing iwconfig]]. | There is a page listing use cases with iwconfig and iw: [[en/users/Documentation/iw/replace-iwconfig|replacing iwconfig]]. | ||
| Line 194: | Line 194: | ||
| For example to add a monitor interface: | For example to add a monitor interface: | ||
| <code>iw phy phy0 interface add moni0 type monitor</code> | <code>iw phy phy0 interface add moni0 type monitor</code> | ||
| - | where you can replace <code>monitor</code> by anything else and <code>moni0</code> by the interface name, and need to replace <code>phy0</code> by the PHY name for your hardware (usually phy0 will be correct unless you hotplugged or reloaded any modules.) If your udev is configured incorrectly, the newly created virtual interface may be renamed by it right away, use <code>ip link</code> to list all interfaces. To create a new managed mode interface you would use: | + | where you can replace <code>monitor</code> by any other supported mode and <code>moni0</code> by the interface name, and need to replace <code>phy0</code> by the PHY name for your hardware (usually phy0 will be correct unless you hotplugged or reloaded any modules.) If your udev is configured incorrectly, the newly created virtual interface may be renamed by it right away, use <code>ip link</code> to list all interfaces. To create a new managed mode interface you would use: |
| Line 244: | Line 244: | ||
| Where "alpha2" is the [[http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2|ISO/IEC 3166 alpha2]] country code. The information used and set comes from our [[en/developers/Regulatory|regulatory infrastructure]]. | Where "alpha2" is the [[http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2|ISO/IEC 3166 alpha2]] country code. The information used and set comes from our [[en/developers/Regulatory|regulatory infrastructure]]. | ||
| - | You can also use the latest wpa_supplicant (as of 0.6.7) now to change your regulatory domain, to do so just add a "COUNTRY=US" entry into your configuration for example. | + | You can also use the latest wpa_supplicant (as of 0.6.7) now to change your regulatory domain, to do so just add a "country=US" entry into your configuration for example. |
en/users/documentation/iw.1473108174.txt.gz · Last modified: 2016/09/05 20:42 by Jens Steinhauser
Page Tools
