| Summary: | net-wireless/hostapd reports wrongly to be 'up' after suspend/resume | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | skaumo <skaumo> |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Could you please take this upstream, to the hostapd developers? This seems to be a bug in hostapd, so it should be taken upstream to the developers :-) You can find the upstream mailing list right here: http://lists.infradead.org/mailman/listinfo/hostap - they will be able to help debug the issue, and help make a patch to fix it. |
Steps: - set up an AP with hostapd on a suspend capable machine - suspend (e.g.: echo "mem">/sys/power/state) - resume * Expected hostapd to spin up the AP after resume automatically (preferably) or report down state otherwise * Actual: - /etc/init.d/hostapd status claims to be "started" - hostapd process is running - driver claims to be still in Master mode - but the AP is actually down # iwconfig wifi IEEE 802.11bgn Mode:Master Tx-Power=1 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Tested against iwlwifi, Intel 7260