Re: Regarding connman service_connect
On Wed, 2015-02-04 at 21:01 -0600, Janakiram Sistla wrote: My question here is I see a call to agent API agent_context_unref(). But i am not sure who is issuing this. Can some one please let me know how this agent API is getting called. Agent API is getting called only if there is vital information needed when connecting that ConnMan doesn't know of. See doc/agent-api.txt for what information is requested. In order to provide such information, at least one Agent needs to be running with the simplest one possible being connmanctl instructed with 'agent on'. HTH, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: Regarding connman service_connect
On Thu, 2015-02-05 at 09:10 -0600, Janakiram Sistla wrote: But per one customer requirement i did already provided connman with the required information that connman will require from user via connmanctl. So i dont want this to be started again. If you have a product, you really have to come up with something else than connmanctl supplying passphrases. I don't have the slightest clue what you mean with having already provided ConnMan with the required information, but here are two things you can try out: - There's no problem if the UI requests all information up front. Just issue a Connect() and reply to RequestInput with the passphrase etc. information when ConnMan asks for it. - If the environment is such that every network is known beforehand, the solution is provisioning, see doc/config-format.txt. That makes the pre-provisioned service immutable, and one has to know about all the networks beforehand. Is there a way where i can stop agent since the information is already provided. I don't understand this question. How was the information provided to ConnMan, since there is no D-Bus method of doing that? Cheers, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: Regarding connman service_connect
On Wed, 2015-02-04 at 21:01 -0600, Janakiram Sistla wrote: * My question here is I see a call to agent API agent_context_unref(). ** But i am not sure who is issuing this. Can some one please let me know ** how this agent API is getting called. * Agent API is getting called only if there is vital information needed when connecting that ConnMan doesn't know of. Patrik, Yes i understand that. But per one customer requirement i did already provided connman with the required information that connman will require from user via connmanctl. So i dont want this to be started again. Is there a way where i can stop agent since the information is already provided. Regards, Sistla. See doc/agent-api.txt for what information is requested. In order to provide such information, at least one Agent needs to be running with the simplest one possible being connmanctl instructed with 'agent on'. HTH, Patrik ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Regarding connman service_connect
Hi All, I am trying to understand the call flow sequence when we try to do a connection using connman connect service. I see the below logs. connmand[2769]: src/network.c:connman_network_get_bool() network 0x2cbde138 key WiFi.UseWPS connmand[2769]: src/network.c:connman_network_get_string() network 0x2cbde138 key WiFi.PinWPS connmand[2769]: src/network.c:connman_network_ref_debug() 0x2cbde138 name sistlajr ref 4 by plugins/wifi.c:1493:network_connect() connmand[2769]: src/network.c:connman_network_set_associating() network 0x2cbde138 associating 1 connmand[2769]: src/service.c:__connman_service_ipconfig_indicate_state() service 0x2cbe08f0 (wifi_00025b03f749_736973746c616a72_managed_psk) state 2 (association) type 1 (IPv4) connmand[2769]: src/service.c:service_indicate_state() service 0x2[ 192.082736] systemd[1]: bluetooth.service operation timed out. Terminating. cbe08f0 old idle - new association/idle = association connmand[2769]: src/session.c:service_state_changed() service 0x2cbe08f0 state 2 connmand[2769]: src/notifier.c:notify_idle_state() idle 0 connmand[2769]: src/manager.c:idle_state() idle 0 connmand[2769]: src/connection.c:update_order() connmand[2769]: src/connection.c:__connman_connection_update_gateway() default (nil) connmand[2769]: src/service.c:__connman_service_ipconfig_indicate_state() service 0x2cbe08f0 (wifi_00025b03f749_73692_managed_psk) state 2 (association) type 2 (IPv6) connmand[2769]: src/service.c:service_indicate_state() service 0x2cbe08f0 old association - new association/association = association connmand[2769]: src/service.c:connman_service_unref_debug() 0x2cbe08f0 ref 1 by src/service.c:7679:agent_context_unref() connmand[2769]: plugins/wifi.c:connect_callback() network 0x2cbde138 result 0 connmand[2769]: src/network.c:connman_network_unref_debug() 0x2cbde138 name sidfsdfsr ref 3 by plugins/wifi.c:1393:connect_callback() connmand[2769]: src/service.c:service_send_changed() connmand[2769]: src/service.c:service_append_added_foreach() changed /net/connman/service/wifi_00025b03f749_736973746c616a72_managed_psk My question here is I see a call to agent API agent_context_unref(). But i am not sure who is issuing this. Can some one please let me know how this agent API is getting called. Regards, Sistla. ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
