[PATCH v3 1/2] technology: trigger technology creation by new interface

From: Guillaume Lucas --- src/technology.c | 154 -- 1 files changed, 79 insertions(+), 75 deletions(-) diff --git a/src/technology.c b/src/technology.c index 7d89b2e..5ef3d10 100644 --- a/src/technology.c +++ b/src/technology.c @@ -139,81 +1

[PATCH v3 2/2] ethernet: Create the bridge before to add an interface to it.

From: Guillaume Lucas The bridge is created by the connman_technology_tethering_notify() function. So this function must be called before to add an interface to the bridge. Means before the call to connman_inet_add_to_bridge(). --- plugins/ethernet.c |4 ++-- 1 files changed, 2 insertions(+)

[PATCH v3 0/2] USB tethering

Hi, Following patch fix issues for USB tethering. Those patches was successfully tested in HW with latest version of connman and latest version of ofono. Patch "Call __connman_technology_add_interface() after rtnl->newlink()" from Martin is no more necessary with those patches. Regards, Guilla

RE: [PATCH v2 1/2] technology: trigger technology creation by new interface

Hi Samuel, > The patch looks fine, but when applied I get: > > cc1: warnings being treated as errors > src/technology.c: In function ‘technology_get’: > src/technology.c:144: error: implicit declaration of function > ‘technology_find’ Sorry, I've do not sent the good patch :( > > You should mo

[PATCH v2 2/2] ethernet: Create the bridge before to add an interface to it.

From: Guillaume Lucas The bridge is created by the connman_technology_tethering_notify() function. So this function must be called before to add an interface to the bridge. Means before the call to connman_inet_add_to_bridge(). --- plugins/ethernet.c |4 ++-- 1 files changed, 2 insertions(+)

[PATCH v2 1/2] technology: trigger technology creation by new interface

From: Guillaume Lucas --- src/technology.c | 198 +++-- 1 files changed, 101 insertions(+), 97 deletions(-) diff --git a/src/technology.c b/src/technology.c index ff1cf78..5ebd134 100644 --- a/src/technology.c +++ b/src/technology.c @@ -133,6 +13

[PATCH v2 0/2] USB tethering

Hi, Following patch fix issues for USB tethering. Those patches was successfully tested in HW with latest version of connman and latest version of ofono. Patch "Call __connman_technology_add_interface() after rtnl->newlink()" from Martin is no more necessary with those patches. Regards, Guilla

RE: [PATCH 1/2] ethernet: Add gadget driver

Hi Samuel > Although the code is right and certainly fixes our issue, I'm bothered > by the > fact that we need a device driver to create a technology, although we > know the > technology exists since we have an interface for it. In other words, I > don't > see why the technology creation could no

[PATCH 2/2] ethernet: Create the bridge before to add an interface to it.

From: Guillaume Lucas The bridge is created by the connman_technology_tethering_notify() function. So this function must be called before to add an interface to the bridge. Means before the call to connman_inet_add_to_bridge(). --- plugins/ethernet.c |4 ++-- 1 files changed, 2 insertions(+)

[PATCH 1/2] ethernet: Add gadget driver

From: Guillaume Lucas --- plugins/ethernet.c | 49 + 1 files changed, 49 insertions(+), 0 deletions(-) diff --git a/plugins/ethernet.c b/plugins/ethernet.c index 71dff3f..b9dc0a3 100644 --- a/plugins/ethernet.c +++ b/plugins/ethernet.c @@ -202,6

[PATCH 0/2] USB tethering

Hi, Following patch fix issues for USB tethering. Those patches was successfully tested in HW with latest version of connman and latest version of ofono. Patch "Call __connman_technology_add_interface() after rtnl->newlink()" from Martin is also mandatory for USB tethering. Regards, Guillaume

RE: USB tethering issues

Hi Martin, > I look through the code and find that I forget to push a updated patch. > Just pushed, you can patch it and try whether it can work. THX! I've updated my code with your patch. It's better as now the __connman_technology_add_interface() is called. But it's always failed for the USB

RE: USB tethering issues

Hi Martin, Hi Marcel, > > You might just have a kernel without bridge support by accident. I think > > we used to have a MeeGo bug open for that, but that got fixed. Same > > applies for having a kernel with proper set of netfilter modules for IP > > forwarding and masquerading. > MeeGo tethering

RE: USB tethering issues

Hi Martin, > > You might just have a kernel without bridge support by accident. I think > > we used to have a MeeGo bug open for that, but that got fixed. Same > > applies for having a kernel with proper set of netfilter modules for IP > > forwarding and masquerading. > MeeGo tethering feature is

RE: USB tethering issues

Hi Marcel, > there is one bridge for all Tethering. So it could be that this already > gets enabled for Bluetooth and then we don't create a second bridge for > USB. The bridge is shared and Bluetooth clients can talk to USB > clients. > That is on purpose. I agree, this is managed by the __connm

RE: USB tethering issues

Hi Marcel, > > > > We can see on it that nothing occurs when I run the enable-tethering > script and that the bridge is never created :( > > if the bridge does not get created, then no wonder that Tethering does > not work. > > Can you check with brctl (part of bridge-utils) that bridge support