Feature #196
closed
Enable hostapd and configure in rootfs
Added by Hammel over 11 years ago.
Updated over 11 years ago.
Category:
04 - Root File System
Description
This will allow the Pi to be a wireless access point.
This may require feature changes/additions to bui-network-config.
See:
Files
- Status changed from New to In Progress
- % Done changed from 0 to 20
Enabled hostapd in buildroot configuration. A meaningful, default configuration (or support via
bui-network-config) still needs to be added.
- Description updated (diff)
- Description updated (diff)
- % Done changed from 20 to 30
hostapd configuration support is now added as a task to bui-network-config, RM #203.
- Priority changed from Urgent to Immediate
- Severity changed from 03 - Medium to 02 - High
hostapd is now enabled in rootfs and bui-network-config generates configuration files for it.
However, the configuration does not bring up hostapd completely. See the attached log file.
- % Done changed from 40 to 90
The reason hostapd doesn't come up is because the password in the psk file was too short. See RM #205.
If the password is fixed, hostapd comes up and I can connect to it from my android phone.
After #205 is fixed, I'll need some options in bui-network-config (see RM #206) to choose between running as an Access Point or as a wireless client. Only one or the other should run. This means that bui-network-config needs to save a marker under /etc/networks that tells S40network whether to start the wireless client or hostapd.
Once #206 is implemented I need to update S40network to use the marker file.
Ready to update S40network based on use of /etc/network/nettype marker file.
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
Updated network init script to choose wireless/wired client or wireless access point configuration.
This issue can now be closed.
Also available in: Atom
PDF