path: root/src/drivers/driver_roboswitch.c
Commit message (Collapse)AuthorAgeFilesLines
* Fix typos found by codespellPavel Roskin2011-09-211-1/+1
| | | | Signed-off-by: Pavel Roskin <proski@gnu.org>
* driver_roboswitch: include net/if.h instead of linux/if.hFelix Fietkau2010-11-091-1/+1
| | | | including linux/if.h clashes with other header files on some systems
* Add drv_event_eapol_rx() helperJouni Malinen2010-01-031-8/+2
* Use driver event, EVENT_EAPOL_RX, for EAPOL frame indicationJouni Malinen2010-01-031-2/+6
* Move definitions away from hostapd_defs.hJouni Malinen2009-11-231-4/+0
| | | | | Clean up definitions to reduce need to include header files from the hostapd directory into files under the src subdirectories.
* General revision of RoboSwitch driverJouke Witteveen2009-04-261-144/+176
| | | | | | | | | | | | | | | | | | | | Attached is a patch for the RoboSwitch driver in trunk. It is a general revision of the source code. Changes: - Improved IEEE 802.1X conformance ([1]) - Better conformity to Broadcom specifications - Fixed compatibility with different chipset revisions It is worth noting that performance may drop a little using the new driver. This can be overcome by using "multicast_only=1" as a parameter. In that case only packets to the PAE group address are regarded, as the previous revision of the driver did. A more detailed description of the parameter and it's consequences is available at [2] (summary: use "multicast_only=1" whenever possible). [1] http://lists.shmoo.com/pipermail/hostap/2009-February/019398.html [2] http://forum.openwrt.org/viewtopic.php?id=19873
* Determiner whether driver is wired at runtime based on capabilitiesJouni Malinen2009-03-071-0/+10
| | | | | | Do not use just the driver name for this since driver_ndis.c supports both wired and wireless NDIS drivers and needs to indicate the driver type after initialization.
* Better support in RoboSwitch driverJouke Witteveen2009-02-041-6/+11
| | | | | | | | | | | | I am terribly sorry, but because of a lack of testing equipment the patch was submitted not properly tested. Because the chipset documentation is not publicly available all behaviour has to be found out by experimentation. The other day, I made some incorrect assumptions based on my findings. I do believe the attached patch does support the whole RoboSwitch line (5325, 5350, 5352, 5365 and others). It is a drop-in substitution for my previous submission.
* Better support in RoboSwitch driverJouke Witteveen2009-02-031-21/+39
| | | | | | | | | | The RoboSwitch driver of wpa_supplicant had one shortcoming: not supporting the 5365 series. I believe the patch attached fixes this problem. Furthermore it contains a small readability rewrite. It basically is an explicit loop-rollout so that the wpa_driver_roboswitch_leave style matches that of wpa_driver_roboswitch_join.
* Fixed a bug in read -> _read cleanup; one missed changeJouke Witteveen2008-11-191-1/+1
* roboswitch: Minor coding style cleanupJouni Malinen2008-11-181-32/+44
* Add RoboSwitch driver interface for wpa_supplicantJouke Witteveen2008-11-181-0/+409
Find attached the patch that creates a new driver: roboswitch. This driver adds support for wired authentication with a Broadcom RoboSwitch chipset. For example it is now possible to do wired authentication with a Linksys WRT54G router running OpenWRT. LIMITATIONS - At the moment the driver does not support the BCM5365 series (though adding it requires just some register tweaks). - The driver is also limited to Linux (this is a far more technical restriction). - In order to compile against a 2.4 series you need to edit include/linux/mii.h and change all references to "u16" in "__u16". I have submitted a patch upstream that will fix this in a future version of the 2.4 kernel. [These modifications (and more) are now included in the kernel source and can be found in versions 2.4.37-rc2 and up.] USAGE - Usage is similar to the wired driver. Choose the interfacename of the vlan that contains your desired authentication port on the router. This name must be formatted as <interface>.<vlan>, which is the default on all systems I know.