Hi Weber
to what permission i need to change?. current my system is showing
# cd dhcpcd
# ls -l
drwxr-xr-x root root 2010-08-19 07:56 dhcpcd-hooks
-rwxrwxrwx root shell1009 2010-08-19 07:00 dhcpcd-run-
hooks
-rw-r--r-- root root 189 2010-08-19 07:20
Hi Ashwin,
I am trying to enable wifi in froyo. when i try to enable wifi is
getting enabled but I am unable to connect to AP.
for IP configuration I am getting 0.0.0.0 entries for many
fields(below)
V/WifiStateTracker( 1010): IP configuration: ipaddr 0.0.0.0 gateway
0.0.0.0 netmask 0.0.0.0 dns1
Thanks，Ashwin
At last I found that it was caused by the permission of /system/etc/
dhcpcd/dhcpcd-run-hooks
I changed it ,and now it can get the ip addr and connect,I can use
iwconfig to see the info or eth1
# iwconfig
lono wireless extensions.
eth0 no wireless extensions.
usb0
Hi,website access through wifi is really caused by eth0
After disabling the eth0
#ifconfig eth0 down
I can surffing the Internet now
Thank you all !
--Weber
On Jul 23, 9:07 pm, Weber qvbs...@gmail.com wrote:
Thanks，Ashwin
At last I found that it was caused by the permission of /system/etc/
Hi Ashwin
I tried the wpa_supplicant code of donut ,and then problem went
away.
Now my board can scan the ap and return the results, but it still can
not connect to ap.
Maybe it is because of the dhcp
and in init.rc,My dhcp service is started by the follow line:
service dhcpcd
Weber,
I have the following in my init.rc file associated with brining up the
WiFi interface:
#-
service wpa_supplicant /system/bin/logwrapper
/system/bin/wpa_supplicant -Dwext -iwlan0
-c/system/etc/wifi/wpa_supplicant.conf -dd
disabled
group system
service dhcpcd
Nicu Pavel wrote:
The differences is that driver_wext.c expects the wifi kernel driver
to implement the SIOCSIWPRIV ioctl and respond to android commands
like RSSI, MACADDR etc, while driver_awext.c replies to android
commands by using standard wireless extensions ioctls and works for
most
Hi,
Nicu Pavel wrote:
The differences is that driver_wext.c expects the wifi kernel driver
to implement the SIOCSIWPRIV ioctl and respond to android commands
like RSSI, MACADDR etc, while driver_awext.c replies to android
commands by using standard wireless extensions ioctls and works for
most
Thanks Dimitry,
I updated the guide. On second look I found out why it the android private
namespace socket didn't work for me.If /data/system/wpa_supplicant folder
exists the ifname will be built incorrect in wifi.c wpa_ctrl_open()
function.
Do you think I should submit the wpa driver that
Hi Nicu,
I am not sure what the difference between driver_awext.c and
driver_wext.c.
And the last one has the necessary changes.
Thanks,
Dmitry
On May 10, 9:24 am, Nicu Pavel npa...@ituner.com wrote:
Thanks Dimitry,
I updated the guide. On second look I found out why it the android private
The differences is that driver_wext.c expects the wifi kernel driver
to implement the SIOCSIWPRIV ioctl and respond to android commands
like RSSI, MACADDR etc, while driver_awext.c replies to android
commands by using standard wireless extensions ioctls and works for
most wifi drivers.
Basically
Very good and useful guide. Just want to add to wpa_supplicant socket
control.
Despite you can use it as you mentioned the idea was to use special
socket pair implementation like this:
wpa_supplicant.conf:
ctrl_interface=wlan0
init.xxx.rc:
service wpa_supplicant /system/bin/wpa_supplicant \
12 matches
Mail list logo
