From: Emil Velikov <emil.l.velikov@gmail.com>
To: Dimitri John Ledkov <dimitri.ledkov@canonical.com>
Cc: iwd@lists.linux.dev
Subject: Re: [PATCH] eap-mschapv2: allow using on kernels without CRYPTO_MD4, and deprecate
Date: Tue, 24 Oct 2023 23:26:53 +0100 [thread overview]
Message-ID: <CACvgo51cspY9BgZoKmPDKuOqJXmMZxfh1K2Wsvr4Kxs_ua2-Mw@mail.gmail.com> (raw)
In-Reply-To: <CADWks+au-HzFjSopfHYnpz3kUW1uOR7aEFTe_m0qHfVvJPcfFA@mail.gmail.com>
Hello Dmitry, all,
On Sat, 21 Oct 2023 at 01:34, Dimitri John Ledkov
<dimitri.ledkov@canonical.com> wrote:>
> On Thu, 19 Oct 2023 at 03:54, Denis Kenzior <denkenz@gmail.com> wrote:
> > Wasn't Ubuntu going to switch to iwd at some point?
>
Was interested in the same question, only to see the somewhat familiar
struggles. Namely, we've battled similar dragons with the SteamDeck so
I thought I'd share the tricks we used.
>... most notably seemingly failing to configure and use
> eap-mschapv2 via NetworkManager GUI,
My debugging over one years ago, indicated that NM was correctly
creating the iwd profile for enterprisy networks, then attempting a
connection _only_ if iwd would advertise it as KnownNetwork.
Which in itself is inherently racy with NM running multiple threads
and communicating with iwd via d-bus. For use I removed that code, so
that NM would issue a connect and if iwd fails with
AlreadyProvisioned, it would then retry to connect with
the-flag-I-do-no-remember-the-name-of flipped.
There was an upstream NM merge request for that, although the
maintainer added additional checking, which only increased the
(re)connection delay without improving the success rate in our tests.
> ... or keep existing configuration
> working after the switch.
The problematic cases we've observed had extra tokens from the
wpa-supplicant based connection profiles. So you can try removing the
following:
mac-address interface-name permissions bssid
In addition, we pruned all files in /var/lib/NetworkManager/
HTH
Emil
prev parent reply other threads:[~2023-10-24 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 23:54 [PATCH] eap-mschapv2: allow using on kernels without CRYPTO_MD4, and deprecate Dimitri John Ledkov
2023-10-16 19:45 ` Denis Kenzior
2023-10-18 16:28 ` Dimitri John Ledkov
2023-10-19 2:54 ` Denis Kenzior
2023-10-21 0:33 ` Dimitri John Ledkov
2023-10-24 22:26 ` Emil Velikov [this message]
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=CACvgo51cspY9BgZoKmPDKuOqJXmMZxfh1K2Wsvr4Kxs_ua2-Mw@mail.gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=dimitri.ledkov@canonical.com \
--cc=iwd@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).