[PATCH */1] let loopback set up loop back device even it is up

The patch is used to fix bug : http://bugzilla.moblin.org/show_bug.cgi?id=5829 If loopback device is up, and does not setup properly, (address 127.0.0.1 Mask 255.0.0.0). loopback plugin will not setup it any more. So it makes the dnsproxy_resolver can not be registered. As a result, only resolvfi

[PATCH 1/1] let loopback set up loop back device even it is up

--- plugins/loopback.c |6 -- 1 files changed, 0 insertions(+), 6 deletions(-) diff --git a/plugins/loopback.c b/plugins/loopback.c index 59716c2..44adfee 100644 --- a/plugins/loopback.c +++ b/plugins/loopback.c @@ -191,12 +191,6 @@ static int setup_loopback(void) goto don

Re: Connman 0.40 regression from 0.19

Hi Marcel, 2009/9/2 Marcel Holtmann : >> I also noticed that -I cmd line option is not used anywhere so perhaps >> it could be removed alltogether from the code. > > The -I should do the exact opposite. Allow all interfaces except that > one. Kinda nice if you wanna exclude eth0 for example. > > R

Re: Connman 0.40 regression from 0.19

Hi Jukka, > I just noticed a regression in 0.40 (compared to 0.19). > > I have two network interfaces (wlan0 and usb0) in host and want to > only enable wlan0 interface so I use >/usr/sbin/connmand -n -i wlan* > to start connmand. > In 0.19 this worked ok, my usb0 interface was left intac

Connman 0.40 regression from 0.19

Hi, I just noticed a regression in 0.40 (compared to 0.19). I have two network interfaces (wlan0 and usb0) in host and want to only enable wlan0 interface so I use /usr/sbin/connmand -n -i wlan* to start connmand. In 0.19 this worked ok, my usb0 interface was left intact and I could use it