Re: Connman-1.20 services scan does not return hidden networks.
Hi, I have applied this commit and it works. Thanks ~Sameer On Wed, Dec 18, 2013 at 2:49 PM, Patrik Flykt patrik.fl...@linux.intel.comwrote: Hi, On Thu, 2013-12-12 at 17:44 +0530, Sameer Naik wrote: Hello, I updated to connman-1.20 and found that hidden wifi networks are not returned when scanning for services. Upon inspection I found that commit #363393cfb1a5f95f8892f40662486c87b80d0091 is where the breakage occurs. For reference, please find the commit message below: commit 363393cfb1a5f95f8892f40662486c87b80d0091 Author: Daniel Wagner daniel.wag...@bmw-carit.de Date: Mon Dec 2 13:50:25 2013 +0100 gsupplicant: Fix empty string test The address of an array is never NULL, so the comparison will always evaluate the same way. Instead test for the length of the SSID. Reported by coverity. This is fixed with commit 91913c40054d9c55c6d38f0c626a78bdbcf4279a, please check and report back that latest upstream fixes your problem. Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Connman-1.20 services scan does not return hidden networks.
Hello, I updated to connman-1.20 and found that hidden wifi networks are not returned when scanning for services. Upon inspection I found that commit #363393cfb1a5f95f8892f40662486c87b80d0091 is where the breakage occurs. For reference, please find the commit message below: commit 363393cfb1a5f95f8892f40662486c87b80d0091 Author: Daniel Wagner daniel.wag...@bmw-carit.de Date: Mon Dec 2 13:50:25 2013 +0100 gsupplicant: Fix empty string test The address of an array is never NULL, so the comparison will always evaluate the same way. Instead test for the length of the SSID. Reported by coverity. Regards ~Sameer ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Requirements for getting Hotspot (Tethering) enabled.
Hello, I am using connman-1.12 on my STB that runs linux kernel version 2.6.22. In my kernel configuration i have enabled the following: CONFIG_BRIDGE=m CONFIG_BRIDGE_NETFILTER=y CONFIG_NF_CONNTRACK_ENABLED=m CONFIG_NF_CONNTRACK=m CONFIG_NF_NAT=m CONFIG_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m I have iptables-1.4.12.2, wpa_supplicant-1.1 installed. My wpa_supplicant config contains the following configuration (among other things): CONFIG_DRIVER_HOSTAP=y CONFIG_DRIVER_WEXT=y CONFIG_WPS=y CONFIG_AP=y CONFIG_BGSCAN_SIMPLE=y The following modules are automatically loaded at boot: bridge 70144 0 - Live 0xc014f000 llc 8864 1 bridge, Live 0xc011 nf_conntrack_ipv4 11488 0 - Live 0xc001d000 nf_conntrack 68816 1 nf_conntrack_ipv4, Live 0xc0123000 iptable_filter 3008 0 - Live 0xc001b000 ip_tables 14544 1 iptable_filter, Live 0xc0057000 x_tables 18448 1 ip_tables, Live 0xc0051000 I am using a rtl8192c wifi dongle for the wifi and works with the Wext interface. When i try to enable tethering in connman i get an error message saying wlan0 does not support AP mode. Are there any additional requirements for getting hotspot feature working? Do i need to install hostapd or something? I would like to debug and get the hotspot feature enabled. But at the moment, I am not sure how to. Please find the connman and wpa_supplicant logs attached. For the purpose of testing, i installed connman-1.12 on my ubuntu 12.10 laptop and tried creating a hotspot using the enable-tethering script. The script indicates that it has enabled tethering on the wifi dongle. But when i scan for wifi networks (on my mobile) i do not see the hotspot created. Please advise. Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: [PATCH v2] wifi: Preliminary fix for autoscanning known hidden SSIDs
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 max_ssids to know how many SSIDs it can provide as
paremeters. However, patch 6af0579c434058536fb40480f40f5e9895cfe863, which
fixes an issue about fast scanning, affects such feature.
Therefore, as a default, it will fallback to 1 if given max_ssids is 0.
There is still the issue that it will autoscan only max_ssid (1 or more)
known hidden SSIDs. This need to be fixed.
Reported by Sameer Naik
---
Dumb test to change, sorry.
plugins/wifi.c | 31 +++
1 file changed, 15 insertions(+), 16 deletions(-)
diff --git a/plugins/wifi.c b/plugins/wifi.c
index 4b097fc..d5a20b3 100644
--- a/plugins/wifi.c
+++ b/plugins/wifi.c
@@ -530,7 +530,8 @@ static void scan_callback_hidden(int result,
{
struct connman_device *device = user_data;
struct wifi_data *wifi = connman_device_get_data(device);
- int driver_max_ssids;
+ GSupplicantScanParams *scan_params;
+ int driver_max_ssids, ret;
DBG(result %d wifi %p, result, wifi);
@@ -539,32 +540,30 @@ static void scan_callback_hidden(int result,
/*
* Scan hidden networks so that we can autoconnect to them.
+* We will assume 1 as a default number of ssid to scan.
*/
driver_max_ssids = g_supplicant_interface_get_max_scan_ssids(
wifi-interface);
- DBG(max ssids %d, driver_max_ssids);
+ if (driver_max_ssids == 0)
+ driver_max_ssids = 1;
- if (driver_max_ssids 0) {
- GSupplicantScanParams *scan_params;
- int ret;
+ DBG(max ssids %d, driver_max_ssids);
- scan_params = g_try_malloc0(sizeof(GSupplicantScanParams));
- if (scan_params == NULL)
- goto out;
+ scan_params = g_try_malloc0(sizeof(GSupplicantScanParams));
+ if (scan_params == NULL)
+ goto out;
- if (get_hidden_connections(driver_max_ssids,
- scan_params) 0) {
- ret = g_supplicant_interface_scan(wifi-interface,
+ if (get_hidden_connections(driver_max_ssids, scan_params) 0) {
+ ret = g_supplicant_interface_scan(wifi-interface,
scan_params,
scan_callback,
device);
- if (ret == 0)
- return;
- }
-
- g_supplicant_free_scan_params(scan_params);
+ if (ret == 0)
+ return;
}
+ g_supplicant_free_scan_params(scan_params);
+
out:
scan_callback(result, interface, user_data);
}
--
1.8.1.4
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
Re: Autoconnect to a hidden wifi service.
I am looking into the connman plugin/wifi.c to figure out the issue. so far i have found that in scan_callback_hidden function, g_supplicant_interface_get_max_scan_ssids(wifi-interface), returns 0 and therefore no attempt to connect to provisioned hidden wifi networks is performed. Will trace the calls further to figure out why g_supplicant_interface_get_max_scan_ssids returns 0. Regards ~Sameer On Fri, Mar 1, 2013 at 2:23 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello, I have been checking the autoconnect to hidden network feature. For far no luck. For your reference, following is my wpa_supplicant-1.1 config CONFIG_DRIVER_HOSTAP=y CONFIG_DRIVER_ATMEL=y CONFIG_DRIVER_WEXT=y CONFIG_DRIVER_WIRED=y CONFIG_IEEE8021X_EAPOL=y CONFIG_EAP_MD5=y CONFIG_EAP_MSCHAPV2=y CONFIG_EAP_TLS=y CONFIG_EAP_PEAP=y CONFIG_EAP_TTLS=y CONFIG_EAP_GTC=y CONFIG_EAP_OTP=y CONFIG_EAP_LEAP=y CONFIG_WPS=y CONFIG_WPS2=y CONFIG_AP=y CONFIG_PKCS12=y CONFIG_CTRL_IFACE=y CONFIG_BACKEND=file CONFIG_PEERKEY=y CONFIG_CTRL_IFACE_DBUS_NEW=y CONFIG_CTRL_IFACE_DBUS_INTRO=y CONFIG_DEBUG_FILE=n CONFIG_BGSCAN_SIMPLE=y CONFIG_BGSCAN_LEARN=y CONFIG_OS=unix CONFIG_L2_PACKET=linux My wpa_supplicant.conf file contains the following: ap_scan=1 ctrl_interface=/var/run/wpa_supplicant I generated the connmand and wpa_supplicant debug logs over a period of 10 minutes (attached). Please let me know if you find anything. Thanks and Regards ~Sameer On Fri, Mar 1, 2013 at 2:08 AM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello Tomasz, Please find attached. Regards ~Sameer On Fri, Mar 1, 2013 at 12:15 AM, Tomasz Bursztyka tomasz.burszt...@linux.intel.com wrote: Hi Sameer, I am wondering whether connman is supposed to be able to autoconnect to this hidden wifi service or is this the expected behaviour. It should autoconnect also with hidden service. Works perfectly with my config but there is maybe an issue with yours. Could you provide the logs of connman (run it like: CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d connman_log.txt) Tomasz __**_ connman mailing list connman@connman.net http://lists.connman.net/**listinfo/connmanhttp://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Autoconnect to a hidden wifi service.
Hello, I am using connman-1.12 on a STB platform. I have implemented a connman client and agent to handle connecting to wired and wireless services via connman. I am currently testing connections to hidden wireless services. Right now i am able to connect to hidden wifi services after responding to the RequestInput method of the agent. What i have noticed is that once i connect to a hidden network the configuration file is created. But when i restart the device or restart connman for that matter, the system will not automatically connect to the (already configured) hidden service. Even when the service configuration is saved. I am wondering whether connman is supposed to be able to autoconnect to this hidden wifi service or is this the expected behaviour. Thanks and Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Understanding connman's ONLINE state change.
Hello, I was trying to understand the state change of services from READY to ONLINE state. From what i can gather a service state will change from READY to ONLINE once connman is able to fetch Hidden=truehttp://ipv4.connman.net/online/status.html(for ipv4). In my system i have a wired service and a wireless service configured, and in the main.conf i have the config line Preferred = ethernet In the test setup i have configured that wired and wireless networks such that the wired network has not internet connection available so it will not be able to reach http://ipv4.connman.net/online/status.html. While the wireless network as full internet access. Now when i start connman, it connects to the wired network and stays in the ready state forever. It does not try to connect to the wireless network to see if it can go online and set it up as the default service. On the other hand if i unplug the lan cable from the device, connman connects to the wireless service and goes in the online state. After that if i plug in the lan cable, connman connects to the wired service, see's that it cannot go online and so keeps the wireless service as the default service and hence connman stays in the online state. I guess this is the expected behaviour. I would like to know if it is possible to instruct connman to connect all available technologies, so that at startup it connects to the wired as well as the wireless services and then decides which one to setup as the default route. Lastly, i would also like to know if connman performs periodic checks to see if the service can go in the online state. i.e. when the state of the manager is in the ready, does connman periodically check if it can go online? Looking forward to your reply. Thanks and Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Understanding connman's ONLINE state change.
Got it. Will try to hack the source. Will let you guys know if i get anywhere. Thanks and Regards ~Sameer On Fri, Mar 1, 2013 at 12:26 AM, Tomasz Bursztyka tomasz.burszt...@linux.intel.com wrote: Hi Sameer, I guess this is the expected behaviour. You guess right. I would like to know if it is possible to instruct connman to connect all available technologies, so that at startup it connects to the wired as well as the wireless services and then decides which one to setup as the default route. As far as I know it cannot. Should not be too complex to patch I think. Lastly, i would also like to know if connman performs periodic checks to see if the service can go in the online state. i.e. when the state of the manager is in the ready, does connman periodically check if it can go online? The idea has been around for a while but no patches yet. Looks trivial on the surface, but actually it implies things around user's moving services before/after another one, (moving the online one after a ready one) etc... Patches are welcome of course ;) Tomasz __**_ connman mailing list connman@connman.net http://lists.connman.net/**listinfo/connmanhttp://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Unable to get the gateway of a service that is not the default route.
I forgot to mention one thing, i have PreferredTechnologies = ethernet in my main.conf. On Mon, Feb 25, 2013 at 5:32 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello, I am using connman-1.11 on an STB platform that has an inbuilt LAN port. For WIFI i am using a wifi dongle. So far i have got every thing working fine. I am able to connect to wired and wireless networks. I am currently testing the stuff out and understanding some connman behaviour patterns along the way. I found that when i connect both the wired and wifi technologies (i.e. connect to a service for each), only one of them goes in the online state. Both will be never enter the online state under normal circumstances. eg. 1. Start connman with lan cable connected Connman connects to the lan network and enter the online state 2. Connect to a wireless service Connman connects to the wireless service, and the service remains in the offline state until the ethernet cable is disconnected. This is probably a behaviour by design and i can understand why it is this way. One of the reason being that only one interface can serve as the default route at a time, etc. But what i noticed is that, if i get the ipv4 configuration for each of the technologies, only the service that is on currently serving as the default route return the gateway. To make my point clearer, please refer to the output of GetServices method at http://pastebin.com/DVkXJiNB. You will notice that of the 2 connected services, only the wired service returns the gateway address. Is this by design? Is possible to get the gateway for services that are in READY state?? Thanks and Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
UI implemetation for connecting to a hidden network
Hello, I am using connman-1.11 on a STB platform. I have some general questions regarding the UI implementation for connecting to hidden wifi networks. Currently in connman, i can list all the wifi services and filter out the hidden services and let the user select the service that he/she may want to connect to. When the user selects the service, the connect method is called on the service and connman then asks the user to input the Name/SSID and the passphrase, etc. Now, this is fine if there is only one hidden network listed. Say for example there are 2 hidden networks, user would have a difficult time figuring out the networks they are suppposed to connect to. Of course you can take a best guess based on the security being used, the signal strength, etc. Once you start having a lot more hidden wifi networks listed it becomes a lot more difficult to figure out the network the user needs to select. So my question is... Is it possible to specify the network we want to connect to by specifying the Name/SSID of the network and connman figures out the rest. Something along the lines of http://screencloud.net/v/Qcu Thanks and Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Unable to get the gateway of a service that is not the default route.
Hello Patrik, But shouldn't the gateway returned for each service be the route setup for the interface on which the service is running (at least display purposes) ie. 192.168.1.1 * 255.255.255.255 UH0 00 eth0 192.168.6.1 * 255.255.255.255 UH0 00 wlan0 By looking up the service that is currently in the online state, i would be able to tell which is the default route (provided that only one service is in the online at any given time, which right now is not always the case). Of course, i should be able to get the gateway information using socket api's or something for my display purposes. But i believe connman would do a better job at it ;) Regards ~Sameer On Mon, Feb 25, 2013 at 6:03 PM, Patrik Flykt patrik.fl...@linux.intel.comwrote: Hi, On Mon, 2013-02-25 at 17:32 +0530, Sameer Naik wrote: I found that when i connect both the wired and wifi technologies (i.e. connect to a service for each), only one of them goes in the online state. Both will be never enter the online state under normal circumstances. eg. 1. Start connman with lan cable connected Connman connects to the lan network and enter the online state 2. Connect to a wireless service Connman connects to the wireless service, and the service remains in the offline state until the ethernet cable is disconnected. This is probably a behaviour by design and i can understand why it is this way. One of the reason being that only one interface can serve as the default route at a time, etc. Your observation is correct, only one default route is set at a time. As a default route is defined as matching every packet and sending the packets to the gateway, only one gateway is set at any time. So only the service which has the default route will contain gateway information. Thus the network information provided by all services is identical to what can be read from the routing table. Cheers, Patrik ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: UI implemetation for connecting to a hidden network
Thanks Tomasz, That was really helpful. The pieces of the puzzle seem to be coming together for me. On Mon, Feb 25, 2013 at 6:13 PM, Tomasz Bursztyka tomasz.burszt...@linux.intel.com wrote: Hi Sameer, Now, this is fine if there is only one hidden network listed. Say for example there are 2 hidden networks, user would have a difficult time figuring out the networks they are suppposed to connect to. Of course you can take a best guess based on the security being used, the signal strength, etc. Once you start having a lot more hidden wifi networks listed it becomes a lot more difficult to figure out the network the user needs to select. There cannot be more hidden services than handled security i.e.: psk, wep, open. Services are grouped by security. You could have 100 hidden service, if all are wpa/wpa2 -- you will see only 1 hidden service on security psk. I had no idea about this. I imagined that each hidden service would be listed. Your response makes a lot of send to me now. It works exactly the same for non-hidden services. Now for you issue, of course you can specify the name of the hidden network you are trying to connect to. For such thing you need to implement the agent API. Take a look at doc/agent-api.txt I have implemented the agent api and have been testing the same. Thanks again. Your reply was really helpful. Regards ~Sameer Br, Tomasz __**_ connman mailing list connman@connman.net http://lists.connman.net/**listinfo/connmanhttp://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Unable to get the gateway of a service that is not the default route.
On Mon, Feb 25, 2013 at 7:17 PM, Patrik Flykt patrik.fl...@linux.intel.comwrote: On Mon, 2013-02-25 at 18:24 +0530, Sameer Naik wrote: 192.168.1.1 * 255.255.255.255 UH0 00 eth0 192.168.6.1 * 255.255.255.255 UH0 00 wlan0 These are individual host routes to the DNS servers. In normal circumstances the DNS server is co-located to the DHCP server box, at least with normal home networking. By looking up the service that is currently in the online state, i would be able to tell which is the default route (provided that only one service is in the online at any given time, The first service in the service list is the one with the default route and also the only one which can be online. Otherwise... which right now is not always the case). ...you have found a bug, I believe. I may be wrong about this... i will need to recheck. Cheers, Patrik ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Unable to connect to open wireless networks
Hello Patrik, I am using a wireless USB dongle that has a realtek 8291cu chipset. The driver in use was realtek's 8192cu driver and the version is v3.4.4_4749.20120730. The driver is downloadable from the following location: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1PFid=48Level=5Conn=4ProdID=277DownTypeID=3GetDown=falseDownloads=true I am using linux-2.6.22, the newer kernels have this driver within the kernel (i think). The wpa_supplicant i am using is version 1.1, but the issue existed with wpa_supplicant version 1.0 and 0.7.3 as well. The connman version in use is 1.11 release version. Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Unable to connect to open wireless networks
Here is the driver download link if required: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1PFid=48Level=5Conn=4ProdID=277DownTypeID=3GetDown=falseDownloads=true On Tue, Feb 12, 2013 at 6:08 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello Patrik, I am using a wireless USB dongle that has a realtek 8291cu chipset. The driver in use was realtek's 8192cu driver and the version is v3.4.4_4749.20120730. The driver is downloadable from the following location: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1PFid=48Level=5Conn=4ProdID=277DownTypeID=3GetDown=falseDownloads=true I am using linux-2.6.22, the newer kernels have this driver within the kernel (i think). The wpa_supplicant i am using is version 1.1, but the issue existed with wpa_supplicant version 1.0 and 0.7.3 as well. The connman version in use is 1.11 release version. Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Unable to connect to open wireless networks
Hi Patrik and Tomasz, I just downgraded my wireless device driver to the older version and suddenly i am able to connect to open wireless networks. With the newer driver I was not able to connect to open wireless networks using connman, but was able to do so using the wpa_cli tool. I will be switching to the older driver for now. However do let me know if need me to perform any tests. Thanks and Regards ~Sameer On Mon, Feb 11, 2013 at 7:03 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello Tomasz, Please find attached connman.log and wpa_supplicant.log file generated in the same run. Regards ~Sameer On Mon, Feb 11, 2013 at 6:00 PM, Tomasz Bursztyka tomasz.burszt...@linux.intel.com wrote: Hi Sameer, Could you send wpa_supplicant's log as well? run it with -dd option so you get a lot of debug. From what I saw in your connman's log, the state transition went from associtating/connecting to disconnected. So we will get more clues from wpa_supplicant logs about the reasons why you've got such transition. Thanks, Tomasz __**_ connman mailing list connman@connman.net http://lists.connman.net/**listinfo/connmanhttp://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Unable to connect to open wireless networks
Hello Patrik, Even after removing -W wext switch from the connmand command line the issue persists. Right now i am using wpa_supplicant-1.1. Regards ~Sameer On Mon, Feb 11, 2013 at 1:02 PM, Patrik Flykt patrik.fl...@linux.intel.comwrote: On Sun, 2013-02-10 at 22:41 +0530, Sameer Naik wrote: $ connmand -W wext -I eth0 -n -d Does it help if you omit the -W switch? With a fairly recent wpa_supplicant, this switch isn't necessary. Cheers, Patrik ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: DNS caching probably not working in dnsproxy.
Please ignore this. On Fri, Feb 1, 2013 at 6:38 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hi, I am testing connman-1.10 and i get the following warnings when i try to resolve a dns address. START OF LOG connmand[2815]: src/dnsproxy.c:udp_listener_event() Received 32 bytes (id 0x090c) connmand[2815]: src/dnsproxy.c:parse_request() id 0x090c qr 0 opcode 0 qdcount 1 arcount 0 connmand[2815]: src/dnsproxy.c:parse_request() query www.google.com. connmand[2815]: src/dnsproxy.c:resolv() server 192.168.1.1 enabled 1 GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed connmand[2815]: src/dnsproxy.c:forward_dns_reply() Received 196 bytes (id 0x1629) connmand[2815]: src/dnsproxy.c:forward_dns_reply() req 0x4daba8 dstid 0x1629 altid 0xe285 rcode 0 connmand[2815]: src/dnsproxy.c:cache_update() offset 0 hdr 0x7fa9fb68 msg 0x7fa9fb68 rcode 0 connmand[2815]: src/dnsproxy.c:parse_response() qr 1 qdcount 1 GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed connmand[2815]: src/dnsproxy.c:cache_update() cache 5 new question wwwgooglecom type 28 ttl 293 size 125 packet 62 dns len 62 connmand[2815]: src/dnsproxy.c:forward_dns_reply() proto 17 sent 196 bytes to 9 connmand[2815]: src/dnsproxy.c:udp_listener_event() Received 32 bytes (id 0x9f96) connmand[2815]: src/dnsproxy.c:parse_request() id 0x9f96 qr 0 opcode 0 qdcount 1 arcount 0 connmand[2815]: src/dnsproxy.c:parse_request() query www.google.com. connmand[2815]: src/dnsproxy.c:resolv() server 192.168.1.1 enabled 1 GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed connmand[2815]: src/dnsproxy.c:forward_dns_reply() Received 248 bytes (id 0x6ebe) connmand[2815]: src/dnsproxy.c:forward_dns_reply() req 0x4daba8 dstid 0x6ebe altid 0x5fc0 rcode 0 connmand[2815]: src/dnsproxy.c:cache_update() offset 0 hdr 0x7fa9fb68 msg 0x7fa9fb68 rcode 0 connmand[2815]: src/dnsproxy.c:parse_response() qr 1 qdcount 1 GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed connmand[2815]: src/dnsproxy.c:cache_update() cache 6 new question wwwgooglecom type 1 ttl 293 size 177 packet 114 dns len 114 connmand[2815]: src/dnsproxy.c:forward_dns_reply() proto 17 sent 248 bytes to 9 END OF LOG It looks like there is some problem in DNS caching. Maybe the cache GHashTable is not initialized. Earlier i had glib assertion checks disabled due to which connman ended by crashing. Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
DNS caching probably not working in dnsproxy.
Hi, I am testing connman-1.10 and i get the following warnings when i try to resolve a dns address. START OF LOG connmand[2815]: src/dnsproxy.c:udp_listener_event() Received 32 bytes (id 0x090c) connmand[2815]: src/dnsproxy.c:parse_request() id 0x090c qr 0 opcode 0 qdcount 1 arcount 0 connmand[2815]: src/dnsproxy.c:parse_request() query www.google.com. connmand[2815]: src/dnsproxy.c:resolv() server 192.168.1.1 enabled 1 GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed connmand[2815]: src/dnsproxy.c:forward_dns_reply() Received 196 bytes (id 0x1629) connmand[2815]: src/dnsproxy.c:forward_dns_reply() req 0x4daba8 dstid 0x1629 altid 0xe285 rcode 0 connmand[2815]: src/dnsproxy.c:cache_update() offset 0 hdr 0x7fa9fb68 msg 0x7fa9fb68 rcode 0 connmand[2815]: src/dnsproxy.c:parse_response() qr 1 qdcount 1 GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed connmand[2815]: src/dnsproxy.c:cache_update() cache 5 new question wwwgooglecom type 28 ttl 293 size 125 packet 62 dns len 62 connmand[2815]: src/dnsproxy.c:forward_dns_reply() proto 17 sent 196 bytes to 9 connmand[2815]: src/dnsproxy.c:udp_listener_event() Received 32 bytes (id 0x9f96) connmand[2815]: src/dnsproxy.c:parse_request() id 0x9f96 qr 0 opcode 0 qdcount 1 arcount 0 connmand[2815]: src/dnsproxy.c:parse_request() query www.google.com. connmand[2815]: src/dnsproxy.c:resolv() server 192.168.1.1 enabled 1 GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed connmand[2815]: src/dnsproxy.c:forward_dns_reply() Received 248 bytes (id 0x6ebe) connmand[2815]: src/dnsproxy.c:forward_dns_reply() req 0x4daba8 dstid 0x6ebe altid 0x5fc0 rcode 0 connmand[2815]: src/dnsproxy.c:cache_update() offset 0 hdr 0x7fa9fb68 msg 0x7fa9fb68 rcode 0 connmand[2815]: src/dnsproxy.c:parse_response() qr 1 qdcount 1 GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed connmand[2815]: src/dnsproxy.c:cache_update() cache 6 new question wwwgooglecom type 1 ttl 293 size 177 packet 114 dns len 114 connmand[2815]: src/dnsproxy.c:forward_dns_reply() proto 17 sent 248 bytes to 9 END OF LOG It looks like there is some problem in DNS caching. Maybe the cache GHashTable is not initialized. Earlier i had glib assertion checks disabled due to which connman ended by crashing. Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Connman does not automatically switch to Wired LAN
Thanks Jeff and Patrik. I was missing the main.conf file. After adding it as per your suggestions its working. As suggested by Patrik i have set PreferredTechnologies = ethernet SingleConnectedTechnology = false in main.conf First impression is that it works. But i am facing a really weird issue that the /dev/null device gets deleted when the lan cable is plugged out. When the lan cable is plugged in a regular file named /dev/null is created which also vanishes after a while, then it reappears again after some time as a regular file and finally vanishes again, never to return. Then again if i unplug the lan cable and plug it back in the same vanishing act takes place, i.e. it appears as a regular file - dissapears - reappears - dissapears. I am not sure what to make of this. If i stop connman, and use ifconfig to configure the lan interface the same thing happens. So it should have something to do with connman. A bug in the kernel maybe??? I you guys have any ideas please share.. Thanks and Regards ~Sameer On Thu, Jan 31, 2013 at 1:12 PM, Patrik Flykt patrik.fl...@linux.intel.comwrote: On Thu, 2013-01-31 at 01:40 +, Zheng, Jeff wrote: SingleConnectedTechnology = true That one is not recommended and should not be used in normal devices. It only lets the _last_ connected connection to be used and thus prevents the detection and usage of another technolgy that could go online. Definitely do not use this, you get a much worse connectivity experience from ConnMan. It's enough to define PreferredTechnologies = ethernet in main.conf if there is no difference between the other network technologies. Cheers, Patrik ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Connman 1.9 won't attempt connecting to wifi service
Hello, Today i noticed one issue. I am not sure whether this is a bug or this is by design. I have a saved wifi profile with Autoconnect turned on and was able to connect to that profile without any problems. Yesterday i updated wpa_supplicant to version 1.0 and found that connman was no longer able to connect to by saved profile. So i reverted back to wpa_supplicant-0.7.3 and noticed that connman was still not able to connect to my saved wifi profile. I noticed that connman had appended a line 'Failure=invalid-key' in the settings file of the saved wifi profile due to which the connection was not happening even after restarting connman multiple times. I had to remove that line for it to start working again. I would have expected that connman would attempt connecting to the service at least once and figure out whether the key was invalid or not and then stop connection attempts to the service if the key was found to be invalid. At the moment I don't have an agent registered, so i don't know if there is something more that occurs in this case. The condition that occured in my case was purely a side effect of being in developer mode. I am not sure if this could occur in production mode. One last thing, Is connman compatible with wpa_supplicant-1.0? Lemme know. Thanks and Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: State of net.connman.Clock Timeservers
Hi, Things i have noticed in the clock API. 1. If a timeserver is specified, using Timeservers property, that is already in the global timeservers list. The time sync is not restarted. 2. If the TimeUpdates property is set to manual and then back to auto, the NTP sync is not started/restarted. Regards ~Sameer On Mon, Mar 5, 2012 at 10:18 AM, Marcel Holtmann mar...@holtmann.org wrote: Hi Jeff, please refrain from top-posting here. No exceptions. Oops, sorry. I tried timeserver with latest connman and it seems to work for me. I can get time updated from timeserver. Could you please try connman test script set-global-timeservers? Though there is a small difference than old ntp plugin: It will append the new timerservers instead of override old ones. what does this mean? The global ones are just the default servers that will be used if DHCP does not provide NTP servers or if they are not working. Here is the command list: [root@localhost ~]# test-clock Timeservers = [ ntp.meego.com ] [root@localhost ~]# set-global-timeservers ntp.connman.net Setting timeserver to ['ntp.connman.net'] [root@localhost ~]# test-clock Timeservers = [ ntp.meego.com ntp.connman.net ] With old ntp plugin, Timeservers was just 'ntp.connman.net' and the old behavior was correct. This is a bug. Regards Marcel ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
ntp synchronization in READY state.
Hello,
According to my understanding NTP synchronization will occur in
connman once service state is CONNMAN_SERVICE_STATE_ONLINE. Further
service will enter the online state once connman can communicate with
http://ipv4.connman.net/online/status.html.
However in my case, generally an NTP server announced via dhcp and is
present on the local network. My device may not necessarily be
connected to the internet. So i need to start the ntp synchronization
before connman enters the ONLINE state.
For this i made the following change:
src/service.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/service.c b/src/service.c
index a21ee3f..e093340 100644
--- a/src/service.c
+++ b/src/service.c
@@ -4052,9 +4052,6 @@ static int service_indicate_state(struct
connman_service *service)
}
}
- if (new_state == CONNMAN_SERVICE_STATE_ONLINE)
- __connman_timeserver_sync(service);
-
if (new_state == CONNMAN_SERVICE_STATE_IDLE) {
connman_bool_t reconnect;
@@ -4157,6 +4154,9 @@ static int service_indicate_state(struct
connman_service *service)
if (new_state == CONNMAN_SERVICE_STATE_ONLINE)
default_changed();
+ if (new_state == CONNMAN_SERVICE_STATE_READY)
+ __connman_timeserver_sync(service);
+
return 0;
}
That is to say, start __connman_timeserver_sync once we are in the
READY state and dont wait for connman to go to ONLINE state.
But after this change, while trying to scan a wifi technology i
receiving the error GDBus.Error:net.connman.Error.NoCarrier: No
carrier very frequently and i am required to stop connman and start
it again after which it is fine. I am finding it difficult to
understand why this is happening. I had made a similar edit for
connman-0.78 and it was working fine. Please find the attached
connman.log
Looking forward to your response.
Regards
~Sameer
$ connmand -n -d -W wext
connmand[743]: Connection Manager version 0.78
connmand[743]: src/dbus.c:__connman_dbus_init()
connmand[743]: src/storage.c:storage_load() Loading /opt/resource/etc/connman/settings
connmand[743]: src/technology.c:__connman_technology_init()
connmand[743]: src/storage.c:storage_load() Loading /opt/resource/etc/connman/settings
connmand[743]: src/notifier.c:__connman_notifier_init()
connmand[743]: src/service.c:__connman_service_init()
connmand[743]: src/provider.c:__connman_provider_init()
connmand[743]: src/notifier.c:connman_notifier_register() notifier 0x4987e0 name provider
connmand[743]: src/network.c:__connman_network_init()
connmand[743]: src/device.c:__connman_device_init()
connmand[743]: src/agent.c:__connman_agent_init()
connmand[743]: src/ippool.c:__connman_ippool_init()
connmand[743]: src/iptables.c:__connman_iptables_init()
connmand[743]: src/nat.c:__connman_nat_init()
connmand[743]: src/notifier.c:connman_notifier_register() notifier 0x498b50 name nat
connmand[743]: src/iptables.c:__connman_iptables_command() command -t nat -F POSTROUTING argc 5
connmand[743]: src/iptables.c:iptables_init() nat
connmand[743]: src/iptables.c:iptables_command() Flush chain POSTROUTING
connmand[743]: src/iptables.c:__connman_iptables_commit() nat
connmand[743]: src/tethering.c:__connman_tethering_init()
connmand[743]: src/counter.c:__connman_counter_init()
connmand[743]: src/manager.c:__connman_manager_init()
connmand[743]: src/notifier.c:connman_notifier_register() notifier 0x498480 name manager
connmand[743]: src/config.c:__connman_config_init()
connmand[743]: src/config.c:read_configs()
connmand[743]: src/stats.c:__connman_stats_init()
connmand[743]: src/clock.c:__connman_clock_init()
connmand[743]: src/timezone.c:__connman_timezone_init()
connmand[743]: src/timezone.c:__connman_timezone_lookup() sysconfig zone (null)
connmand[743]: src/timezone.c:__connman_timezone_lookup() localtime zone (null)
connmand[743]: src/resolver.c:__connman_resolver_init() dnsproxy 1
connmand[743]: src/dnsproxy.c:__connman_dnsproxy_init()
connmand[743]: src/dnsproxy.c:__connman_dnsproxy_add_listener() interface lo
connmand[743]: src/dnsproxy.c:create_dns_listener() interface lo
connmand[743]: No IPv6 support; DNS proxy listening only on Legacy IP
connmand[743]: Failed to bind UDP listener interface
connmand[743]: src/dnsproxy.c:create_dns_listener() interface lo
connmand[743]: No IPv6 support; DNS proxy listening only on Legacy IP
connmand[743]: Failed to bind TCP listener interface
connmand[743]: src/resolver.c:__connman_resolvfile_append() interface lo server 127.0.0.1
connmand[743]: src/notifier.c:connman_notifier_register() notifier 0x498b20 name dnsproxy
connmand[743]: src/ipconfig.c:__connman_ipconfig_init()
connmand[743]: src/rtnl.c:__connman_rtnl_init()
connmand[743]: src/task.c:__connman_task_init()
connmand[743]: src/proxy.c:__connman_proxy_init()
connmand[743]: src/detect.c:__connman_detect_init()
connmand[743]: src/rtnl.c:connman_rtnl_register() rtnl 0x498810
Re: Powered stated on on board ethernet technology is false.
Please review.
On Fri, Feb 24, 2012 at 3:56 PM, Sameer Naik
sameer.subscripti...@damagehead.com wrote:
Apparently the technology is being enabled before it is even in the
technology_list. Since the technology cannot be found in the
technology list, its enabled flag remains unset.
On Fri, Feb 24, 2012 at 1:35 AM, Sameer Naik
sameer.subscripti...@damagehead.com wrote:
Hi,
Have been trying to figure out what the issue is. No leads yet.
One thing though is that the Powered state response to the dbus call
depends on whether the technology is enabled.
if (technology-enabled 0)
powered = TRUE;
else
powered = FALSE;
The logs show that the device is powered (as you pointed out). The
code flow shows that the technology is disabled.
Regards
~Sameer
On Thu, Feb 23, 2012 at 10:38 PM, Sameer Naik
sameer.subscripti...@damagehead.com wrote:
Hello,
Yes, this happens every single time. One thing worth noting is that i
have my rootfs mounted over NFS. So the ethernet interface is already
connected before connman starts up. Maybe this is causing the issue.
I launch connman via boot scripts with the following command
$ connmand -W wext
Technologies enabled are: ethernet, wifi
Plugins enabled are: ether google loopback wifi
My settings file contains the following.
[global]
OfflineMode=false
Timeservers=0.pool.ntp.org;1.pool.ntp.org;2.pool.ntp.org;3.pool.ntp.org
[WiFi]
Enable=true
[Bluetooth]
Enable=false
[Wired]
Enable=true
[3G]
Enable=false
[WiMAX]
Enable=false
Regards
~Sameer
On Thu, Feb 23, 2012 at 5:09 PM, alok barsode alokbars...@gmail.com wrote:
Hi,
On Thu, Feb 23, 2012 at 11:11 AM, Sameer Naik
sameer.subscripti...@damagehead.com wrote:
Hello Alok,
Please find attached connman.log file.
Do let me know if you need me to generate logs for specific modules.
Thanks for the log. I can see connman_device_set_powered() powered 1 called
on the ethernet device. so i dont know why it shows powered=false.
I am not able to repordude this problem. Do u see this every time ? How
can i reproduce this? any specific setup? what does ur
/var/lib/connman/settings
say?
Cheers,
Alok.
Regards
~Sameer
On Thu, Feb 23, 2012 at 1:18 PM, alok barsode alokbars...@gmail.com
wrote:
Hi Sameer,
On Thu, Feb 23, 2012 at 7:47 AM, Sameer Naik
sameer.subscripti...@damagehead.com wrote:
Hi,
I have a system with on board ethernet and using connman git head.
When i query the technology it says Powered state is false and at
the same time Connected state is true.
$ dbus-send --system --print-reply --dest=net.connman /net/c
onnman/technology/ethernet net.connman.Technology.GetProperties
method return sender=:1.0 - dest=:1.27 reply_serial=2
array [
dict entry(
string Name
variant string Wired
)
dict entry(
string Type
variant string ethernet
)
dict entry(
string Powered
variant boolean false
)
dict entry(
string Connected
variant boolean true
)
dict entry(
string Tethering
variant boolean false
)
]
We definitely need more info that this, connman logs, setup details.
Its very tough to say what the problem is just from a dbus-send output.
Regards
~Sameer
Cheers,
Alok.
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
From 321d7ba148c807c1f3271137a7cb19cf2168bbf9 Mon Sep 17 00:00:00 2001
From: Sameer Naik sam...@damagehead.com
Date: Fri, 24 Feb 2012 16:06:35 +0530
Subject: [PATCH] technology: while enabling a technology, create it if it
does not exist in the technologies_list.
Technology was not being set to enabled if it could not be found in the
technologies_list. Hence a technology would be marked disabled when it
is created.
To fix this, we replace the technology_find call with the technology_get
call, so that it is created when not found.
---
src/technology.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/technology.c b/src/technology.c
index 12ed5af..5fa07d9 100644
--- a/src/technology.c
+++ b/src/technology.c
@@ -1101,7 +1101,7 @@ int __connman_technology_enabled(enum connman_service_type type)
{
struct connman_technology *technology;
- technology = technology_find(type);
+ technology = technology_get(type);
if (technology == NULL
Re: Powered stated on on board ethernet technology is false.
Hello, I can confirm that the patch patch fixes the issue. Thanks ~Sameer On Fri, Feb 24, 2012 at 4:50 PM, alok barsode alokbars...@gmail.com wrote: Hi, NACK for the patch. __connman_technology_enabled() should not create a technology if there isnt one. the device should land up in techless_device_list and must be later picked up by the technology when the tech _driver registers it. Here is my guess: from the logs i can see that connman_technology_add_device() calls __connman_device_enable() but since the device is already enabled, the calls does not propagate through to connman_device_set_powered. Can u apply the following patch and check if this solves the issue? I will will then post it on the ML for review. Thanks! Alok. On Fri, Feb 24, 2012 at 12:46 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Please review. On Fri, Feb 24, 2012 at 3:56 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Apparently the technology is being enabled before it is even in the technology_list. Since the technology cannot be found in the technology list, its enabled flag remains unset. On Fri, Feb 24, 2012 at 1:35 AM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hi, Have been trying to figure out what the issue is. No leads yet. One thing though is that the Powered state response to the dbus call depends on whether the technology is enabled. if (technology-enabled 0) powered = TRUE; else powered = FALSE; The logs show that the device is powered (as you pointed out). The code flow shows that the technology is disabled. Regards ~Sameer On Thu, Feb 23, 2012 at 10:38 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello, Yes, this happens every single time. One thing worth noting is that i have my rootfs mounted over NFS. So the ethernet interface is already connected before connman starts up. Maybe this is causing the issue. I launch connman via boot scripts with the following command $ connmand -W wext Technologies enabled are: ethernet, wifi Plugins enabled are: ether google loopback wifi My settings file contains the following. [global] OfflineMode=false Timeservers=0.pool.ntp.org;1.pool.ntp.org;2.pool.ntp.org; 3.pool.ntp.org [WiFi] Enable=true [Bluetooth] Enable=false [Wired] Enable=true [3G] Enable=false [WiMAX] Enable=false Regards ~Sameer On Thu, Feb 23, 2012 at 5:09 PM, alok barsode alokbars...@gmail.com wrote: Hi, On Thu, Feb 23, 2012 at 11:11 AM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello Alok, Please find attached connman.log file. Do let me know if you need me to generate logs for specific modules. Thanks for the log. I can see connman_device_set_powered() powered 1 called on the ethernet device. so i dont know why it shows powered=false. I am not able to repordude this problem. Do u see this every time ? How can i reproduce this? any specific setup? what does ur /var/lib/connman/settings say? Cheers, Alok. Regards ~Sameer On Thu, Feb 23, 2012 at 1:18 PM, alok barsode alokbars...@gmail.com wrote: Hi Sameer, On Thu, Feb 23, 2012 at 7:47 AM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hi, I have a system with on board ethernet and using connman git head. When i query the technology it says Powered state is false and at the same time Connected state is true. $ dbus-send --system --print-reply --dest=net.connman /net/c onnman/technology/ethernet net.connman.Technology.GetProperties method return sender=:1.0 - dest=:1.27 reply_serial=2 array [ dict entry( string Name variant string Wired ) dict entry( string Type variant string ethernet ) dict entry( string Powered variant boolean false ) dict entry( string Connected variant boolean true ) dict entry( string Tethering variant boolean false ) ] We definitely need more info that this, connman logs, setup details. Its very tough to say what the problem is just from a dbus-send output. Regards ~Sameer Cheers, Alok. ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http
Re: Powered stated on on board ethernet technology is false.
Hello, Yes, this happens every single time. One thing worth noting is that i have my rootfs mounted over NFS. So the ethernet interface is already connected before connman starts up. Maybe this is causing the issue. I launch connman via boot scripts with the following command $ connmand -W wext Technologies enabled are: ethernet, wifi Plugins enabled are: ether google loopback wifi My settings file contains the following. [global] OfflineMode=false Timeservers=0.pool.ntp.org;1.pool.ntp.org;2.pool.ntp.org;3.pool.ntp.org [WiFi] Enable=true [Bluetooth] Enable=false [Wired] Enable=true [3G] Enable=false [WiMAX] Enable=false Regards ~Sameer On Thu, Feb 23, 2012 at 5:09 PM, alok barsode alokbars...@gmail.com wrote: Hi, On Thu, Feb 23, 2012 at 11:11 AM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello Alok, Please find attached connman.log file. Do let me know if you need me to generate logs for specific modules. Thanks for the log. I can see connman_device_set_powered() powered 1 called on the ethernet device. so i dont know why it shows powered=false. I am not able to repordude this problem. Do u see this every time ? How can i reproduce this? any specific setup? what does ur /var/lib/connman/settings say? Cheers, Alok. Regards ~Sameer On Thu, Feb 23, 2012 at 1:18 PM, alok barsode alokbars...@gmail.com wrote: Hi Sameer, On Thu, Feb 23, 2012 at 7:47 AM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hi, I have a system with on board ethernet and using connman git head. When i query the technology it says Powered state is false and at the same time Connected state is true. $ dbus-send --system --print-reply --dest=net.connman /net/c onnman/technology/ethernet net.connman.Technology.GetProperties method return sender=:1.0 - dest=:1.27 reply_serial=2 array [ dict entry( string Name variant string Wired ) dict entry( string Type variant string ethernet ) dict entry( string Powered variant boolean false ) dict entry( string Connected variant boolean true ) dict entry( string Tethering variant boolean false ) ] We definitely need more info that this, connman logs, setup details. Its very tough to say what the problem is just from a dbus-send output. Regards ~Sameer Cheers, Alok. ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Powered stated on on board ethernet technology is false.
Hi, Have been trying to figure out what the issue is. No leads yet. One thing though is that the Powered state response to the dbus call depends on whether the technology is enabled. if (technology-enabled 0) powered = TRUE; else powered = FALSE; The logs show that the device is powered (as you pointed out). The code flow shows that the technology is disabled. Regards ~Sameer On Thu, Feb 23, 2012 at 10:38 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello, Yes, this happens every single time. One thing worth noting is that i have my rootfs mounted over NFS. So the ethernet interface is already connected before connman starts up. Maybe this is causing the issue. I launch connman via boot scripts with the following command $ connmand -W wext Technologies enabled are: ethernet, wifi Plugins enabled are: ether google loopback wifi My settings file contains the following. [global] OfflineMode=false Timeservers=0.pool.ntp.org;1.pool.ntp.org;2.pool.ntp.org;3.pool.ntp.org [WiFi] Enable=true [Bluetooth] Enable=false [Wired] Enable=true [3G] Enable=false [WiMAX] Enable=false Regards ~Sameer On Thu, Feb 23, 2012 at 5:09 PM, alok barsode alokbars...@gmail.com wrote: Hi, On Thu, Feb 23, 2012 at 11:11 AM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello Alok, Please find attached connman.log file. Do let me know if you need me to generate logs for specific modules. Thanks for the log. I can see connman_device_set_powered() powered 1 called on the ethernet device. so i dont know why it shows powered=false. I am not able to repordude this problem. Do u see this every time ? How can i reproduce this? any specific setup? what does ur /var/lib/connman/settings say? Cheers, Alok. Regards ~Sameer On Thu, Feb 23, 2012 at 1:18 PM, alok barsode alokbars...@gmail.com wrote: Hi Sameer, On Thu, Feb 23, 2012 at 7:47 AM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hi, I have a system with on board ethernet and using connman git head. When i query the technology it says Powered state is false and at the same time Connected state is true. $ dbus-send --system --print-reply --dest=net.connman /net/c onnman/technology/ethernet net.connman.Technology.GetProperties method return sender=:1.0 - dest=:1.27 reply_serial=2 array [ dict entry( string Name variant string Wired ) dict entry( string Type variant string ethernet ) dict entry( string Powered variant boolean false ) dict entry( string Connected variant boolean true ) dict entry( string Tethering variant boolean false ) ] We definitely need more info that this, connman logs, setup details. Its very tough to say what the problem is just from a dbus-send output. Regards ~Sameer Cheers, Alok. ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Wifi Technology says its offline when wifi dongle is unplugged and plugged back in
Nevermind. I have updated to git version. Apparently the API of the git version is much refined (and does not suffer from the issues present in the stable version). On Wed, Feb 22, 2012 at 10:20 AM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello, I am using the current stable version 0.78. Regards ~Sameer On Wed, Feb 22, 2012 at 1:15 AM, alok barsode alokbars...@gmail.com wrote: Hi Sameer, On Tue, Feb 21, 2012 at 8:14 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello, I seems that the technology state is not updated correctly. When i start connman and by ethernet connection is up and system is online, The ethernet technology says enabled. I think it should be saying connected. For wifi, when the dongle is removed the State goes to offline. But on plugging it back in, it never goes to the enabled or connected states. This is until connman is relaunched. Is this a bug? or am i not understanding it right! what version of connman are u using ? we have moved to Powered and Connected properties for technology. I think you seem to be using a older version by what you are reporting. here is what i get when I do a GetPropreties on wifi dbus-send --system --print-reply --dest=net.connman /net/connman/technology/wifi net.connman.Technology.GetProperties method return sender=:1.101 - dest=:1.153 reply_serial=2 array [ dict entry( string Name variant string WiFi ) dict entry( string Type variant string wifi ) dict entry( string Powered variant boolean true ) dict entry( string Connected variant boolean true ) dict entry( string Tethering variant boolean false ) ] Regards ~Sameer Cheers, Alok. On Sun, Feb 19, 2012 at 1:10 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hi, if i connect a usb wifi dongle and start connman and query the wifi technology as so: -- $ dbus-send --system --print-reply --dest=net.connman /net /connman/technology/wifi net.connman.Technology.GetProperties. $ dbus-send --system --print-reply --dest=net.connman /net /connman/technology/wifi net.connman.Technology.GetProperties method return sender=:1.172 - dest=:1.174 reply_serial=2 array [ dict entry( string State variant string enabled ) dict entry( string Name variant string WiFi ) dict entry( string Type variant string wifi ) dict entry( string Tethering variant boolean false ) ] - It lists that the state of the wifi technology is enabled. When i remove the wifi dongle the Technology it says its offline But when i plug the dongle back in, it remains offline and does not go to enabled. However, if i get the manager properties using: $ dbus-send --system --print-reply --dest=net.connman / net.connman.Manager.GetProperties, wifi is listed under enabled technologies. so in short, Manager says technology is enabled, while Technology says its offline. Is this the expected behaviour? Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
Re: Wifi Technology says its offline when wifi dongle is unplugged and plugged back in
Hello, I am using the current stable version 0.78. Regards ~Sameer On Wed, Feb 22, 2012 at 1:15 AM, alok barsode alokbars...@gmail.com wrote: Hi Sameer, On Tue, Feb 21, 2012 at 8:14 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hello, I seems that the technology state is not updated correctly. When i start connman and by ethernet connection is up and system is online, The ethernet technology says enabled. I think it should be saying connected. For wifi, when the dongle is removed the State goes to offline. But on plugging it back in, it never goes to the enabled or connected states. This is until connman is relaunched. Is this a bug? or am i not understanding it right! what version of connman are u using ? we have moved to Powered and Connected properties for technology. I think you seem to be using a older version by what you are reporting. here is what i get when I do a GetPropreties on wifi dbus-send --system --print-reply --dest=net.connman /net/connman/technology/wifi net.connman.Technology.GetProperties method return sender=:1.101 - dest=:1.153 reply_serial=2 array [ dict entry( string Name variant string WiFi ) dict entry( string Type variant string wifi ) dict entry( string Powered variant boolean true ) dict entry( string Connected variant boolean true ) dict entry( string Tethering variant boolean false ) ] Regards ~Sameer Cheers, Alok. On Sun, Feb 19, 2012 at 1:10 PM, Sameer Naik sameer.subscripti...@damagehead.com wrote: Hi, if i connect a usb wifi dongle and start connman and query the wifi technology as so: -- $ dbus-send --system --print-reply --dest=net.connman /net /connman/technology/wifi net.connman.Technology.GetProperties. $ dbus-send --system --print-reply --dest=net.connman /net /connman/technology/wifi net.connman.Technology.GetProperties method return sender=:1.172 - dest=:1.174 reply_serial=2 array [ dict entry( string State variant string enabled ) dict entry( string Name variant string WiFi ) dict entry( string Type variant string wifi ) dict entry( string Tethering variant boolean false ) ] - It lists that the state of the wifi technology is enabled. When i remove the wifi dongle the Technology it says its offline But when i plug the dongle back in, it remains offline and does not go to enabled. However, if i get the manager properties using: $ dbus-send --system --print-reply --dest=net.connman / net.connman.Manager.GetProperties, wifi is listed under enabled technologies. so in short, Manager says technology is enabled, while Technology says its offline. Is this the expected behaviour? Regards ~Sameer ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
[PATCH] gweb: fix typo in parse_url function while processing http_proxy proxy setting.
Lookup for the proxy scheme and host should be performed on the recently
duplicated proxy string. As a result of this issue proxies specified by
the scheme http_proxy=http://192.168.1.1:3128, would not work.
From 71b2d26867227d9e4d5c67fea081ee30b3d1ac39 Mon Sep 17 00:00:00 2001
From: Sameer Naik sam...@damagehead.com
Date: Mon, 13 Feb 2012 17:32:01 +0530
Subject: [PATCH 1/2] gweb: fix typo in parse_url function while processing
http_proxy proxy setting.
Lookup for the proxy scheme and host should be performed on the recently
duplicated proxy string. As a result of this issue proxies specified by
the scheme http_proxy=http://192.168.1.1:3128, would not work.
---
gweb/gweb.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/gweb/gweb.c b/gweb/gweb.c
index 365f67c..6d9e7ad 100644
--- a/gweb/gweb.c
+++ b/gweb/gweb.c
@@ -1098,7 +1098,7 @@ static int parse_url(struct web_session *session,
if (scheme == NULL)
return -EINVAL;
- host = strstr(proxy, ://);
+ host = strstr(scheme, ://);
if (host != NULL) {
*host = '\0';
host += 3;
--
1.7.6.5
___
connman mailing list
connman@connman.net
http://lists.connman.net/listinfo/connman
[PATCH] gweb: set session-host to the parsed proxy hostname.
If the proxy is specified then we should set the session-host to the parsed proxy hostname. The proxy hostname was instead being set in the session-address variable. Since session-address is not being resolved, specifying the http_proxy variable in the scheme http_proxy=proxy.example.com:3128 would not work. From a6446d8d9c3dd00864204a2352e66415743e6329 Mon Sep 17 00:00:00 2001 From: Sameer Naik sam...@damagehead.com Date: Mon, 13 Feb 2012 17:40:31 +0530 Subject: [PATCH 2/2] gweb: set session-host to the parsed proxy hostname. If the proxy is specified then we should set the session-host to the parsed proxy hostname. The proxy hostname was instead being set in the session-address variable. Since session-address is not being resolved, specifying the http_proxy variable in the scheme http_proxy=proxy.example.com:3128 would not work. --- gweb/gweb.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/gweb/gweb.c b/gweb/gweb.c index 6d9e7ad..da2ab0a 100644 --- a/gweb/gweb.c +++ b/gweb/gweb.c @@ -1125,7 +1125,9 @@ static int parse_url(struct web_session *session, } } - session-address = g_strdup(host); + if (session-host) + g_free(session-host); + session-host = g_strdup(host); g_free(scheme); -- 1.7.6.5 ___ connman mailing list connman@connman.net http://lists.connman.net/listinfo/connman
