| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
directory [1]
- add the FILES section to the wpa_supplicant.conf.5 file, so that people
will be able to detect the example configuration file easier. [2]
PR: docs/121821 [2]
Approved by: brooks [1]
MFC after: 3 days
|
|
|
|
|
|
| |
o add private wired driver that fixes various bugs in the vendor version
Submitted by: thompsa (ndis fixups)
|
|
|
|
|
|
|
| |
o add+enable radius acl support
Supported by: Hobnob
Submitted by: Chris Zimmermann (acl support)
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: "Paul B. Mahol" <onemda@gmail.com>
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
wpa_supplicant expects that it has exclusive access to the net80211 state so
when its starts poking in the WEP/WPA settings and the card is already
scanning it can cause net80211 to try and associate incorrectly with a
protected AP.
This is an inconvenience for firmware based cards such as iwi where it can be
sent an auth instruction with incomplete security info and cause a firmware
error.
Remove the 'ifconfig up' from network.subr since wpa_supplicant will
immediately down the interface again.
Reported by: Guy Helmer (and others)
Reviewed by: sam, brooks, avatar
MFC after: 3 days
|
|
|
|
|
|
| |
PR: docs/116658
Submitted by: Henrik Brix Andersen <henrik@brixandersen.dk>
MFC after: 3 days
|
| |
|
|
|
|
|
| |
Reviewed by: sam
Approved by: re (kensmith)
|
|
|
|
|
| |
PR: 116439
Approved by: re (gnn)
|
|
|
|
|
|
|
|
|
|
| |
WPA_SUPPLICANT_CFLAGS, etc. (consult the Makefile's for details)
o enable ipv6 support in hostapd (for communication w/ a radius backend)
PR: bin/116164
Submitted by: "Scot Hetzel" <swhetzel@gmail.com>
Approved by: re (gnn)
MFC after: 2 weeks
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
|
|
|
| |
PR: docs/113127
Submitted by: "O. Hartmann"<ohartman@mail.zedat.fu-berlin.de>
Reviewed by: keramida
Approved by: re (bmah)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
FreeBSD 6.2, but it didn't make it into RELENG_6_2.
Update the manual page to say "FreeBSD 6.3".
PR: docs/114429
Submitted by: Henrik Brix Andersen <henrik@brixandersen.dk>
MFC after: 3 days
Approved by: re (bmah)
|
|
|
|
|
|
|
|
|
|
|
| |
o unix domain socket to wpa_cli is configured w/ CONFIG_CTRL_IFACE_UNIX
o terminate on last interface option is configured w/ CONFIG_TERMINATE_ONLASTIF
o ndis/Packet32.c fixups to force roaming mode to manual
o document new mixed_cell config knob
Submitted by: thompsa (Packet32.c)
Reviewed by: thompsa, sephe
Approved by: re (hrs)
|
|
|
|
| |
Approved by: re (hrs)
|
|
|
|
|
|
|
| |
for 802.1x over wired interfaces
Submitted by: Jouke Witteveen
Approved by: re (hrs)
|
| |
|
|
|
|
|
| |
Obtained from: netbsd
MFC after: 1 week
|
|
|
|
|
|
| |
PR: bin/104457
Submitted by: Henrik Brix Andersen
MFC after: 1 week
|
| |
|
|
|
|
| |
Obtained from: netbsd
|
|
|
|
| |
Obtained from: netbsd
|
|
|
|
| |
Obtained from: netbsd
|
| |
|
|
|
|
|
| |
Noticed by: Jouni Malinen
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
| |
PR: bin/94735
Submitted by: Scot Hetzel <swhetzel@gmail.com>
Requested by: scottl
|
|
|
|
|
|
|
|
| |
http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html
The src.conf(5) manpage is to follow in a few days.
Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
|
|
|
|
|
|
| |
Submitted by: Yoshihiko Sarumaru (mistral at imasy dot or dot jp)
PR: docs/93801 and docs/93803
MFC after: 2 days
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
wep key configure at key indices > 0 and 802.1x/EAPOL operation
with ap's that want the station to install a key at indices > 0.
Hard work by: Joe Love
Reviewed by: avatar
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
ENABLE_WPA_SUPPLICANT_EAPOL is no more, now use NO_WPA_SUPPLICANT_EAPOL
to build with only WPA-PSK support.
Reviewed by: ru, bsdimp (basic approach)
MFC after: 1 week
|
|
|
|
| |
OK-ed by: sam
|
|
|
|
| |
system log when not in verbose logging mode.
|
| |
|
|
|
|
| |
the 0.4.x versions of wpa_supplicant.
|
|
|
|
|
| |
RTM_IFINFO message, in case some were posted before ndis_events
was run. This keeps us in sync with wpa_supplicant.
|
|
|
|
|
| |
seems to already be able to tell when it's associated and the extra
events just confuse it. Only forward media-specific events by default.
|
|
|
|
|
| |
This allows wpa_supplicant to work with WPA and WPA2 compliant NDIS
drivers.
|
|
|
|
|
|
|
|
| |
segfaults on amd64
o while here correct printf formats for size_t args
Identified by: Pascal Hofstee
MFC after: 3 days
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
that have at least 3 characters.
MFC after: 1 week
Thanks to: Music band ``Chingon''
for keeping me company while searching for these.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a card is ejected). wpa_supplicant requires that internal events
for interfaces coming+going include a name but after an interface
is removed you cannot use if_indextoname to map the interface index
in the RTM_IFINFO (or RTM_IFANNOUNCE) msg to an interface name.
Instead record the interface index in the driver-private data area
and use that to filter msgs from the routing socket. This insures
that when we have a message to process we know the interface name.
The end result is that we can now dispatch an "interface removed"
event that is understood when notified than an interface went away
(where previously the event dispatched was ignored because the
interface name was unrecognized).
This change also insures we only process events for our interface.
The only downside is that we can no longer wait for an interface
to arrive as we need to map the interface name to an index at
startup. This is not important as wpa_supplicant should be launched
by devd and not include a separate mechanism for doing interface
discovery.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|