I am working on a system where a USB dongle is used for Wi-Fi functionality.
The Wi-Fi can be used in client or access point mode, configurable. However, it
seems it's not possible to enable/disable tethering mode while the USB Wi-Fi
device is not currently plugged in. E.g.:
# connmanctl te
I've been looking into extending connmanctl's functionality with configuration
for the net.connman.Clock API. I've been developing a command that can set
clock properties, similar to the existing "config" command.
I've noticed that when multiple parameters are set, then the 'return' function
is
> I've noticed that on ConnMan 1.30, net.connman.Clock property Timezone
> isn't updating when /etc/localtime gets changed.
>
> I found this old message which sounds similar -- "[PATCH] timezone: Fix
> timezone can't auto update, file localtime permission issue":
> https://lists.connman.net/piperm
Hi Patrik,
On 10/13/2015 11:32 AM, Patrik Flykt wrote:
> Hi,
>
> On Tue, 2015-10-13 at 08:49 +, John Ernberg wrote:
>
>> ConnMan runs on the embedded system, which is the USB host side.
>> And when an USB gadget connects, I want to start a DHCP server on the
>> interface provided by cdc
On Oct 13, 2015, at 11:01 PM, Patrik Flykt wrote:
> On Tue, 2015-10-13 at 14:42 -0700, Naveen Singh wrote:
>
>> There is nothing that application knows that connman does not know.
>> In fact application gets to know through connman that connection did
>> not go through. The way application gets c
On Tue, 2015-10-13 at 14:42 -0700, Naveen Singh wrote:
> There is nothing that application knows that connman does not know.
> In fact application gets to know through connman that connection did
> not go through. The way application gets connected back is to initiate
> a scan and hoping that one
I've noticed that on ConnMan 1.30, net.connman.Clock property Timezone isn't
updating when /etc/localtime gets changed.
I found this old message which sounds similar -- "[PATCH] timezone: Fix
timezone can't auto update, file localtime permission issue":
https://lists.connman.net/pipermail/connma
On Tue, Oct 13, 2015 at 1:00 AM, Patrik Flykt
wrote:
>
> Hi,
>
> On Mon, 2015-10-12 at 21:46 -0700, Naveen Singh wrote:
> > In my previous email when I meant *"**User could be initiating scan" *I
> > actually meant "*Application could be initiating scan".*
>
> Well, don't. Now the respons
Thanks Patrik,
I've seen that the Connman version I'm working with is the 1.29 and that in
1.30 some fixs have been done on ipv4 configuration.
Maybe it is worth to update my version first.
Thanks & Regards
Francesco
> Subject: Re: net.connman.Service s
Hi,
On Tue, 2015-10-13 at 08:49 +, John Ernberg wrote:
> ConnMan runs on the embedded system, which is the USB host side.
> And when an USB gadget connects, I want to start a DHCP server on the
> interface provided by cdc_ether so that the USB gadget that connects
> can receive an IP
Hi Patrik,
On 10/13/2015 10:21 AM, Patrik Flykt wrote:
> Hi,
>
> On Mon, 2015-10-12 at 14:26 +, John Ernberg wrote:
>
>> I'm using Connman in an embedded environment where a device will connect
>> to us over USB, this device will provide an ethernet interface on the
>> USB port, and the
On Tue, 2015-10-13 at 04:22 +, francobrun...@hotmail.com wrote:
> Thanks.
>
> Are you able to change IPv4 configuration? I'm getting not supported error.
'IPv4.Configuration' is the property to change. On low-level the
attribute is an 'sv' with the variant 'v' containing a dict which is of
th
Hi,
On Mon, 2015-10-12 at 14:26 +, John Ernberg wrote:
> I'm using Connman in an embedded environment where a device will connect
> to us over USB, this device will provide an ethernet interface on the
> USB port, and the device will be in gadget mode.
> Thus when they connect to u
Hi,
On Mon, 2015-10-12 at 21:46 -0700, Naveen Singh wrote:
> In my previous email when I meant *"**User could be initiating scan" *I
> actually meant "*Application could be initiating scan".*
Well, don't. Now the responsibility of correct behavior is taken away
from ConnMan and placed on
14 matches
Mail list logo
