Closed Bug 1038624 Opened 10 years ago Closed 6 years ago

Wi-Fi goes to 'offline' when it is in 'Obtaining IP address'

Categories

(Firefox OS Graveyard :: Wifi, defect, P5)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ap00344712, Unassigned)

Details

User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MS-RTC LM 8)

Steps to reproduce:

Steps to reproduce:
>Turn ON Wi-Fi
>Device will scan and list the available AP's
>Select one AP to connect
 


Actual results:

The device display below states after selecting one AP:
>Authenticating
>Connecting
>Obtaining IP Address
>Connection Failed
>Offline
2/3 time the device will try to obtain an IP address. It will not get succeeded. Then it moves to Connection Failed and finally goes to offline.

Logcat log snippet:


05-21 03:11:33.500 D/wpa_supplicant( 5028): RX ctrl_iface - hexdump(len=10): 44 49 53 43 4f 4e 4e 45 43 54

05-21 03:11:33.500 D/wpa_supplicant( 5028): wlan0: Control interface command 'DISCONNECT'

05-21 03:11:33.500 D/wpa_supplicant( 5028): wlan0: Cancelling scan request

05-21 03:11:33.500 D/wpa_supplicant( 5028): wpa_driver_nl80211_disconnect(addr=20:54:76:f4:2e:9e reason_code=3)

05-21 03:11:33.539 D/wpa_supplicant( 5028): wlan0: Event DEAUTH (12) received

05-21 03:11:33.539 D/wpa_supplicant( 5028): wlan0: Deauthentication notification

05-21 03:11:33.539 D/wpa_supplicant( 5028): wlan0:  * reason 3 (locally generated)

05-21 03:11:33.539 D/wpa_supplicant( 5028): Deauthentication frame IE(s) - hexdump(len=0): [NULL]

05-21 03:11:33.539 I/wpa_supplicant( 5028): wlan0: CTRL-EVENT-DISCONNECTED bssid=20:54:76:f4:2e:9e reason=3 locally_generated=1

05-21 03:11:33.539 D/wpa_supplicant( 5028): CTRL_IFACE monitor send - hexdump(len=40): 2f 64 61 74 61 2f 6d 69 73 63 2f 77 69 66 69 2f 73 6f 63 6b 65 74 73 2f 77 70 61 5f 63 74 72 6c ...

05-21 03:11:33.539 D/wpa_supplicant( 5028): wlan0: Auto connect enabled: try to reconnect (wps=0 wpa_state=9)

05-21 03:11:33.539 D/wpa_supplicant( 5028): wlan0: Setting scan request: 0 sec 500000 usec

05-21 03:11:33.539 D/wpa_supplicant( 5028): Added BSSID 20:54:76:f4:2e:9e into blacklist

05-21 03:11:33.539 D/wpa_supplicant( 5028): wlan0: Setting scan request: 0 sec 100000 usec

05-21 03:11:33.539 D/wpa_supplicant( 5028): wlan0: State: COMPLETED -> DISCONNECTED

05-21 03:11:33.539 D/wpa_supplicant( 5028): wpa_driver_nl80211_set_operstate: operstate 1->0 (DORMANT)

05-21 03:11:33.539 D/wpa_supplicant( 5028): netlink: Operstate: linkmode=-1, operstate=5


Expected results:

The device should get the IP address and Wi-Fi connection should succeeded.
Summary: When we start Wi-Fi, it will scan all the AP's, but it will not connect to selected AP. It says that 'Obtaining IP address' and after that 'Connection Failed'. Finally it goes to 'offline' → Wi-Fi goes to 'offline' when it is in 'Obtaining IP address'
Severity: normal → critical
OS: All → Gonk (Firefox OS)
Priority: -- → P5
Hardware: All → ARM
If the problem is in dhcp, you should check the code in external/dhcpcd. Wifi uses dhcpcd in gonk to obtain the ip address. It's possible that there is an interoperability problem between dhcp client and server.
Hi Vincent...
Thanks for your reply.
Actually if you see the dmesg kernel log, seems to be, it fails to start the dhcpcd service init.
I am struggling to make it up. Do you guys having any idea on how to overcome this issue ?

dmesg log snippet:
[  285.161804] c0 987 (ksdioirqd/mmc2) wlan: SCAN COMPLETED: scanned AP count=7
[  285.185241] c1 1237 (wpa_supplicant) wlan: Connected to bssid 00:XX:XX:XX:ae:e1 successfully
[  285.201019] c0 4 (kworker/0:0) ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

[  285.367797] c0 1 (init) init: no such service 'dhcpcd_/system/etc/dhcpcd/dhcpcd.conf:-f wlan0 wlan0'

[  295.542938] c1 1237 (wpa_supplicant) wlan: Successfully disconnected from 00:XX:XX:XX:ae:e1: Reason code 3
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.