From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: missing options to get iwd running
Date: Wed, 23 Dec 2020 03:07:06 +0100 [thread overview]
Message-ID: <20201223020706.Hlq2Tl5R0cgkXTL-BWX01qe-Jt_7HAnhrSadFIvhdB0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27346@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
New comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/issues/27346#issuecomment-749881365
Comment:
Was able to enable those options and get the daemon running. Whenever I tried to connect to a station I received a message "Operation failed" in the client.
Full logs:
daemon:
```
Wireless daemon version 1.10
station: Network configuration is disabled.
Wiphy: 0, Name: phy0
Permanent Address: 6c:21:a2:e8:35:47
Bands: 2.4 GHz 5 GHz
Ciphers: CCMP TKIP BIP
Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Wiphy phy0 will only use the default interface
ation4-Way handshake failed for ifindex: 2, reason: 15
4-Way handshake failed for ifindex: 2, reason: 15
Received Deauthentication event, reason: 3, from_ap: true
```
iwctl client:
```
[iwd]# station wlan0 connect <<SSID>>
Type the network passphrase for <<SSID>> psk.
Passphrase: ************
Operation failed
```
dmesg (this is the only message that seemed relevant/new):
```
alg: No test for hmac(md4) (hmac(md4-generic))
```
next prev parent reply other threads:[~2020-12-23 2:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 8:23 [ISSUE] " Johnnynator
2020-12-22 16:47 ` CameronNemo
2020-12-23 2:06 ` CameronNemo
2020-12-23 2:07 ` CameronNemo [this message]
2020-12-31 21:06 ` ericonr
2020-12-31 21:11 ` CameronNemo
2021-01-21 14:28 ` ericonr
2021-01-21 20:46 ` CameronNemo
2021-01-21 20:50 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201223020706.Hlq2Tl5R0cgkXTL-BWX01qe-Jt_7HAnhrSadFIvhdB0@z \
--to=cameronnemo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).