Re: 'Not supported' message
- Original Message - From: Tomasz Bursztyka Sent: 04/10/14 07:56 AM To: connman@connman.net Subject: Re: 'Not supported' message Hi Cliff, Okay, so let's get this right. Supplicant is started by D-bus when Connman contacts D-bus? So there is no need for start up files for supplicant or any of that? Is there anyway Connman could be at fault here by not contacting D-bus properly? No it works properly. There is surely an issue with your wpa_supplicant installation and/or dbus. Yes, you're right there was. I have recently converted to Systemd. As you're aware one can install four .service files with supplicant. /lib/systemd/system/wpa_supplicant.service has to be enabled if D-Bus interface was built into wpa_supplicant, so that wpa_supplicant D-Bus interface can be started at boot instead of being automatically activated by the D-Bus daemon which doesn't work when using systemd. I didn't know this. I now have a fully working Connman. I must thank you for your patience and help and apologise for any time wasting. regards Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: 'Not supported' message
- Original Message - From: Tomasz Bursztyka Sent: 04/09/14 07:39 AM To: connman@connman.net Subject: Re: 'Not supported' message Hi Cliff, But if I run 'wpa_supplicant -Dnl80211 -iwlan0 -c/etc/wpa_supplicant.conf' and then 'connmand -n -d' from the connman source, I get the familiar 'Error /net/connman/technology/wifi: Not supported' Again there is no soft blocking anymore - why I don't know. Never run wpa_supplicant that way for connman. Actually, if properly installed: wpa_supplicant will be properly started by dbus when connman will request its interface So, try starting connman, without starting yourself wpa_supplicant. Does this work? No, but if I start supplicant manually, then I can connect, otherwise I get the error. For some reason connman is not requesting supplicant. Still starting connman from source dir. If not, check this file: /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service do you have it, and is its content like: [D-BUS Service] Name=fi.w1.wpa_supplicant1 Exec=/usr/sbin/wpa_supplicant -u User=root SystemdService=wpa_supplicant.service This is okay, installed by supplicant when reinstalled. thanks Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: 'Not supported' message
- Original Message - From: Tomasz Bursztyka Sent: 04/09/14 08:54 AM To: connman@connman.net Subject: Re: 'Not supported' message Hi Cliff, No, but if I start supplicant manually, then I can connect, otherwise I get the error. For some reason connman is not requesting supplicant. Still starting connman from source dir. ConnMan does not request supplicant, it requests its dbus interface. And if wpa_supplicant is properly installed, dbus will start it automatically. Okay, so let's get this right. Supplicant is started by D-bus when Connman contacts D-bus? So there is no need for start up files for supplicant or any of that? Is there anyway Connman could be at fault here by not contacting D-bus properly? Sorry for this hand fisted approach but I'm no programmer, just need a working Connman for roaming. many thanks Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: 'Not supported' message
- Original Message - From: Tomasz Bursztyka Sent: 04/08/14 07:18 AM To: connman@connman.net Subject: Re: 'Not supported' message Hi, I'm sending four attachments to your email to avoid mailing to the list. But I think I have the reason why I had no wifi; Connman is soft blocking the card when it starts. If I unblock using rfkill, I can scan and connect! Log 1 is with card blocked, Log 2 after I unblock. So how is this? How is it solved? This is the normal behavior: first start, connman blocks all technologies but ethernet. Blocks = set powered off. Then if you power on the technology, connman will remind it. According to connmanctl your wifi technology was powered, can you verify that: if wifi card is soft rfkill, connman still shows that? Bug is there then. Right the situation is this. If I run: 'wpa_supplicant -u -ddt'(with or without log) the supplicant starts then 'connmand -n -d' from the connman source; connman starts and scans Then, from another terminal, 'connmanctl scan wifi': I can then connect. There is no soft blocking. But if I run 'wpa_supplicant -Dnl80211 -iwlan0 -c/etc/wpa_supplicant.conf' and then 'connmand -n -d' from the connman source, I get the familiar 'Error /net/connman/technology/wifi: Not supported' Again there is no soft blocking anymore - why I don't know. Where should I go now? thanks Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: 'Not supported' message
- Original Message - From: Tomasz Bursztyka Sent: 04/07/14 07:41 AM To: connman@connman.net Subject: Re: 'Not supported' message Hi Cliff, Do you have a wifi technology appearing in connmanctl ? (technologies command) Yes, 'connmanctl technologies' gives: /net/connman/technology/wifi Name = WiFi Type = wifi Powered = True Connected = False Tethering = False ConnMan should not show up wifi technology if it did not registered itself to wpa_supplicant. And according to your logs, that's what happened but you had issue to get the logs: What did you meant in your previous message by It wasn't until I stopped supplicant that I got a log.? Okay Tomasz, thanks for sticking with this problem. I meant that there was no output and nothing in the log from 'wpa_supplicant -u -ddt wpa_supplicant_log.txt' until I exited. It then read: 1396859395.292359: wpa_supplicant v2.1 1396859395.292386: random: Trying to read entropy from /dev/random 1396859395.293788: dbus: Register D-Bus object '/fi/w1/wpa_supplicant1' 1396859395.294380: Providing DBus service 'fi.w1.wpa_supplicant1'. 1396859395.294854: Providing DBus service 'fi.epitest.hostap.WPASupplicant'. 1396859395.294873: Successfully initialized wpa_supplicant 1396859395.294890: random: Got 20/20 bytes from /dev/random 1396859418.833686: dbus: Unregister D-Bus object '/fi/w1/wpa_supplicant1' You should run both wpa_supplicant and connman on their own terminal. When your test is over, just ctrlc+c on both. I have done this again the Connman log is attached(supplicant see above). thanks again Cliff connmand[3877]: Connection Manager version 1.22 connmand[3877]: src/dbus.c:__connman_dbus_init() connmand[3877]: src/inotify.c:__connman_inotify_init() connmand[3877]: src/technology.c:__connman_technology_init() connmand[3877]: src/storage.c:storage_load() Loading /var/lib/connman/settings connmand[3877]: src/storage.c:storage_load() Loading /var/lib/connman/settings connmand[3877]: src/notifier.c:__connman_notifier_init() connmand[3877]: src/agent.c:__connman_agent_init() connmand[3877]: src/service.c:__connman_service_init() connmand[3877]: src/agent.c:connman_agent_driver_register() Registering driver 0x8106680 name service connmand[3877]: src/peer.c:__connman_peer_init() connmand[3877]: src/provider.c:__connman_provider_init() connmand[3877]: src/notifier.c:connman_notifier_register() notifier 0x8106760 name provider connmand[3877]: src/network.c:__connman_network_init() connmand[3877]: src/config.c:__connman_config_init() connmand[3877]: src/inotify.c:create_watch() Add directory watch for /var/lib/connman connmand[3877]: src/config.c:read_configs() connmand[3877]: src/device.c:__connman_device_init() connmand[3877]: src/ippool.c:__connman_ippool_init() connmand[3877]: src/iptables.c:__connman_iptables_init() connmand[3877]: src/firewall.c:__connman_firewall_init() connmand[3877]: src/nat.c:__connman_nat_init() connmand[3877]: src/notifier.c:connman_notifier_register() notifier 0x8106b00 name nat connmand[3877]: src/tethering.c:__connman_tethering_init() connmand[3877]: src/counter.c:__connman_counter_init() connmand[3877]: src/manager.c:__connman_manager_init() connmand[3877]: src/notifier.c:connman_notifier_register() notifier 0x8106480 name manager connmand[3877]: src/stats.c:__connman_stats_init() connmand[3877]: src/clock.c:__connman_clock_init() connmand[3877]: src/timezone.c:__connman_timezone_init() connmand[3877]: src/timezone.c:__connman_timezone_lookup() sysconfig zone (null) connmand[3877]: src/timezone.c:__connman_timezone_lookup() localtime zone Europe/Guernsey connmand[3877]: src/storage.c:storage_load() Loading /var/lib/connman/settings connmand[3877]: src/resolver.c:__connman_resolver_init() dnsproxy 1 connmand[3877]: src/dnsproxy.c:__connman_dnsproxy_init() connmand[3877]: src/dnsproxy.c:__connman_dnsproxy_add_listener() index 1 connmand[3877]: src/dnsproxy.c:get_listener() family 2 protocol 17 index 1 connmand[3877]: src/inet.c:__connman_inet_get_interface_address() index 1 interface lo connmand[3877]: src/dnsproxy.c:get_listener() family 10 protocol 17 index 1 connmand[3877]: src/inet.c:__connman_inet_get_interface_address() index 1 interface lo connmand[3877]: src/dnsproxy.c:get_listener() family 2 protocol 6 index 1 connmand[3877]: src/inet.c:__connman_inet_get_interface_address() index 1 interface lo connmand[3877]: src/dnsproxy.c:get_listener() family 10 protocol 6 index 1 connmand[3877]: src/inet.c:__connman_inet_get_interface_address() index 1 interface lo connmand[3877]: src/resolver.c:__connman_resolvfile_append() index 1 server ::1 connmand[3877]: src/resolver.c:__connman_resolvfile_append() index 1 server 127.0.0.1 connmand[3877]: src/notifier.c:connman_notifier_register() notifier 0x8106ac0 name dnsproxy connmand[3877]: src/ipconfig.c:__connman_ipconfig_init() connmand[3877]: src/rtnl.c:__connman_rtnl_init() connmand[3877]:
Re: 'Not supported' message
- Original Message - From: Tomasz Bursztyka Sent: 04/07/14 11:21 AM To: connman@connman.net Subject: Re: 'Not supported' message Ok then it's really weird: ConnMan should not show up the wifi technology in this case. Let's revisit this from scratch: - give me your hardware specification of the wifi card See attachment - Intel Corporation Centrino Advanced-N 6200 (rev 35) - what kernel version? 3.12.1 - get the latest version of ConnMan from git (1.23), built it with bootstrap-configure (adapt it according to your needs). Done this will built connman in a maintainer mode, so you will be able to run the output binary in src/ directly - wpa_supplicant 2.0 or 2.1 (verify it is built/installed as we advise too in connman's README file) Done - as before, start wpa_supplicant as I said, before connman. And run Connman then, as I already advised but this time the one from src (so src/./connmand if you are in your local connman repo) - do you test, and give me the output I'm sending four attachments to your email to avoid mailing to the list. But I think I have the reason why I had no wifi; Connman is soft blocking the card when it starts. If I unblock using rfkill, I can scan and connect! Log 1 is with card blocked, Log 2 after I unblock. So how is this? How is it solved? thanks Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: 'Not supported' message
- Original Message - From: Tomasz Bursztyka Sent: 04/04/14 08:02 AM To: connman@connman.net Subject: Re: 'Not supported' message Hi Cliff, Got to see you logs and something is weird: there is no messages coming from plugins/wifi.c You did not filtered out the logs, did you? No, not at all, but what is strange is that I have no plugins dir and hence no wifi.c! Maybe you built all as builtin. But in your case I don't think it's the issue, it really looks like you lack off wifi plugin at all. Would be interesting to see gsupplicant's output as well. Could you retest and get the log this way: CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d connman_log.txt Would be nice to get wpa_supplicant's log as well (start it before connman): wpa_supplicant -u -ddt wpa_supplicant_log.txt Attached are the two logs. It wasn't until I stopped supplicant that I got a log. Can I ask why starting Connman manually would create a soft block om Wireless LAN? Do you have a wifi technology appearing in connmanctl ? (technologies command) Yes, 'connmanctl technologies' gives: /net/connman/technology/wifi Name = WiFi Type = wifi Powered = True Connected = False Tethering = False It looks like wifi plugin has not been built at all: wpa_supplicant is totally untouched. How did you build and installed ConnMan? (bootstrap-configure) ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var I understood that wifi is enabled by default, as is gadget, bluetooth etc. thanks Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: 'Not supported' message
- Original Message - From: Tomasz Bursztyka Sent: 04/03/14 07:27 AM To: connman@connman.net Subject: Re: 'Not supported' message Hi Cliff, Hi thanks for getting involved. Got to see you logs and something is weird: there is no messages coming from plugins/wifi.c You did not filtered out the logs, did you? No, not at all, but what is strange is that I have no plugins dir and hence no wifi.c! Would be interesting to see gsupplicant's output as well. Could you retest and get the log this way: CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d connman_log.txt Would be nice to get wpa_supplicant's log as well (start it before connman): wpa_supplicant -u -ddt wpa_supplicant_log.txt Attached are the two logs. It wasn't until I stopped supplicant that I got a log. Can I ask why starting Connman manually would create a soft block om Wireless LAN? thanks Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
'Not supported' message
Hi Sorry, but the two logs have gone to Tomasz Bursztyka. Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: 'Not supported' message
- Original Message - From: Jukka Rissanen Sent: 03/30/14 07:03 PM To: connman Subject: Re: 'Not supported' message Hi Cliff, On 30 March 2014 18:44, Cliff McDiarmid cliffhan...@gardener.com wrote: Hi I'm new to Connman, hoping to move from Wicd. I've configured, built and installed 1.22. Connman is starting with systemd okay When I input 'connmanctl scan wifi' I'm getting: 'Error /net/connman/technology/wifi: Not supported' Can someone tell me what this means? Wifi is enabled and built in, so I'm puzzled. You have not powered wifi technology. So try connmanctl enable wifi before starting the scan. The radio technologies are by default off when connman is started first time. If that does not help, then other alternative is that your wpa_supplicant has not enabled proper options. See connman README file what options are needed for supplicant. It's no go here. I've rebuilt wpa and the error message is the same, i.e. 'Error /net/connman/technology/wifi: Not supported' Wifi is enabled because 'connmanctl technologies' confirms this. thanks Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
Re: 'Not supported' message
On ti, 2014-04-01 at 07:25 -0400, Cliff McDiarmid wrote: - Original Message - From: Jukka Rissanen Sent: 03/30/14 07:03 PM To: connman Subject: Re: 'Not supported' message Hi Cliff, On 30 March 2014 18:44, Cliff McDiarmid cliffhan...@gardener.com wrote: Hi I'm new to Connman, hoping to move from Wicd. I've configured, built and installed 1.22. Connman is starting with systemd okay When I input 'connmanctl scan wifi' I'm getting: 'Error /net/connman/technology/wifi: Not supported' Can someone tell me what this means? Wifi is enabled and built in, so I'm puzzled. You have not powered wifi technology. So try connmanctl enable wifi before starting the scan. The radio technologies are by default off when connman is started first time. If that does not help, then other alternative is that your wpa_supplicant has not enabled proper options. See connman README file what options are needed for supplicant. It's no go here. I've rebuilt wpa and the error message is the same, i.e. 'Error /net/connman/technology/wifi: Not supported' Wifi is enabled because 'connmanctl technologies' confirms this. Hmm, that sounds quite weird. What version of wpa_supplicant you have? V2.1 And what about the kernel version 3.12.1 and what is the wifi device you want to use? Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35) Can you run connmand -n -d and paste the debug log somewhere so we can Sent it to your personel, hope that's okay If possible wpa_supplicant debug log would also be nice to have, just start it manually with wpa_supplicant -u -d before starting connman. wpa_supplicant v2.1 random: Trying to read entropy from /dev/random dbus: Register D-Bus object '/fi/w1/wpa_supplicant1' Providing DBus service 'fi.w1.wpa_supplicant1'. Providing DBus service 'fi.epitest.hostap.WPASupplicant'. Successfully initialized wpa_supplicant random: Got 20/20 bytes from /dev/random - STOP thanks Jukka Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
'Not supported' message
Hi I'm new to Connman, hoping to move from Wicd. I've configured, built and installed 1.22. Connman is starting with systemd okay When I input 'connmanctl scan wifi' I'm getting: 'Error /net/connman/technology/wifi: Not supported' Can someone tell me what this means? Wifi is enabled and built in, so I'm puzzled. thanks Cliff ___ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
