Main index | Section 8 | Options |
The ndis_events daemon works by listening for interface information events via a routing socket. When it detects an event that was generated by an ndis(4) interface, it transmits it via UDP packet on the loopback interface, where wpa_supplicant(8) is presumably listening. The standard wpa_supplicant(8) distribution includes its own version of this utility for use with Windows[rg]. The FreeBSD version performs the same functions as the Windows[rg] one, except that it uses an ioctl(2) and routing socket interface instead of WMI.
Note that a single instance of ndis_events is sufficient to scan for events for any number of ndis(4) interfaces in a system.
| |
Process all events. By default, ndis_events will only process and forward media-specific events, which contain PMKID candidate information, and not bother forwarding connect and disconnect events, since wpa_supplicant(8) normally can determine the current link state on its own. In some cases, the additional connect and disconnect events only confuse it and make the association and authentication process take longer. | |
| |
Run in debug mode. This causes ndis_events to run in the foreground and generate any output to the standard error instead of using the syslog(3) facility. | |
| |
Run in verbose mode. This causes ndis_events to emit notifications when it receives events. | |
NDIS_EVENTS (8) | August 30, 2007 |
Main index | Section 8 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
“ | A UNIX saleslady, Lenore, Enjoys work, but she likes the beach more. She found a good way To combine work and play: She sells C shells by the seashore. |
” |