Re: RFC: D-Bus access to all configured services

2015-07-10 Thread Slava Monich
On 10/07/15 16:07, Tomasz Bursztyka wrote: > Hi Slava, > >> connman is a piece of middleware, its >> job is to provide the functionality and leave it to UI designers to >> decide what to show, what not to show and how to present it to the user. > > That's a debate on its own. > > Actually, I don'

Re: RFC: D-Bus access to all configured services

2015-07-10 Thread Patrik Flykt
On Fri, 2015-07-10 at 15:45 +0300, Slava Monich wrote: > 1. To see the password (if you have forgotten it) or proxy > configuration (to copy/paste it into the new configuration) We wasted a few hours thinking on this once upon a time, and concluded that we'll either be close to the AP to verify th

Re: RFC: D-Bus access to all configured services

2015-07-10 Thread Tomasz Bursztyka
Hi Slava, All D-Bus calls (except for "Connect" obviously) would work for unavailable service just as they do for available services. The main use case is wifi. The user has to be able to see the list of configured wifi networks, edit their properties, remove them etc. For other types of servic

Re: RFC: D-Bus access to all configured services

2015-07-10 Thread Marcel Holtmann
Hi Slava, >>> Does upstream have any interest in providing D-Bus access to all >>> configured services, including those that have no network associated >>> with it? Before I start writing any code, I would like to know whether >>> it's going to be accepted upstream or will remain part of our fork.

Re: RFC: D-Bus access to all configured services

2015-07-10 Thread Slava Monich
On 10/07/15 14:56, Tomasz Bursztyka wrote: > Hi Slava, > >> All D-Bus calls (except for "Connect" >> obviously) would work for unavailable service just as they do for >> available services. >> >> The main use case is wifi. The user has to be able to see the list of >> configured wifi networks, edit

Re: RFC: D-Bus access to all configured services

2015-07-10 Thread Slava Monich
On 10/07/15 14:51, Marcel Holtmann wrote: > Hi Slava, > >> Does upstream have any interest in providing D-Bus access to all >> configured services, including those that have no network associated >> with it? Before I start writing any code, I would like to know whether >> it's going to be accepted

Re: RFC: D-Bus access to all configured services

2015-07-10 Thread Tomasz Bursztyka
Hi Slava, All D-Bus calls (except for "Connect" obviously) would work for unavailable service just as they do for available services. The main use case is wifi. The user has to be able to see the list of configured wifi networks, edit their properties, remove them etc. For other types of servic

Re: RFC: D-Bus access to all configured services

2015-07-10 Thread Marcel Holtmann
Hi Slava, > Does upstream have any interest in providing D-Bus access to all > configured services, including those that have no network associated > with it? Before I start writing any code, I would like to know whether > it's going to be accepted upstream or will remain part of our fork. > > Ba

Effect of dnsproxy errors in tethering and Natting in conMan

2015-07-10 Thread Sukanya Ch
Hi, I am using connMan-1.29 version in ARM platform. I was able to make AP using tethering in connMan. But when I was connected to this AP I was not able to get internet access in client connected to this AP. I checked iptables.Those are fine. The only difference I found here and in x86 is in dns

RFC: D-Bus access to all configured services

2015-07-10 Thread Slava Monich
Does upstream have any interest in providing D-Bus access to all configured services, including those that have no network associated with it? Before I start writing any code, I would like to know whether it's going to be accepted upstream or will remain part of our fork. Basically the idea is to