Hi Tomasz,
I have a question about this interface:
How does ConnMan support the remote peer which only support PIN?
On 08/01/2014 07:16 PM, Tomasz Bursztyka wrote:
+ Requesting the WPS details when connecting to a peer:
+
+ RequestPeerAuthorization("/peer4",
Don't interpret this, this function is just here because of my
refactorization of dhcp.c
"On network" it will try to apply something yes: so it can return true
or false in this specific case.
If there is no network is silently make the function to poss, so
returning true.
Exactly as apply_dh
Hi Tomasz,
On 08/04/2014 03:52 PM, Tomasz Bursztyka wrote:
Hi,
+++ b/src/dhcp.c
@@ -459,7 +459,8 @@ static void lease_available_cb(GDHCPClient
*dhcp_client, gpointer user_data)
__connman_ipconfig_set_gateway(dhcp->ipconfig, gateway);
}
-if (!apply_lease_available_on_netw
On 08/01/2014 05:23 PM, Tomasz Bursztyka wrote:
Hi,
+++ b/gsupplicant/supplicant.c
@@ -4804,6 +4804,8 @@ static const char *g_supplicant_rule5 =
"type=signal,"
"interface=" SUPPLICANT_INTERFACE ".Network";
static const char *g_supplicant_rule6 = "type=signal,"
"inter
Hi Tomasz,
I met a wifi direct issue when use latest connman.
I'm not sure whether I catch your point, if I'm wrong , please correct
me, thanks:-)
This patch seem that connman will use peer's */Group/* member to check
whether local side is GC.
and peer's group will updata when peer property
Hi everyone,
As we know, we can set up wifi tethering with ./enable-tethering wifi
SSID PASSWD.
And client device also can scan out the AP. at the same times, it also
support WPS method.
so what can I do if client device want to connect the AP using WPS
method(both PBC and PIN)?
Thanks
Guo
Hi
On 03/28/2014 03:59 PM, Tomasz Bursztyka wrote:
Hi,
Due to the fact wpa_supplicant might not (it's a bug) send the device
address, the peer identifier will be constructed on its name in this
case.
I have a suggestion that maybe we can get the device address from the
obj_path temporarily.
Y
Hi Tomasz,
On 03/27/2014 11:29 PM, Tomasz Bursztyka wrote:
Listen to DeviceFound and DeviceLost. From there it gets the Peer path
and properties, store it into the interface object and call relevant
peer_found/peer_lost callbacks provided by the wifi plugin.
Due to the fact wpa_supplicant might
On 03/03/2014 04:31 PM, Tomasz Bursztyka wrote:
Hi,
Please forgive me that I maybe not fully catch your points.
I just wander how does ConnMan deal with a incoming p2p connection
request.
I can't find the interface or a signal about notifying user a
incoming request received in your RFC V4.
On 02/28/2014 10:22 PM, Tomasz Bursztyka wrote:
If available, the p2p technology will be instanciated. Note that it's
fully dependant over wifi technology: wifi is the parent technology of
p2p.
If present, it will be possible to run a p2p peers discovery through p2p
technology's Scan() method. R
Hi,
Hi:
I'd like to speak more on group operation. :)
However, To me, I also believe that the Group concept in WiFi P2P Spec
is suck.
Temporary/Persistent group, group loading and all the related stuff is
really redundant to user.
The best and simple user experience is
1. just to connect to one
Hi Patrik
I think the most difficult is how to define what is the power means when
usb work as rndis mode.
And apply the patch, I test it in my device, found that it is only
create a USB gadget network interface when kernel
mode loaded even without a cable connected. so ConnMan create a
techn
12 matches
Mail list logo
