Hi Somisetty,
On 08/05/2011 10:52 AM, Somisetty Sreegowri wrote:
> Sorry for the late reply.
No worries.
> We tested wifi on connman-0.76, but wifi
> did not come up. We also tried different versions of the connman
> still not able to get the wifi up.
That sounds strange.
> We somehow suspect the wpa_supplicant installation in Fedora 14.
I think F14 ships a too old wpa_supplicant. IIRC, I have used my own
compiled wpa_supplicant on F14.
> Details are as follows :
[...]
> I tried different scenarios of installation of wpa_supplicant:
>
> a) Installed the latest wpa_supplicant-0.7.2.tar.gz without
> uninstalling the earlier wpa_supplicant. So, it was showing two
> different version of wpa_supplicant in the same system, at
> "/etc/wpa_supplicant" for wpa_supplicant-0.6.8 and
> "/usr/local/sbin/wpa_supplicant" for wpa_supplicant-0.7.2. Replaced that
> with the latest supplicant version. But that didnt work.
What are your configuration options for wpa_supplicant. The
configuration I used for my own version of wpa_supplicant was:
CONFIG_DRIVER_HOSTAP=y
CONFIG_DRIVER_ATMEL=y
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_NL80211=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_PKCS12=y
CONFIG_SMARTCARD=y
CONFIG_CTRL_IFACE=y
CONFIG_READLINE=y
CONFIG_BACKEND=file
CONFIG_PEERKEY=y
CONFIG_CTRL_IFACE_DBUS=y
CONFIG_CTRL_IFACE_DBUS_NEW=y
CONFIG_CTRL_IFACE_DBUS_INTRO=y
CONFIG_DEBUG_FILE=y
> b) Uninstalled wpa_supplicant-0.6.8 rpm package that is installed in Fedora
> 14 using :
> "rpm -e --nodeps wpa_supplicant-0.6.8.fc14.i686" and then installed the
> latest wpa_supplicant-0.7.2.tar.gz. But that installation didnt created files
> in respective folders :"/etc/dbus-1/system.d/" and
> "/usr/share/dbus-1/system-services/"
> So, i copied files of those folders from Meego1.1 (CrownBay Board with
> wpa_supplicant-0.7.2 ) into the respective folders in Fedora-14 system.
> In /etc/dbus-1/system.d/ ----> "wpa_supplicant.conf"
> and In /usr/share/dbus-1/system-services/ --->
> "fi.epitest.hostap.WPASupplicant.service" "fi.w1.wpa_supplicant1.service"
>
> Restarted system, stoped network and Network manager and started connmand.
> But, still wifi didn't come up in ifconfig.
> and even connmand not starting the wpa_supplicant in Background. And its
> showing its status as :
>
> [root@01HW102775 manager]# service wpa_supplicant status
> wpa_supplicant: unrecognized service
>
> Manually starting wpa_supplicant with :
> [root@01HW102775 manager]# wpa_supplicant -Dwext -iwlan0
> -c/etc/wpa_supplicant.conf
> Bring up the wifi interface, but didnt show the service path in
> ./test-connman services.
>
> Kindly let me know how to bring the wifi interface in higher version. Is am i
> doing something wrong in wpa_supllicant installation? Please suggest...!!
Can you post please the log output from connman and wpa_supplicant?
connmand -n -d 2&> log.txt
wpa_supplicant OPTIONS -dd
thanks,
daniel
Dear Daniel,
Following errors are seen when running any of the test scripts of connman
versions 0.67,0.68 and 0.69 in Fedora 14
The output is :
[root@01HW102775 test]# ./list-services
ERROR:dbus.proxies:Introspect error on :1.65:/: dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.
Traceback (most recent call last):
File "./list-services", line 31, in <module>
properties = manager.GetProperties()
File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not
receive a reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
Kindly let me know what additional steps are required to be done in order to
avoid this error.
Thanks and Regards,
Somisetty Sree Gowri
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
