[RTEMS Project] #3223: libbsd: wpa_supplicant has to be started dynamically

[RTEMS trac]

#3223: libbsd: wpa_supplicant has to be started dynamically
----------------------------------+---------------------------------
 Reporter:  Christian Mauderer    |       Owner:  Christian Mauderer
     Type:  enhancement           |      Status:  accepted
 Priority:  normal                |   Milestone:  Indefinite
Component:  network/libbsd        |     Version:  5
 Severity:  normal                |  Resolution:
 Keywords:  SoC libbsd WiFi WLAN  |
----------------------------------+---------------------------------

Comment (by Christian Mauderer):

 == Possible Approaches

 The DHCP client used in the libbsd (dhcpcd) has a script hook support.
 That support has been removed in the RTEMS port because there is no script
 interpreter. One possibility would be to try to make the dhcpcd script
 hooks usable on RTEMS so that they can call C functions instead of the
 scripts. Such a hook could then start a wpa_supplicant from a hook.

 Another solution would be to take a detailled look at the FreeBSD
 implementation and create something similar.

 == Additional Problems

 Most likely it will be necessary to start more then one instance of
 wpa_supplicant (for example if two interfaces are connected). Currently
 that is not possible. The wpa_supplicant should be reviewed whether it can
 be started multiple times in parallel.

 == Necessary Hardware

 I would recommend some real hardware (like a Beagle Bone Black with a
 RTL8188 based USB WiFi dongle) and a hardware debugger (Segger J-Link,
 Flyswatter 2, something supported by OpenOCD, ...). Real hardware with
 WiFi is the most likely later use case.

 Theoretically WPA should be usable on wired interfaces. So it might be
 possible to develop this in a simulator too. The advantage of this is that
 there are no hardware costs and a simple debug integration. If you think
 about that solution, please discuss it with your (planned) mentor before
 starting.

 == Related projects

 #3222 will need some WiFi related rc.conf integration too. Maybe the hot-
 plug detection of that project could be of some use too.

--
Ticket URL: <http://devel.rtems.org/ticket/3223#comment:4>
RTEMS Project <http://www.rtems.org/>
RTEMS Project