On 18.02.2013 09:58, Patrik Flykt wrote:
On Thu, 2013-02-14 at 13:38 +0100, Simon Busch wrote:
I have a similar case where something like this is needed. Anyone
already working on getting this implemented?
AFAIK not at the moment. I have a few things to do before I have a
chance to look at th
On Thu, 2013-02-14 at 13:38 +0100, Simon Busch wrote:
> I have a similar case where something like this is needed. Anyone
> already working on getting this implemented?
AFAIK not at the moment. I have a few things to do before I have a
chance to look at this. Patches are always welcome.
Cheers,
Am 15.01.2013 16:00, schrieb Patrik Flykt:
>> 1. Provide a default configuration .config file that sets the Ethernet
>> defaults to something static instead of DHCPv4. This would be good to
>> do some default factory configuration.
>
> This one is doable.
I have a similar case where something lik
Hi,
On Fri, 2013-01-11 at 14:36 +0100, Bach, Pascal wrote:
> 1. Provide a default configuration .config file that sets the Ethernet
> defaults to something static instead of DHCPv4. This would be good to
> do some default factory configuration.
This one is doable.
> 2. Allow the user to
On Fri, Jan 11, 2013 at 5:36 AM, Bach, Pascal wrote:
>
> > Just to be sure: all of you above want to provision/configure static
> > IPv4 (or IPv6) addresses before the ethernet cable is connected, right?
> >
>
> Provision is the most important use case for me. But I think there are two
> ways prov
On 11/01/13 13:36, Bach, Pascal wrote:
Just to be sure: all of you above want to provision/configure static
IPv4 (or IPv6) addresses before the ethernet cable is connected, right?
Provision is the most important use case for me. But I think there are two ways
provision could be done.
1. Pro
> Just to be sure: all of you above want to provision/configure static
> IPv4 (or IPv6) addresses before the ethernet cable is connected, right?
>
Provision is the most important use case for me. But I think there are two ways
provision could be done.
1. Provide a default configuration .config
On Fri, 2013-01-11 at 11:56 +, Jack Mitchell wrote:
> In this case, I have a program that runs over a serial port which can
> configure
> the ethernet. The user may want to pre-configure the device over
> serial,
> before
> installing it on-site.
Just to be sure: all of you above want to pro
On 11/01/13 11:43, Patrik Flykt wrote:
Hi,
On Fri, 2013-01-11 at 11:19 +0200, Jukka Rissanen wrote:
implement provisioning support i.e., .config file
support for ethernet devices
This would be the way to go for pre-configuration of ethernet services.
Connecting an ethernet cable gives
Hi,
On Fri, 2013-01-11 at 11:19 +0200, Jukka Rissanen wrote:
> implement provisioning support i.e., .config file
> support for ethernet devices
This would be the way to go for pre-configuration of ethernet services.
Connecting an ethernet cable gives a fully connected ethernet service
Hi all,
On 11.01.2013 11:07, Bach, Pascal wrote:
Hello
I'm looking to use connman as the network manager for a small NAS
device.
The device could have a wireless adapter, and one or two ethernet
adapters. I'd like to be able to show the user all the network
interfaces
on the box, and allow
Hello
> I'm looking to use connman as the network manager for a small NAS
> device.
> The device could have a wireless adapter, and one or two ethernet
> adapters. I'd like to be able to show the user all the network
> interfaces
> on the box, and allow them to configure them with or without a
Hi Patrik,
On Thu, Jan 10, 2013 at 11:02 PM, Patrik Flykt wrote:
> On Wed, 2013-01-09 at 18:07 -0800, Justin Maggard wrote:
> > Personally, it doesn't matter to me if it's in the service list, or in
> > some
> > other list. All I really want to do is find which interfaces connman
> > is
> > con
Hi,
On Wed, 2013-01-09 at 18:07 -0800, Justin Maggard wrote:
> Personally, it doesn't matter to me if it's in the service list, or in
> some
> other list. All I really want to do is find which interfaces connman
> is
> controlling (connected or disconnected), and configure them whether o
> -Original Message-
> From: connman-boun...@connman.net
> [mailto:connman-boun...@connman.net] On Behalf Of Justin Maggard
> Sent: Thursday, January 10, 2013 10:07 AM
> To: connman@connman.net
> Subject: Re: Pre-configuring an ethernet interface
>
> On Wed
On Wed, Jan 9, 2013 at 5:48 PM, Zheng, Jeff wrote:
> >
> > Thanks for the replies. I've actually tried every option available from
> > connmanctl, and even all the python test scripts. None of them will
> show my
> > ethernet interfaces until I plug in a cable and connman detects a
> carrier.
>
Hi Justin,
>
> Thanks for the replies. I've actually tried every option available from
> connmanctl, and even all the python test scripts. None of them will show my
> ethernet interfaces until I plug in a cable and connman detects a carrier.
>
I searched doc and found following sentence in o
On Wed, Jan 9, 2013 at 4:39 PM, Kok, Auke-jan H wrote:
> On Wed, Jan 9, 2013 at 4:32 PM, Felipe Ferreri Tonello
> wrote:
> > On 01/09/2013 11:17 AM, Justin Maggard wrote:
> >>
> >> I have a system with multiple ethernet interfaces, and I'm a bit
> confused
> >> as to how connman is expected to wo
On Wed, Jan 9, 2013 at 4:32 PM, Felipe Ferreri Tonello
wrote:
> On 01/09/2013 11:17 AM, Justin Maggard wrote:
>>
>> I have a system with multiple ethernet interfaces, and I'm a bit confused
>> as to how connman is expected to work with this. How can I get connman to
>> give me a list of all inter
On 01/09/2013 11:17 AM, Justin Maggard wrote:
I have a system with multiple ethernet interfaces, and I'm a bit confused
as to how connman is expected to work with this. How can I get connman to
give me a list of all interfaces, both with and without a carrier? The
You need to use the dbus int
I have a system with multiple ethernet interfaces, and I'm a bit confused
as to how connman is expected to work with this. How can I get connman to
give me a list of all interfaces, both with and without a carrier? The
docs in several places seem to imply that an interface with no carrier
would b
21 matches
Mail list logo