Re: Multiple interfaces, same technology

Hi Marcel, You can re-order services with MoveBefore and MoveAfter methods btw., but I think there is no test script for that. Actually there is one: test/service-move-before Tomasz ___ connman mailing list connman@connman.net http://lists.connman.net

Re: Connman 1.2 Open Issues

Hi Grant, > I ran connman-1.2 through it's paces today. I noticed two significant issues > right away: > > 1) An empty or commented out NetworkInterfaceBlacklist setting in main.conf > does not work. Patch submitted (see > http://lists.connman.net/pipermail/connman/2012-June/010241.html). thi

Re: Multiple interfaces, same technology

Hi Justin, > After hearing about all the cool things that connman can do, all built > in to a small daemon, I thought I'd give it a try. I'm using it on a > desktop system with multiple ethernet interfaces, and I'm a little > confused by what the default behavior is supposed to be. > > I have ea

Re: [PATCH] main: static-qualify default config values

Hi, On Wed, 2012-06-27 at 17:21 -0700, Grant Erickson wrote: > - char *default_auto_connect[] = { > + static char *default_auto_connect[] = { This isn't strictly necessary as default_auto_connect[] is only used locally as input to parse_service_types(). Cheers, Pat

Re: [PATCH] main: static-qualify default config values

Hi Grant, > The default configuration arrays default_auto_connect and > default_blacklist must be static-qualified. Otherwise, their > stack-allocated storage will go out of scope after parse_config > is finished and empty or commented-out DefaultAutoConnectTechnologies > or NetworkInterfaceBlack

Multiple interfaces, same technology

Hi all, After hearing about all the cool things that connman can do, all built in to a small daemon, I thought I'd give it a try. I'm using it on a desktop system with multiple ethernet interfaces, and I'm a little confused by what the default behavior is supposed to be. I have each network inte

Connman 1.2 Open Issues

I ran connman-1.2 through it's paces today. I noticed two significant issues right away: 1) An empty or commented out NetworkInterfaceBlacklist setting in main.conf does not work. Patch submitted (see http://lists.connman.net/pipermail/connman/2012-June/010241.html). 2) Named (e.g. pool.ntp.or

[PATCH] main: static-qualify default config values

The default configuration arrays default_auto_connect and default_blacklist must be static-qualified. Otherwise, their stack-allocated storage will go out of scope after parse_config is finished and empty or commented-out DefaultAutoConnectTechnologies or NetworkInterfaceBlacklist config entries w

Crash with 1.2 with Ctrl-C on Exit

connmand[1771]: ... connmand[1771]: src/rtnl.c:connman_rtnl_remove_watch() id 2 connmand[1771]: plugins/wifi.c:network_removed() name WiFi Activation connmand[1771]: plugins/wifi.c:network_removed() name Rock connmand[1771]: plugins/wifi.c:network_removed() name Scissors connmand[1771]: plugins/wif

ConnMan 1.2 has been released

Hello everyone, I am happy to announce our ConnMan 1.2 release. We fixed a few more bugs that have been discovered and added small features that got overlooked for 1.0 and 1.1 releases. Please upgrade and report back any issues. Regards Marcel ___ c

[PATCH] ofono: Fix potential crash

If a dummy context is created, it might happen that its index is equal to -1. In this particular case the IP address has not been copied to context->address during ipv4 extraction. If we force from oFono a context activation, it will make ConnMan crashing on set_connected(). --- plugins/ofono.c |