| Summary: | wireless: Enable power save | ||
|---|---|---|---|
| Product: | Network | Reporter: | Michael Tremer <michael.tremer> |
| Component: | Wireless | Assignee: | Arne.F <arne.fitzenreiter> |
| Status: | NEW --- | QA Contact: | Michael Tremer <michael.tremer> |
| Severity: | Balancing | ||
| Priority: | Will affect most users | ||
| Version: | unspecified | ||
| Hardware: | unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugzilla.ipfire.org/show_bug.cgi?id=13098 | ||
|
Description
Michael Tremer
2018-09-24 22:22:39 UTC
IPFire 2.x has already an option to set the txpower in the web interface of the ap page. This is filled with "auto" which mean "max" but could set down by entering a value in db or mw. Im not sure if the other powersave options are a good idea for AP mode. Many of them slow down the network to not wake the cpu. I have seen ping times of several seconds with activate wlan power save. (In reply to Arne Fitzenreiter from comment #1) > IPFire 2.x has already an option to set the txpower in the web interface of > the ap page. This is filled with "auto" which mean "max" but could set down > by entering a value in db or mw. > This is for IPFire 3's network. I guess there is no way to configure this now. > Im not sure if the other powersave options are a good idea for AP mode. Many > of them slow down the network to not wake the cpu. I have seen ping times of > several seconds with activate wlan power save. In that case, power saving is broken. But IPFire 3 does not only support AP mode. I guess in all cases the default should be auto, but an AP always sends beacons with maximum transmit power. |