connman.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "VAUTRIN Emmanuel (Canal Plus Prestataire)" <Emmanuel.VAUTRIN@cpexterne.org>
To: Daniel Wagner <wagi@monom.org>
Cc: Denis Kenzior <denkenz@gmail.com>,
	"connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: RE: [PATCH v2] iwd: Always disconnect connection completely
Date: Mon, 28 Feb 2022 11:21:44 +0000	[thread overview]
Message-ID: <MRZP264MB154417BCA30F1C47EDE6DAC793009@MRZP264MB1544.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220227180930.ruqnmsgtei26zq4n@beryllium.lan>

Hi Daniel,
> If I understood it correctly, you are saying ConnMan receives a
> Disconnect call via D-Bus, it is forwarded to iwd and wait for iwd to
> respond that the network is disconnected. Then ConnMan replies the
> initial posted Disconnect call to the user back. The user posts then
> Connect() which is too fast?
I switch between 2 known secure networks.
I have retried this morning with the following sequence:
gdbus call --system -d net.connman -o $PATH1 -m net.connman.Service.Disconnect
()
gdbus call --system -d net.connman -o $PATH2 -m  net.connman.Service.Connect
()
gdbus call --system -d net.connman -o $PATH1 -m net.connman.Service.Connect
Error: GDBus.Error:net.connman.Error.Failed: Input/output error

I think that the D-Bus reply of the Disconnect is immediate and does not wait for
the network to be really disconnected or on error, contrary to the Connect, which
really waits for the connection to be effective before replying.
I thought it was on purpose.

Best Regards,

Emmanuel

  reply	other threads:[~2022-02-28 11:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220124085336.3641685-1-Emmanuel.VAUTRIN@cpexterne.org>
2022-01-24  9:06 ` [PATCH v2] iwd: Always disconnect connection completely VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-01-25  9:50   ` Daniel Wagner
2022-01-25 10:43     ` VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-01-25 10:57       ` Daniel Wagner
2022-01-25 16:25         ` Denis Kenzior
2022-02-08 15:33           ` VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-02-21  9:10             ` VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-02-21 16:44               ` Daniel Wagner
2022-02-21 16:53                 ` VAUTRIN Emmanuel (Canal Plus Prestataire)
2022-02-27 18:09                   ` Daniel Wagner
2022-02-28 11:21                     ` VAUTRIN Emmanuel (Canal Plus Prestataire) [this message]
2022-03-04  8:05                       ` Daniel Wagner
2022-03-04  8:51                         ` VAUTRIN Emmanuel (Canal Plus Prestataire)

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=MRZP264MB154417BCA30F1C47EDE6DAC793009@MRZP264MB1544.FRAP264.PROD.OUTLOOK.COM \
    --to=emmanuel.vautrin@cpexterne.org \
    --cc=connman@lists.linux.dev \
    --cc=denkenz@gmail.com \
    --cc=wagi@monom.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).