Re: cli or gui client
On Wed, 2012-12-12 at 10:43 -0800, Kok, Auke-jan H wrote: connman creates a folder for each network under /var/lib/connman. You should be able to pre-define a network in there and use connmanctl to connect to a service. This way you can set WPA/WEP passwords without any client. However, the format of these files isn't documented AFAIK. No. You should not touch/create any directories in /var/lib/connman. The only thing one is allowed to add/remove in /var/lib/connman are the wifi provisioning files ending with '.config' and documented in doc/config-format.txt. ConnMan will pick up the provisioned wifi network from the .config files and use those settings when a matching SSID is found. After that connmanctl can be used to connect/disconnect the service normally. Cheers, Patrik ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: [PATCH] technology: Enable wifi tethering open network type
Hi,
On Thu, 2012-12-13 at 11:25 +0800, Arron Wang wrote:
some device want to support wifi open tethering network type
our ConnMan already supported, just not export the API, I also
not sure whether we force the user to use encrypied wifi network
for security consideration
If the passphrase is defined, WPA encryption is enabled. If it's
missing, an open WiFi network is created.
---
src/technology.c | 18 +-
test/enable-tethering |7 +--
2 files changed, 18 insertions(+), 7 deletions(-)
diff --git a/src/technology.c b/src/technology.c
index bf82b8d..d4382b8 100644
--- a/src/technology.c
+++ b/src/technology.c
@@ -216,9 +216,6 @@ static int set_tethering(struct connman_technology
*technology,
{
const char *ident, *passphrase, *bridge;
- ident = technology-tethering_ident;
- passphrase = technology-tethering_passphrase;
-
if (technology-driver == NULL ||
technology-driver-set_tethering == NULL)
return -EOPNOTSUPP;
@@ -227,12 +224,23 @@ static int set_tethering(struct connman_technology
*technology,
if (technology-enabled == FALSE)
return -EACCES;
+ /* Clear passphrase filed when disable wifi tethering,
+ * else if we once enabled encrypied wifi network,
+ * we may failed to enable open wifi network type
+ */
+ if (enabled == FALSE) {
+ g_free(technology-tethering_passphrase);
+ technology-tethering_passphrase = NULL;
+ }
+
+ ident = technology-tethering_ident;
+ passphrase = technology-tethering_passphrase;
+
We don't want to clear the passphrase when disconnecting since that'd
mean explicitely selecting open/WPA secured WiFi from some UI every time
tethering is enabled.
Thus NACK for this patch.
Patrik
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
Re: Connman not showing a wifi adapter as a technology
On Tue, 2012-12-11 at 11:04 -0500, Gary Coulbourne wrote: That sounds like a bug. Should work without rfkill support also. Cheers, Patrik It would be good to verify that it happens generally, not just in my circumstance. It's possible there is some other underlying thing that changed in my configuration that I didn't account for. When starting up ConnMan for the first time (or removing its settings file in /var), all wireless technologies are by default off. The safest way to fix this is to do 'connmanctl enable wifi' or similar incantation in a preferred programming language at first time startup. I noticed that with rfkill enabled, there was a bug in handling the initial WiFi state. It now also correctly defaults to WiFi off and actually works as expected if WiFi is to be disabled when the device is restarted. It now works the same way with and without rfkill support. Cheers, Patrik ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: cli or gui client
On Thu, Dec 13, 2012 at 9:14 AM, Patrik Flykt patrik.fl...@linux.intel.com wrote: On Wed, 2012-12-12 at 10:43 -0800, Kok, Auke-jan H wrote: connman creates a folder for each network under /var/lib/connman. You should be able to pre-define a network in there and use connmanctl to connect to a service. This way you can set WPA/WEP passwords without any client. However, the format of these files isn't documented AFAIK. No. You should not touch/create any directories in /var/lib/connman. The only thing one is allowed to add/remove in /var/lib/connman are the wifi provisioning files ending with '.config' and documented in doc/config-format.txt. ConnMan will pick up the provisioned wifi network from the .config files and use those settings when a matching SSID is found. After that connmanctl can be used to connect/disconnect the service normally. Sounds useful, but how does that work with a hidden SSID? Would it try to match the configured profiles and see if the AP responds to that SSID. I don't know too much about the protocol but always wondered how that woks. If I configure a connection and set the SSID which is not advertized does connman or networmanager have to blindly try or is there a well defined method to see if the SSID matches an AP? Guys thanks for all the hints and I don't want to repeat myself or sound helpless but any idea how I can debug the dbus connection problem so that I can finally try out the suggested connection methods? btw, thanks for the quick responses. ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: [PATCH] technology: Enable wifi tethering open network type
Hi Arron, some device want to support wifi open tethering network type our ConnMan already supported, just not export the API, I also not sure whether we force the user to use encrypied wifi network for security consideration I am strictly against providing anything else than a WPA2 encrypted Hotspot. It is an extremely bad idea to let the user configure a Hotspot without password. So yes, we force the user to have a passphrase. That is 100% intentional and has been spelled out clearly 2 years ago when we added Tethering support to ConnMan. Same as we do required Bluetooth authentication and authorization before Tethering over Bluetooth can be used. The one thing we have not done yet is setting the friendly name automatically from something like hostnamed (from systemd). Regards Marcel ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: cli or gui client
Hi, On Thu, 2012-12-13 at 11:16 +0100, Carsten Mattner wrote: Sounds useful, but how does that work with a hidden SSID? In the .config file, add an entry saying 'Hidden = true'. This will make ConnMan do an active scan for the specified SSID. This and more is in doc/config-format.txt. Cheers, Patrik ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: cli or gui client
On Thu, Dec 13, 2012 at 12:14 AM, Patrik Flykt patrik.fl...@linux.intel.com wrote: On Wed, 2012-12-12 at 10:43 -0800, Kok, Auke-jan H wrote: connman creates a folder for each network under /var/lib/connman. You should be able to pre-define a network in there and use connmanctl to connect to a service. This way you can set WPA/WEP passwords without any client. However, the format of these files isn't documented AFAIK. No. You should not touch/create any directories in /var/lib/connman. The only thing one is allowed to add/remove in /var/lib/connman are the wifi provisioning files ending with '.config' and documented in doc/config-format.txt. ConnMan will pick up the provisioned wifi network from the .config files and use those settings when a matching SSID is found. After that connmanctl can be used to connect/disconnect the service normally. ahhh, thanks for the pointer - I never saw this file before. Auke ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Connman upstream test result_20121214
Hi all, This is test report for connman-1.9.191.gd735026-1.1.i586. In this testing,we ran 114 cases. 97 cases passed and 17 cases blocked because of new bugs. The pass rate is 87%. We found 3 new bugs, reopen 0 bug and verify 0 bug. In this commit we found the bug that Fail to connect to wifi AP with security by simple-agent,Errors output when connect to OpenVPN in the first time and Connmanctl can't remove connected wifi services. New bugs === 25893 - Fail to connect to wifi AP with security by simple-agent https://bugs.meego.com/show_bug.cgi?id=25893 25894 - Errors output when connect to OpenVPN in the first time https://bugs.meego.com/show_bug.cgi?id=25894 25895 - Connmanctl can't remove connected wifi services https://bugs.meego.com/show_bug.cgi?id=25895 Re-open bugs: === N/A Verified bugs: === N/A reproduced bugs: === 25862 - service-move-before does not change the connman state https://bugs.meego.com/show_bug.cgi?id=25862 25884 - Still see wifi service after disable wifi https://bugs.meego.com/show_bug.cgi?id=25884 === Testing Environment == Hardware: netbook Eeepc 1005PE / Cedar Trail / Ocktrail Green Ridge Image: meego-netbook-ia32-1.2.0 / netbook-ia32-pinetrail-tizen_20120424.2 ConnMan: connman-1.9.191.gd735026-1.1.i586 wpa_supplicant: wpa_supplicant-1.0-13.1.i586 Ofono: ofono-1.11.306.g660bbf6-1.1.i586 bluez: bluez-4.87-1.12.i586 3G: Unicom Sim card/ZTE MF190/HuaWei E261 BT: Palm Pre/AnyCom AP/CSR dongle (disable the onboard BT device) Wireless AP:netgear WNR2000/dlink Test Execution Summary == Category Total PASS FAILN/A Comments WiFi 18 117 bt66 3G 29 29 Ethernet 28 28 Regulatory1 1 NTP 1 1 Openvpn 7 7 surfing 3 3 proxy 11 11 tethering 10 10 Total 11497 17 Bug referred here is bug at bugs.meego.com, for example, bug #23110 refer to http://bugs.meego.com/show_bug.cgi?id=23110 ConnMan Test Report List Date:2012-12-14 ---Ethernet--- CM_Eth_BigBroadcastPing PASS CM_Eth_Conn PASS CM_Eth_HasDHCP PASS CM_Eth_IsReEnableWorks PASS CM_Eth_PoweredOn PASS CM_Eth_SmallBroadcastPingPASS CM_Eth_IsPoweredOn PASS CM_Eth_IsReady PASS CM_Eth_DisconnectPASS CM_Eth_PoweredOffPASS CM_Eth_Hotplug PASS CM_Eth_HasIP PASS CM_Eth_Connect PASS CM_Advance_StaticIP_WiredPASS CM_Advance_StaticIP PASS CM_Eth_UploadPASS CM_Eth_Download PASS CM_Flt_eth_autoconn PASS CM_Flt_ConnWired PASS CM_Flt_EthNoPing PASS CM_Flt_EthPoweredOff PASS CM_Flt_EthIsPoweredOff PASS CM_Flt_EthPoweredOn PASS CM_Flt_EthOnline PASS CM_IPv6_eth_set_address PASS CM_Info_EthConnInfo PASS CM_IPv6_eth_ssh PASS CM_AutoConn_RebootWired PASS Total:28 Pass:28 Fail:0 N/A:0 ---WiFi--- CM_WF_wps_pinBlock block by #25893 CM_WF_wps_pbcBlock block by #25893 CM_WS_WEP_Upload Block block by #25893 CM_WS_WEP_Download Block block by #25893 CM_WS_PSK2 Block block by #25893 CM_WS_RSNBlock block by #25893 CM_WS_WEP64 Block block by #25893 CM_WS_SharedHiddenWEP128 Block block by #25893 CM_WS_WPABlock block by #25893 CM_WS_OpenBroadcastWEP40 Block block by #25893 CM_WS_WEP128 Block block by #25893 CM_WS_Open PASS CM_WS_Hidden Block block by #25893 CM_Autoconn_HIDDEN_Rem_NoSecuBlock block by #25893 CM_AutoConn_RememWEP64 Block block by #25893 CM_Autoconn_HIDDEN_Rem_WPAPSKAES Block block by #25893 CM_Autoconn_RememWPAPSKTKIP Block block by #25893 CM_Autoconn_HIDDEN_Rem_WEP128Block block by #25893 Total:18 Pass:1 Fail:0 N/A:17 ---Bluetooth--- CM_BT_ConnectPASS CM_BT_SmallPing PASS CM_BT_BigPingPASS CM_BT_IsReEnableWorksPASS
