Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37744 - [hostapd] & suspend to disk: wifi AP isn't re-created on resume

Attached to Project: Community Packages
Opened by Thomas Riccardi (Niluge_KiWi) - Tuesday, 12 November 2013, 20:16 GMT
Last edited by Sergej Pupykin (sergej) - Saturday, 16 November 2013, 18:47 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I created a wifi access point following this doc https://wiki.archlinux.org/index.php/Software_Access_Point. I use hostapd and a usb wifi dongle (Bus 008 Device 006: ID 148f:2070 Ralink Technology, Corp. RT2070 Wireless Adapter), everything works great, except when I suspend to disk/resume: after resuming, the wifi AP doesn't show up, and a service restart hostapd makes it work again.


Additional info:
* linux 3.11.5-1-ARCH
* hostapd 2.0-6

hostapd logs:
Nov 12 09:52:04 my-pc hostapd[28449]: wlan0: STA xx:xx:xx:xx:xx:xx WPA: group key handshake completed (RSN)
Nov 12 20:50:45 my-pc hostapd[28449]: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
Nov 12 20:54:55 my-pc systemd[1]: Stopping Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator...
Nov 12 20:54:55 my-pc systemd[1]: Starting Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator...
Nov 12 20:54:55 my-pc systemd[1]: Started Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator.
Nov 12 20:55:01 my-pc hostapd[2904]: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Nov 12 20:55:01 my-pc hostapd[2904]: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Nov 12 20:55:01 my-pc hostapd[2904]: wlan0: STA xx:xx:xx:xx:xx:xx RADIUS: starting accounting session 5282878F-00000000
Nov 12 20:55:01 my-pc hostapd[2904]: wlan0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)

suspend after 09:52 with a client connected. Resume at 20:50, service restart hostapd at 20:54:55, client reconnects at 20:55:01.

dmesg.log:
up to 244323.155595: previous resume
246671.101598: suspend @~09:52 (but dmesg timestamp seems to be the time at resume, not at suspend...)
246676.701966: end resume @~20:50
246935.076493: service restart hostapd
   dmesg.log (6.3 KiB)
This task depends upon

Closed by  Sergej Pupykin (sergej)
Saturday, 16 November 2013, 18:47 GMT
Reason for closing:  Upstream
Additional comments about closing:  or not a bug
Comment by Sergej Pupykin (sergej) - Wednesday, 13 November 2013, 10:03 GMT
please report upstream
Comment by Thomas Riccardi (Niluge_KiWi) - Wednesday, 13 November 2013, 10:07 GMT
On hostapd?
Comment by Sergej Pupykin (sergej) - Wednesday, 13 November 2013, 10:10 GMT
I think yes, or may be proper solution is restarting hostapd from script which executed on resume

Loading...