All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
To: Daniel Wagner <wagi@monom.org>
Cc: connman@lists.linux.dev
Subject: Re: Network with same ssid question
Date: Fri, 14 Jan 2022 12:19:54 +0100	[thread overview]
Message-ID: <CAOf5uwn3TyX_mKLRmSy1Hk98esi-AbKV9rqjo3-oh0-hngKAHg@mail.gmail.com> (raw)
In-Reply-To: <03304641-cc5c-4150-277e-3ac77732f9f1@monom.org>

Hi Daniel

On Fri, Jan 14, 2022 at 12:17 PM Daniel Wagner <wagi@monom.org> wrote:
>
> Hi Michael,
>
> On 14.01.22 10:50, Michael Nazzareno Trimarchi wrote:
> > suppose you have 3 access point with different signal strength on a
> > network, the best will be connman select access point in the area
>
> This selection is done by the wpa_supplicant/iwd, not by ConnMan.

the wpa_supplicatan using wpa_cli show all the network so connman
can create several services with the same ssid name. The logic to what
service to connect is can not be done even in connman

>
> >>> IIRC, ConnMan merges those together and only exposes it one Service.
> >>
> >> is_duplicated the one that merges them? I think that in scenario when
> >> multiple access point
> >> are present we should not do it. I have seen that even iwd does not
> >> show duplicated. Is that correct?
>
> wpa_supplicant or iwd? I can't remember the wpa_supplicant details here.
> For iwd, all these stuff is done in iwd. Not ConnMan.

I have tested iwctl and wpa_cli. The first one show only one ssid the second one
all the access point. iw scan show all of them

Michael


>
> HTH,
> Daniel



-- 
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
michael@amarulasolutions.com
__________________________________

Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
info@amarulasolutions.com
www.amarulasolutions.com

  reply	other threads:[~2022-01-14 11:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 15:43 Network with same ssid question Michael Nazzareno Trimarchi
2022-01-13 16:05 ` Daniel Wagner
2022-01-13 16:08   ` Michael Nazzareno Trimarchi
2022-01-14  9:50     ` Michael Nazzareno Trimarchi
2022-01-14 11:17       ` Daniel Wagner
2022-01-14 11:19         ` Michael Nazzareno Trimarchi [this message]
2022-01-16  8:29           ` Marcel Holtmann
2022-01-16  8:43             ` Michael Nazzareno Trimarchi
2022-01-18  9:30               ` Marcel Holtmann

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=CAOf5uwn3TyX_mKLRmSy1Hk98esi-AbKV9rqjo3-oh0-hngKAHg@mail.gmail.com \
    --to=michael@amarulasolutions.com \
    --cc=connman@lists.linux.dev \
    --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 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.