Bug #439
hostapd config leaves rsn_pairwise at ccmp
| Status: | Closed | Start date: | 21 May 2015 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assignee: |  Hammel | % Done: | 100% | |
| Category: | 04 - Root File System | |||
| Target version: | 0.11.0 | |||
| Severity: | 01 - Critical |
Description
It needs to be TKIP to match the clients.
This was configured via bui-network-config.
Associated revisions
RM #439: Fix load of hostap config to default to TKIP to match clients expectations.
RM #439: Fix load of hostap config to default to TKIP to match clients expectations.
History
#1
Updated by Hammel about 5 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
This was supposed to be fixed once before. See RM #425, RM #376 and this revision
The real problem here is having two places that handle this. We have two because bui-network-config is a standalone app. The fix would be to have bui-network-config and piboxd use a library that does these changes for them, so the changes are handled in a single code base.
#2
Updated by Hammel about 5 years ago
- % Done changed from 10 to 50
Updated bui-network-config to use TKIP as default for RSN-PAIRWISE when loading the hostapd conf file.
Need to verify this fix actually corrects the problem. It should, but a real test is required to verify.
#3
Updated by Hammel about 5 years ago
FYI - the updated bui-network-config is built into the latest rootfs so that's what should be tried.
Rebuild the rootfs image and use that to image an SD card.
#4
Updated by Hammel about 5 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
This appears to be fixed, though the WAP doesn't come up automatically for some reason. That will be a different issue. TKIP is correctly set in /etc/hostapd.conf.
Closing issue.