[PATCH] tethering: Include definition for struct in6_addr

2013-03-04 Thread Daniel Wagner
From: Daniel Wagner daniel.wag...@bmw-carit.de The kernel header linux/if_bridge.h was updated with kernel 3.8 which includes a new 'struct br_mdb_entry' which has a member of type 'struct ip6'. See mainline kernel commit: ee07c6e7a6f8a25c18f0a6b18152fbd7499245f6 --- src/tethering.c | 1 + 1

Re: [PATCH] tethering: Include definition for struct in6_addr

2013-03-04 Thread Daniel Wagner
On 04.03.2013 15:17, Daniel Wagner wrote: From: Daniel Wagner daniel.wag...@bmw-carit.de The kernel header linux/if_bridge.h was updated with kernel 3.8 which includes a new 'struct br_mdb_entry' which has a member of type 'struct ip6'. See mainline kernel commit:

Re: [PATCH] service: Restart wispr on nameserver change

2013-03-04 Thread Forest Bond
Hi Patrik, On Fri, Jan 04, 2013 at 12:33:36PM +0200, Patrik Flykt wrote: On Wed, 2012-12-05 at 16:44 -0500, Forest Bond wrote: From: Forest Bond forest.b...@rapidrollout.com This is needed to make a service go online in the case where it was already connected and then manual IPv4

Re: [RFC 01/12] doc: Add method call and signal for tethering information

2013-03-04 Thread Marcel Holtmann
Hi Patrik, this does not look like an useful interface. I find it actually pretty ugly and glued on. It does not fit. So lets not do it this way. Yes, all attributes you mentioned describes it well. Martin wanted to see the code, so it was better to send it here early as an RFC. If we

Re: [RFC 01/12] doc: Add method call and signal for tethering information

2013-03-04 Thread MartinXu
Marcel: I do not even know what any of these information mean. What are they good for. What value are they providing. What would the user interface do with this information? The idea here is to provide a list of the clients that are tethered. Some additional information about each

Re: [RFC 01/12] doc: Add method call and signal for tethering information

2013-03-04 Thread Tomasz Bursztyka
Hi Martin, 1. MAC address of the remote devices What's the use case? Is there a plan to filter the access by MAC address like in android afterwards? Br, Tomasz ___ connman mailing list connman@connman.net

Re: [PATCH v2] wifi: Preliminary fix for autoscanning known hidden SSIDs

2013-03-04 Thread Sameer Naik
Hello Tomasz, I tested your patch and it works when there is only one provisioned hidden service (as expected). I will use this patch for now. Thanks and Regards ~Sameer On Fri, Mar 1, 2013 at 4:47 PM, Tomasz Bursztyka tomasz.burszt...@linux.intel.com wrote: Currently, it relies on

Re: [PATCH v2] wifi: Preliminary fix for autoscanning known hidden SSIDs

2013-03-04 Thread Tomasz Bursztyka
Hi Sameer, Hello Tomasz, I tested your patch and it works when there is only one provisioned hidden service (as expected). Thanks for testing it. I will do a patch for scanning the whole set, but I am a bit busy right now. Let's say end of next week. Br, Tomasz

Re: [RFC 01/12] doc: Add method call and signal for tethering information

2013-03-04 Thread Marcel Holtmann
Hi Martin, I do not even know what any of these information mean. What are they good for. What value are they providing. What would the user interface do with this information? The idea here is to provide a list of the clients that are tethered. Some additional information about each one