mainpage.doxygen 2.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152
  1. /**
  2. \mainpage Developers' documentation for hostapd
  3. hostapd includes IEEE 802.11 access point management (authentication /
  4. association), IEEE 802.1X/WPA/WPA2 Authenticator, EAP server, and
  5. RADIUS authentication server functionality. It can be build with
  6. various configuration option, e.g., a standalone AP management
  7. solution or a RADIUS authentication server with support for number of
  8. EAP methods.
  9. The goal of this documentation and comments in the source code is to
  10. give enough information for other developers to understand how hostapd
  11. has been implemented, how it can be modified, how new drivers can be
  12. supported, and how hostapd can be ported to other operating
  13. systems. If any information is missing, feel free to contact Jouni
  14. Malinen <j@w1.fi> for more information. Contributions as
  15. patch files are also very welcome at the same address. Please note
  16. that hostapd is licensed under dual license, GPLv2 or BSD at user's
  17. choice. All contributions to hostapd are expected to use compatible
  18. licensing terms.
  19. The source code and read-only access to hostapd CVS repository
  20. is available from the project home page at
  21. http://hostap.epitest.fi/hostapd/. This developers' documentation
  22. is also available as a PDF file from
  23. http://hostap.epitest.fi/hostapd/hostapd-devel.pdf .
  24. The design goal for hostapd was to use hardware, driver, and
  25. OS independent, portable C code for all WPA functionality. The source
  26. code is divided into separate C files as shown on the \ref
  27. code_structure "code structure page". All hardware/driver specific
  28. functionality is in separate files that implement a \ref
  29. driver_wrapper "well-defined driver API". Information about porting
  30. to different target boards and operating systems is available on
  31. the \ref porting "porting page".
  32. EAPOL (IEEE 802.1X) state machines are implemented as a separate
  33. module that interacts with \ref eap_module "EAP server implementation".
  34. Similarly, RADIUS authentication server is in its own separate module.
  35. Both IEEE 802.1X and RADIUS authentication server can use EAP server
  36. functionality.
  37. hostapd implements a \ref ctrl_iface_page "control interface" that can
  38. be used by external programs to control the operations of the hostapdt
  39. daemon and to get status information and event notifications. There is
  40. a small C library that provides helper functions to facilitate the use
  41. of the control interface. This library can also be used with C++.
  42. \image html hostapd.png "hostapd modules"
  43. \image latex hostapd.eps "hostapd modules" width=15cm
  44. */