Send connman mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."


Today's Topics:

   1. Re: Configuration file issues (Nuno Gon?alves)
   2. Re: Configuration file issues (Daniel Wagner)
   3. Re: hidden ssid connection  when service path is unknow
      (Alexandre Leblanc)


----------------------------------------------------------------------

Message: 1
Date: Fri, 23 Nov 2018 12:21:13 +0100
From: Nuno Gon?alves <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: Configuration file issues
Message-ID:
        <caexmxlt2ve8wcubqpanjumxijcu4m9mrpob3ynh9thoipoa...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On Fri, Nov 23, 2018 at 12:04 PM Daniel Wagner <[email protected]> wrote:

> The service is also in idle state. So that is okay. Do you expect that
> the autoconnect happens?
>
> > Default without config file: DHCP
> > I add a config file: Static
> > I remove the config file: Unconfigured.
> >
> > Maybe I missed any relevant field?
>
> And if you then tell ConnMan to connect given service?


Thanks Daniel.

I've tried it now, and even unplugging and plugging the cable back triggers
the DHCP configuration.

I don't fully understand the logic of connman, but in this case removing
the file does not have the same effect as having a file with DHCP
explicitly set, which is the default.

This additional connect step is required.

It does not seem right to me, I think removing the file should make it as
it was before, default and connected. But also...weak opinion here.

Thanks,
Nuno
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.01.org/pipermail/connman/attachments/20181123/16d7c9c2/attachment-0001.html>

------------------------------

Message: 2
Date: Fri, 23 Nov 2018 12:56:37 +0100
From: Daniel Wagner <[email protected]>
To: Nuno Gon?alves <[email protected]>
Cc: [email protected]
Subject: Re: Configuration file issues
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi Nuno,

On 11/23/18 12:21 PM, Nuno Gon?alves wrote:
> This additional connect step is required.
> 
> It does not seem right to me, I think removing the file should make it 
> as it was before, default and connected. But also...weak opinion here.

ConnMan usually tries to do what the user has indented. That means if 
you plug in an ethernet cable, ConnMan tries to use it.

When removing an configuration file we just don't trigger the auto 
connect code. I don't think anyone really considering this so far 
because I don't suppose you are going to add and remove configuration 
files all the time.

Thanks,
Daniel


------------------------------

Message: 3
Date: Fri, 23 Nov 2018 09:29:57 -0500 (EST)
From: Alexandre   Leblanc <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: connman <[email protected]>, [email protected]
Subject: Re: hidden ssid connection  when service path is unknow
Message-ID:
        <502160633.164143.1542983397045.javamail.zim...@savoirfairelinux.com>
Content-Type: text/plain; charset=utf-8

Hello Daniel

I do indeed see the service with hidden network and I provide an agent with the 
correct format.  Looking at the code I actually managed to isolate all the 
hidden network and try a connection on all of them. So this is actually now 
resolved. Thank you !

Alexandre Leblanc
Free Software Consultant | Montreal, Qc
Savoir-faire Linux
Office: (+ 1) 514 276-5468 ext.377

Confidentiality Message: This communication (including any files transmitted 
with it) is intended solely for the person or entity to whom it is addressed, 
and may contain confidential or privileged information. 
The disclosure, distribution or copying of this message is strictly forbidden. 
Should you have received this communication in error, kindly contact the sender 
promptly, destroy any copies and delete this message from your computer system.

----- Message original -----
De: "Daniel Wagner" <[email protected]>
?: "Alexandre Leblanc" <[email protected]>
Cc: "connman" <[email protected]>, [email protected]
Envoy?: Vendredi 23 Novembre 2018 00:34:30
Objet: Re: hidden ssid connection  when service path is unknow

Hi,

On Thu, Nov 15, 2018 at 04:10:29PM -0500, Alexandre Leblanc wrote:
> Hello everyone
> 
> I'm trying do develop a small wrapper around connmam mostly using dbus and 
> python. Everything work fine yet. 
> Managing hidden network is a bit of an issue.

That is an understatement from my past experience.

> The  wrapper will be use in an environment where there will be a lot of 
> hidden network (not for security reason...) 
> and only the ssid Name will be known. 
> So how would one identity the right service to connect to ? 
> Using my wrapper I can already see hidden network path. 
> I already know that my agent will handle the ssid Name when a connection 
> request is done. 
> Should I simply try connect to all of them ?

I haven't done anything for a while with hidden networks. The documentation 
says following

service-api.txt:

[...]

        void Connect()
                        [...]

                        Calling Connect() on a hidden WiFi service entry will
                        query the missing SSID via the Agent API causing a
                        WiFi service with the given SSID to be scanned,
                        created and connected.

IIRC, you should see a service for the hidden networks. Do you provide
an agent for ConnMan to call?

Thanks,
Daniel


------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman


------------------------------

End of connman Digest, Vol 37, Issue 13
***************************************

Reply via email to