Hi Marcel
On Fri, Oct 15, 2010 at 03:10, Marcel Holtmann wrote:
>> 2. (What do you think???) Convert the provisioning file to XML??
>
> Don't think this is a good idea since the INI style keyfiles are so
> simple that it is pretty nice.
>
> What benefit would XML give over key files.
>
This was j
Hi Lucio,
> Back to service provisioning (EAP configuration on the fly).
>
> So now I'll have some time to work on this.
>
> I think the easiest way to do this, is to add support for inotify for
> .config dir, and then add a Method to upload .config files that will
> be read on the fly.
in simp
Hello...
Back to service provisioning (EAP configuration on the fly).
So now I'll have some time to work on this.
I think the easiest way to do this, is to add support for inotify for
.config dir, and then add a Method to upload .config files that will
be read on the fly.
My plan is to:
1. Add
Hi Patrik,
> > I am not signing up for confusing the end user. If it is more than
> > username and password, it will not be exposed by the UI.
>
> Unfortunately I'm in the same camp as Kalle disagreeing on this one.
> Setting up WPA Enterprise WLANs must be possible even for the end user.
> In ad
On Fri, 2010-08-20 at 10:37 +0200, ext Marcel Holtmann wrote:
> I am not signing up for confusing the end user. If it is more than
> username and password, it will not be exposed by the UI.
Unfortunately I'm in the same camp as Kalle disagreeing on this one.
Setting up WPA Enterprise WLANs must be
Hi Kalle,
> >> There are WPA Enterprise networks just with a list of settings and
> >> possible screenshots of settings dialogs from different devices. Here
> >> are few examples I quickly googled:
> >>
> >> http://oregonstate.edu/helpdocs/wireless/getting-connected/OSU-secure
> >> http://www.oit
Marcel Holtmann writes:
> Hi Kalle,
Hi again Marcel,
>> There are WPA Enterprise networks just with a list of settings and
>> possible screenshots of settings dialogs from different devices. Here
>> are few examples I quickly googled:
>>
>> http://oregonstate.edu/helpdocs/wireless/getting-conn
Hi Kalle,
> >> I'm not following you here and I haven't looked connman EAP code (yet),
> >> so I maybe misunderstanding something. But are you saying that there
> >> should not be any UI for the EAP settings, Instead the user should
> >> receive an XML file from the network administrator and insta
Hi Marcel,
Marcel Holtmann writes:
>> I'm not following you here and I haven't looked connman EAP code (yet),
>> so I maybe misunderstanding something. But are you saying that there
>> should not be any UI for the EAP settings, Instead the user should
>> receive an XML file from the network admi
Marcel Holtmann wrote:
> > >> So, how that should work, we would pass a configuration filename for
> > >> connman,
> > >> that would set the service's settings and would save it to the proper
> > >> place so it will
> > >> read it every restart. Or just save the service settings using normal
> > >
Hi Kalle,
> >> So, how that should work, we would pass a configuration filename for
> >> connman,
> >> that would set the service's settings and would save it to the proper
> >> place so it will
> >> read it every restart. Or just save the service settings using normal
> >> service storage?
> >
>
Hi Lucio,
> > I must admit that I haven't spent much on the details here, but in
> > general I would you pass a configuration as string. This string for
> > example could be the same format or maybe better XML. As I said, the
> > only thing that I know is that we don't wanna do this via service
>
Hi Lucio,
> > I must admit that I haven't spent much on the details here, but in
> > general I would you pass a configuration as string. This string for
> > example could be the same format or maybe better XML. As I said, the
> > only thing that I know is that we don't wanna do this via service
>
Hi Marcel,
Marcel Holtmann writes:
>> So, how that should work, we would pass a configuration filename for connman,
>> that would set the service's settings and would save it to the proper
>> place so it will
>> read it every restart. Or just save the service settings using normal
>> service sto
> Hi Lucio,
Hi,
>
> I would really welcome that :)
Me too :)
>
> I must admit that I haven't spent much on the details here, but in
> general I would you pass a configuration as string. This string for
> example could be the same format or maybe better XML. As I said, the
> only thing that I know
Hi Lucio,
> >
> > yes, that is what I mean. Install provision configuration via a user
> > interface. And yes, the Manager interface sounds right. Are you planning
> > to work on that?
>
> Thats is up to my Manager, but I hope so.
I would really welcome that :)
> So, how that should work, we wo
Hi Samuel,
> > > > we don't really wanna do this and that is the reason why we never
> > > > exposed these information.
> > > Ok. got it.
> > >
> > > >
> > > > I prefer actually that loading configuration via D-Bus is implemented
> > > > than a bunch of WPA-Enterprise parameters that we can not e
Hi Marcel,
On Thu, Aug 12, 2010 at 03:57:05PM -0400, Marcel Holtmann wrote:
> Hi Lucio,
>
> > > we don't really wanna do this and that is the reason why we never
> > > exposed these information.
> > Ok. got it.
> >
> > >
> > > I prefer actually that loading configuration via D-Bus is implemented
> Hi Lucio,
Hello again
>
>
> yes, that is what I mean. Install provision configuration via a user
> interface. And yes, the Manager interface sounds right. Are you planning
> to work on that?
Thats is up to my Manager, but I hope so.
So, how that should work, we would pass a configuration filena
Hi Lucio,
> > we don't really wanna do this and that is the reason why we never
> > exposed these information.
> Ok. got it.
>
> >
> > I prefer actually that loading configuration via D-Bus is implemented
> > than a bunch of WPA-Enterprise parameters that we can not expose to the
> > end user any
> Hi Lucio,
Hi Marcel
>
> we don't really wanna do this and that is the reason why we never
> exposed these information.
Ok. got it.
>
> I prefer actually that loading configuration via D-Bus is implemented
> than a bunch of WPA-Enterprise parameters that we can not expose to the
> end user anyway
Hi Lucio,
> Support configuration of EAP parameters via service-api DBus
> interface.
> Also save and load EAP parameters from connman storage.
>
> Provisioned EAP services are still immutable and can't
> be changed using the service-api
> ---
> doc/service-api.txt | 77 ++
From: Lucio Maciel
Support configuration of EAP parameters via service-api DBus
interface.
Also save and load EAP parameters from connman storage.
Provisioned EAP services are still immutable and can't
be changed using the service-api
---
doc/service-api.txt | 77 ++
src/
23 matches
Mail list logo
