-
Notifications
You must be signed in to change notification settings - Fork 0
Bug#3 Progress
doru91 edited this page Feb 25, 2017
·
16 revisions
Current implementation
When the second interface is created, PS is automatically disabled and the Average Power Consumption is ~600mW.
Code version
Git head is at: https://github.com/doru91/linux-stable/commit/88d13870bb100bfa3945b1424387d1d90ade7fac The problem is that the card still exists PS mode out-of-nowhere but there are tests (1/20) when the card behaves correctly for a longer timer (e.g.: 15 minutes)
Test bed
- WiFi Dongle: TP-LINK TL-WN722N
- AP1: [TP-LINK Archer C2] (http://www.tp-link.com.au/products/details/cat-9_Archer-C2.html), DTIM count = 2, beacon interval = 100ms, DHCP: 192.168.0.0/24, SSID: 2.4_mptcp, Password: iarbaeverde
- AP2: Android Wi-Fi Hotsport from a Nexus5 smartphone running CM13, 802.11n, DTIM count = 2, beacon interval = 100ms, DHCP: 192.168.43.0/24, SSID: AndroidAP, Password: iarbaeverde
- Power Monitor: Monsoon
Scenario
- disable wpa_supplicant on the host (e.g.: sudo mv /sbin/wpa_supplicant /sbin/wpa_supplicant_temp + kill the existing wpa_supplicant process)
- create two virtual interfaces in managed mode: wlan4 and rename27
- connect wlan4 at AP1 (using wpa_supplicant from command line)
- connect rename27 at AP2 (using wpa_supplicant from command line)
- dhclient on wlan4 (sudo dhcllient wlan4)
- dhclient on rename27 (sudo dhclient rename27)
- enable PS mode (iw wlan4 set power save on -> this command will enable PS for both interfaces)
- Result: Average Power Consumption: ~380mW ([Monsoon Files] (https://drive.google.com/open?id=0B5SBH08PU_ChNHYyQUVLTUFhbXc))
- pings on wlan4 at 1s interval (card wakes up both for transmitting data then for receiving data) Result: Average Power Consumption: ~425mW ([Monsoon Files] (https://drive.google.com/open?id=0B5SBH08PU_ChV1RJRXhBNjN4bEU))
- pings on wlan4 + pings on rename27 in parallel (card wakes up both for TX, then RX data) Result: Average Power Consumption: ~485mW ([Monsoon Files] (https://drive.google.com/open?id=0B5SBH08PU_ChUVMxNFVXZTUxbEU))
- [dmesg_log] (https://drive.google.com/open?id=0B5SBH08PU_ChaWdYMVZsYkZlVVE) (while true; do sudo dmesg -c >> file; done)
- [Wireshark capture] (https://drive.google.com/open?id=0B5SBH08PU_ChNVRnN0pzZEpTREU)