Feature #196
Enable hostapd and configure in rootfs
| Status: | Closed | Start date: | 07 Jul 2013 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assignee: |  Hammel | % Done: | 100% | |
| Category: | 04 - Root File System | |||
| Target version: | 1.0 - Atreides | |||
| Severity: | 02 - High |
Description
This will allow the Pi to be a wireless access point.
This may require feature changes/additions to bui-network-config.
See:- http://w1.fi/hostapd/
- http://elinux.org/RPI-Wireless-Hotspot
- http://sirlagz.net/2012/08/09/how-to-use-the-raspberry-pi-as-a-wireless-access-pointrouter-part-1/
- http://nims11.wordpress.com/2012/04/27/hostapd-the-linux-way-to-create-virtual-wifi-access-point/
- http://www.ibm.com/developerworks/library/l-wifiencrypthostapd/
Associated revisions
RM #196: Enabled hostapd in buildroot configuration. A meaningful, default configuration (or support via
bui-network-config) still needs to be added.
RM #196: Updated network init script to choose wireless/wired client or wireless access point configuration.
History
#1
Updated by Hammel over 7 years ago
- 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.
#2
Updated by Hammel about 7 years ago
- Description updated (diff)
#3
Updated by Hammel about 7 years ago
- Description updated (diff)
#4
Updated by Hammel about 7 years ago
- % Done changed from 20 to 30
hostapd configuration support is now added as a task to bui-network-config, RM #203.
#5
Updated by Hammel about 7 years ago
- Priority changed from Urgent to Immediate
- Severity changed from 03 - Medium to 02 - High
#6
Updated by Hammel about 7 years ago
- File hostapd.log added
- % Done changed from 30 to 40
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.
#7
Updated by Hammel about 7 years ago
- % 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.
#8
Updated by Hammel about 7 years ago
Ready to update S40network based on use of /etc/network/nettype marker file.
#9
Updated by Hammel about 7 years ago
- 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.