From: Yuri D'Elia <wavexx@thregr.org>
To: iwd@lists.01.org
Subject: Re: iwctl force autoconnect
Date: Mon, 29 Mar 2021 18:32:07 +0200 [thread overview]
Message-ID: <871rbxnci9.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <0faae04d-6658-55d8-2d10-20da4e043917@mclink.it>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
> Il 29/03/2021 18:12, Denis Kenzior ha scritto:
>> So in theory this should always be happening. Once iwd is in
>> 'autoconnect' state (starting state, or when we lose a connection)
>> then any scan results triggered (either internal scanning logic or
>> scans triggered via dbus/iwctl) should then be considered for
>> autoconnect purposes. You say that 'it's not always the case'.
Indeed. AP disappears. Some time passes. I issue a 'station <net> scan'.
In some cases, iwd immediately connects to a known network. In some
other cases, I can see it with 'station <net> get-networks', but nothing
happens. Issuing a manual 'connect' will bring the network up
immediately.
>> Also, are you running any other network managers on top of iwd or
>> just iwd standalone?
I'm using iwd standalone.
On Mon, Mar 29 2021, Mauro Condarelli wrote:
> I am guessing he needs to re-enter 'autoconnect' state after an explicit
> disconnect.
I didn't explicitly disconnect in this case, but this makes me wonder if
iwd can exit the 'autoconnect' state by itself for some other reason.
> Use case for this would be to disconnect from the currently connected
> net and try to connect to some other, if available.
>
> What would be command sequence for this?
Would be curious about that too.
next prev parent reply other threads:[~2021-03-29 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 21:28 iwctl force autoconnect Yuri D'Elia
2021-03-29 16:12 ` Denis Kenzior
2021-03-29 16:29 ` Mauro Condarelli
2021-03-29 16:32 ` Yuri D'Elia [this message]
2021-03-29 16:37 ` Denis Kenzior
2021-03-29 17:09 ` Mauro Condarelli
2021-03-29 18:11 ` Denis Kenzior
2021-03-29 19:44 ` Mauro Condarelli
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=871rbxnci9.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox