gettingstarted
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
gettingstarted [2018/05/10 19:57] Denis Kenzior created |
gettingstarted [2022/04/01 16:47] James Prestwood |
||
|---|---|---|---|
| Line 46: | Line 46: | ||
| </code> | </code> | ||
| - | Now it is time to build iwd source itself. First we need to configure. If your system is not running systemd (like the test system in this example), then you should use '--disable-systemd-service' argument. | + | Now it is time to build iwd source itself. First we need to configure. There are some dependencies required to configure. They are libtool, readline development headers and glib development headers. For building the manual pages rst2man is also required (python-docutils package on some distros). |
| + | |||
| + | For debian based systems, run the following command | ||
| + | |||
| + | <code> | ||
| + | $ sudo apt install libtool libreadline-dev libdbus-glib-1-dev python-docutils | ||
| + | </code> | ||
| + | |||
| + | If your system is not running systemd (like the test system in this example), then you should use '--disable-systemd-service' argument. | ||
| <code> | <code> | ||
| Line 92: | Line 100: | ||
| scripts/config --enable CONFIG_CRYPTO_AES | scripts/config --enable CONFIG_CRYPTO_AES | ||
| scripts/config --enable CONFIG_CRYPTO_ECB | scripts/config --enable CONFIG_CRYPTO_ECB | ||
| - | scripts/config --enable CONFIG_CRYPTO_ARC4 | ||
| scripts/config --enable CONFIG_CRYPTO_DES | scripts/config --enable CONFIG_CRYPTO_DES | ||
| scripts/config --enable CONFIG_CRYPTO_CBC | scripts/config --enable CONFIG_CRYPTO_CBC | ||
| Line 119: | Line 126: | ||
| -p, --phys Phys to manage | -p, --phys Phys to manage | ||
| -P, --nophys Phys to ignore | -P, --nophys Phys to ignore | ||
| - | -c, --config Configuration directory to use | ||
| -l, --plugin Plugins to include | -l, --plugin Plugins to include | ||
| -L, --noplugin Plugins to exclude | -L, --noplugin Plugins to exclude | ||
| + | -d, --debug Enable debug output | ||
| + | -v, --version Show version | ||
| -h, --help Show help options | -h, --help Show help options | ||
| </code> | </code> | ||
| Line 134: | Line 142: | ||
| If your kernel is configured correctly, your iwd service should now be running. If iwd fails to start, pay attention to which kernel configuration are missing from your kernel and address those missing options first. | If your kernel is configured correctly, your iwd service should now be running. If iwd fails to start, pay attention to which kernel configuration are missing from your kernel and address those missing options first. | ||
| + | |||
| + | == Connecting to a Network == | ||
| + | |||
| + | For this HOWTO we will be using iwd's command line client, iwctl, starting it from the iwd build directory. The default DBus configuration requires users to be part of the netdev group. If you are not, add yourself: | ||
| + | |||
| + | <code> | ||
| + | usermod -a -G netdev <user> | ||
| + | </code> | ||
| + | |||
| + | iwctl should be shipped by default with most distributions, so if you are using iwd from a distribution package, you can simply invoke 'iwctl'. | ||
| + | |||
| + | <code> | ||
| + | denkenz@iwd-test ~/iwd $ client/iwctl | ||
| + | [iwd]# device list | ||
| + | Devices * | ||
| + | -------------------------------------------------------------------------------- | ||
| + | Name Address Powered Adapter Mode | ||
| + | -------------------------------------------------------------------------------- | ||
| + | wlp2s0b1 f6:1c:7f:ee:56:24 on phy2 station | ||
| + | </code> | ||
| + | |||
| + | Here we can see that this system has a single wireless device in 'station' mode, 'wlp2s0b1'. Lets try to find a network to connect to: | ||
| + | |||
| + | <code> | ||
| + | [iwd]# station wlp2s0b1 scan | ||
| + | [iwd]# station wlp2s0b1 get-networks | ||
| + | Available networks * | ||
| + | -------------------------------------------------------------------------------- | ||
| + | Network name Security Signal | ||
| + | -------------------------------------------------------------------------------- | ||
| + | TestWPA psk **** | ||
| + | TestWPA2 psk **** | ||
| + | </code> | ||
| + | |||
| + | As you can see there are two networks available. Lets connect to 'TestWPA2'. This network is a 'psk' network and requires a passphrase. When connecting to the network for the first time, iwd will ask you for the passphrase first. Type it in when prompted. For subsequent connections the passphrase entry will not be needed. | ||
| + | |||
| + | <code> | ||
| + | [iwd]# station wlp2s0b1 connect TestWPA2 | ||
| + | Type the network passphrase for TestWPA2 psk. | ||
| + | Passphrase: ********************* | ||
| + | [iwd]# station wlp2s0b1 get-networks | ||
| + | Available networks | ||
| + | -------------------------------------------------------------------------------- | ||
| + | Network name Security Signal | ||
| + | -------------------------------------------------------------------------------- | ||
| + | TestWPA psk **** | ||
| + | > TestWPA2 psk **** | ||
| + | </code> | ||
| + | |||
| + | As you can see, we should now be connected! | ||
gettingstarted.txt · Last modified: 2022/04/01 16:47 by James Prestwood
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
