1167550 - [Flame] Continuous disconnection from specific network

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Wifi, defect)

Description

[u495161]

Attachment: Logcat form disconnecting

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150520175203



Actual results:

After established connection to network, after about 3 seconds, Flame disconnects and try to reconnect.
It is happening on one specific network. Other networks work without problems

Comment 1

[u495161]

Firstly, I thought it is related to IPv6, but on the other network which also uses IPv4/IPv6 Flame works good

Comment 2

[u495161]

The bug does NOT occur on:

Build ID: 20150526104742
GCI: 2015-05-26 03:56:33 0d67eb54

Builds between 20150520175203 and 20150526104742 were not tested

I still don't know what was the reason of this weird behavior, but it looks like fixed for me.

Comment 3

[:gerard-majax]

Thanks kamil! Would you mind bisecting to find the patch that fixed it?

Comment 4

[u495161]

I tried, but now it is working for old builds too.
I don't understand, maybe this wasn't B2G problem, just something with router... I don't know if someone changed something with router, so I can't confirm that.

Comment 5

[:gerard-majax]

I would not consider this as an indication of fix somehow, because investigating similar issue on my side on Z3 Compact I had some intermittence in reproducing the issue.

Comment 6

[Vincent Chang[:vchang][changyihsin]]

I found some error messages when setting route stuff in the log. But I think it's not related to the bug description in comment 1. Ni? Henry and see his comments. 

How do you identify that network is disconnect and reconnect? Do you see the wifi tries to associate to others SSID? From the log, I don't see the wifi connection is disconnected.

Comment 7

[u495161]

Icon on status bar disappear, and in WiFi settings i saw that network is Offline, and after a while Obtaining IP address.
But as I said in comment #4, it works for now

Comment 8

[u495161]

okay, it looks like the problem is back, weird because on this build it worked earlier


i restarted router and it looks good now, but other devices dont have problems with this network at all

Comment 9

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Do you know what base build you're on for the flame?  I think we had this in an older version of the base build.

adb shell getprop ro.bootloader

should get us what build you're on.

Comment 10

[u495161]

Result of adb shell getprop ro.bootloader:

L1TC000118D0


I can reflash later if needed

Comment 11

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Odd.  That's the latest version.

Looking at the log, I think you're getting rejected by the server:
05-22 12:59:09.359  6222  6222 D wpa_supplicant: EAPOL: External notification - EAP success=0
05-22 12:59:09.359  6222  6222 D wpa_supplicant: EAPOL: Supplicant port status: Unauthorized
05-22 12:59:09.359  6222  6222 D wpa_supplicant: nl80211: Set supplicant port unauthorized for 

Are you logging in via EAP?  It seems weird to me that you're getting rejected soon after connecting...

Comment 12

[Henry Chang [:hchang]]

I think this may be the duplicate of Bug 1167466 which caused by interleaving DHCP request.

Comment 13

[u495161]

I am logging using WPA-PSK

Comment 14

[:gerard-majax]

(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #11)
> Odd.  That's the latest version.
> 
> Looking at the log, I think you're getting rejected by the server:
> 05-22 12:59:09.359  6222  6222 D wpa_supplicant: EAPOL: External
> notification - EAP success=0
> 05-22 12:59:09.359  6222  6222 D wpa_supplicant: EAPOL: Supplicant port
> status: Unauthorized
> 05-22 12:59:09.359  6222  6222 D wpa_supplicant: nl80211: Set supplicant
> port unauthorized for 
> 
> Are you logging in via EAP?  It seems weird to me that you're getting
> rejected soon after connecting...

(In reply to Henry Chang [:henry] from comment #12)
> I think this may be the duplicate of Bug 1167466 which caused by
> interleaving DHCP request.

Oh so much fun ... That's exactly what I was seeing in my first wifi issues reports ...

Comment 15

[BMO Automation]

Firefox OS is not being worked on