Redpine: wifi-ap stopped working after restart

Bug #1773400 reported by Siva Rebbagondla on 2018-05-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Critical
Unassigned
Xenial
Critical
Unassigned

Bug Description

SRU Justification:
------------------

Impact:
    Wi-Fi access point isn’t visible to outside devices after reboot

Test Case:
    Configure Wi-Fi AP using setup wizard:
       $ sudo wifi-ap.setup-wizard

    Check configured AP settings:
       $ sudo wifi-ap.config get

       debug: false
       dhcp.lease-time: 12h
       dhcp.range-start: 10.0.60.2
       dhcp.range-stop: 10.0.60.200
       disabled: false
       share.disabled: false
       share.network-interface: wlan0
       wifi.address: 10.0.60.1
       wifi.channel: 6
       wifi.country-code:
       wifi.hostapd-driver: nl80211
       wifi.interface: wlan0
       wifi.interface-mode: direct
       wifi.netmask: ff000000
       wifi.operation-mode: g
       wifi.security: wpa2
       wifi.security-passphrase: some-password
       wifi.ssid: dell-gateway

    Check in third-party stations. SSID is invisible.

    Restart AP and check its status:
       $ sudo wifi-ap.status restart-ap

    Check status of AP. It is showing true.
       $ sudo wifi-ap.status
       ap.active: true

    At this point also, Wi-Fi access point is not visible.

Fix:
    Power save is enabled in AP mode. it must be disabled.

Regression potential:
    Ran "wifi-ap.status restart-ap" command in every 1 minute and observed whether it is visible to third party devices are not. And it is behaving as expected.

This patch is for tracking only, please don't triage.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1773400

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Critical
Changed in linux (Ubuntu Xenial):
status: New → Confirmed
importance: Undecided → Critical
description: updated
Stefan Bader (smb) on 2018-06-15
Changed in linux (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu Xenial):
status: Confirmed → Fix Committed
Brad Figg (brad-figg) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-xenial

Verified on Dell IoT Edge 300x kernel snap (r93) based on 4.4.0-132.158

tags: added: verification-done-xenial
removed: verification-needed-xenial
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers