New issue
Advanced search Search tips

Issue 881372 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Dec 20
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

Lost WiFi connectivity after updating to Chrome OS m68, "out of range"

Project Member Reported by caseq@chromium.org, Sep 6

Issue description

Chrome Version: 68.0.3440.118
OS: Chrome OS

I have lost an ability to connect to my home wifi network after an upgrade to m68, the error I'm getting is "Failed to connect to network '<ssid>': Out of range". This happens even when the chromebook is within 3ft of the wifi AP. It is still able to connect to other (open) networks in the building and to a tethering AP in an Android phone (using WPA2/PSK).

I tried changing wifi channel and disabling WDS, but it did not help.
The hardware is Samsung 303C (XE303C12)
The access point is TP-Link TL-WR1043N/ND v1 (Atheros AR9132 rev 2)
running OpenWrt 18.06.1 r7258-5eb055306.
Here's /etc/config/wireless from my access point:

config wifi-device  radio0
        option type     mac80211
        option channel  8
        option macaddr  54:e6:fc:<censored>            
        option hwmode   11ng
        option htmode   HT20
        list ht_capab   SHORT-GI-40
        list ht_capab   DSSS_CCK-40
 
config wifi-iface
        option device   radio0
        option network  lan
        option mode     ap
        option ssid     <censored>   
        option hidden   0
        option wds      1
        option encryption 'psk'
        option key '<censored>' 

Note that a bunch of other devices, including Android phones and another wds station of the same model have no problem connecting to the AP and the chromebook only started having problem after recent update. Unfortunately, the exact version when it regressed is unknown, since the chromebook wasn't used since Feb 2018.

 
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
Status: Archived (was: Untriaged)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.

Sign in to add a comment