From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: Failing to resolve after roams
Date: Thu, 12 Aug 2021 12:12:24 -0500 [thread overview]
Message-ID: <c11a18de-19a8-54c9-19f6-6593a5537833@gmail.com> (raw)
In-Reply-To: <CACsRnHVsREZ=Z6Gj=pkpPbJ+N7037q=01Uj_MhjYDbhLtTPQKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
Hi Michael,
On 8/12/21 11:57 AM, Michael Johnson wrote:
> Hi Denis,
>
> Using dbus-monitor I can see that networkd is sending out messages
> during a roam despite being set to "Unmanaged" for this interface.
> This appears to trigger a resolved message which I'm guessing is where
> the problem is.
So carrier disappearing is expected. Kernel/driver takes away the carrier when
it disassociates from the current AP. Carrier should be restored once we
associate to the new AP and iwd should be setting the device back up after the
roam. This happens in netdev_connect_ok(), l_rtnl_set_linkmode_and_operstate()
invocation.
What is unclear is why the carrier is sometimes not restored according to
networkd. Looking at the log in your first post on this topic I see that
station_fast_transition_cb() is called and station goes from roaming to
connected state. So that would imply that netdev_connect_ok is called in the
'failure' case (since connect_cb would be set to station_fast_transition_cb) and
we should have restored carrier earlier.
Any chance you have iwmon logs of this happening?
Regards,
-Denis
next prev parent reply other threads:[~2021-08-12 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 10:58 Failing to resolve after roams Michael Johnson
2021-08-12 14:22 ` Denis Kenzior
2021-08-12 14:30 ` Michael Johnson
2021-08-12 14:40 ` Denis Kenzior
2021-08-12 16:57 ` Michael Johnson
2021-08-12 17:12 ` Denis Kenzior [this message]
2021-08-12 17:41 ` Michael Johnson
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=c11a18de-19a8-54c9-19f6-6593a5537833@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.