DGNum/hostapd
6
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions
hostapd/wpa_supplicant/notify.c

822 lines
19 KiB
C
Raw Normal View History

Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
/*
* wpa_supplicant - Event notifications
Add suspend/resume notifications wpa_supplicant can now be notified of suspend/resume events, e.g., from pm-action scripts. This allows wpa_supplicant to clear information that may become invalid during a suspend operation.
2010-02-27 17:46:02 +01:00
* Copyright (c) 2009-2010, Jouni Malinen <j@w1.fi>
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
*
Remove the GPL notification from files contributed by Jouni Malinen Remove the GPL notification text from the files that were initially contributed by myself. Signed-hostap: Jouni Malinen <j@w1.fi>
2012-02-11 15:46:35 +01:00
* This software may be distributed under the terms of the BSD license.
* See README for more details.
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
*/
Add ctrl_iface events for BSS added/removed
2009-12-27 23:42:51 +01:00
#include "utils/includes.h"
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
Add ctrl_iface events for BSS added/removed
2009-12-27 23:42:51 +01:00
#include "utils/common.h"
#include "common/wpa_ctrl.h"
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
#include "config.h"
#include "wpa_supplicant_i.h"
#include "wps_supplicant.h"
dbus: Share common initialization code for both old and new interface This was mostly identical code that had been copied for the new D-Bus API implementation and as such, should really have been shared from the beginning. In addition, the copied code ended up generating interesting stack traces since the actual D-Bus connection was being shared even though the pointer to it was stored in two distinct data structures. The old D-Bus code ended up dispatching some D-Bus callbacks which ended up running the new D-Bus code. Since the private context pointers were mostly identical, everything seemed to more or less work, but this design was just making things more complex and potentially very easy to break.
2009-12-30 23:15:56 +01:00
#include "dbus/dbus_common.h"
dbus: Rename old D-Bus API files to include "_old" This makes it easier to figure out which file is used by which D-Bus interface.
2009-12-31 20:55:32 +01:00
#include "dbus/dbus_old.h"
dbus: Fix build with "ctrl_iface_" prefix removed
2009-12-20 20:34:56 +01:00
#include "dbus/dbus_new.h"
Flush PMKSA cache entries and invalidate EAP state on network changes If a network configuration block is removed or modified, flush all PMKSA cache entries that were created using that network configuration. Similarly, invalidate EAP state (fast re-auth). The special case for OKC on wpa_supplicant reconfiguration (network_ctx pointer change) is now addressed as part of the PMKSA cache flushing, so it does not need a separate mechanism for clearing the network_ctx values in the PMKSA cache.
2011-09-07 16:46:00 +02:00
#include "rsn_supp/wpa.h"
FST: Integration into wpa_supplicant This commit integrates the FST into the wpa_supplicant. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
2014-11-16 16:28:53 +01:00
#include "fst/fst.h"
Add suspend/resume notifications wpa_supplicant can now be notified of suspend/resume events, e.g., from pm-action scripts. This allows wpa_supplicant to clear information that may become invalid during a suspend operation.
2010-02-27 17:46:02 +01:00
#include "driver_i.h"
#include "scan.h"
P2P: Add support for cross connection If enabled, cross connection allows GO to forward IPv4 packets using masquerading NAT from the P2P clients in the group to an uplink WLAN connection. This is disabled by default and can be enabled with "wpa_cli p2p_set cross_connect 1" on the P2P device interface.
2010-07-10 19:19:34 +02:00
#include "p2p_supplicant.h"
SME: Add timers for authentication and asscoiation mac80211 authentication or association operation may get stuck for some reasons, so wpa_supplicant better use an internal timer to recover from this. Signed-off-by: Ben Greear <greearb@candelatech.com>
2011-02-24 15:59:46 +01:00
#include "sme.h"
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
#include "notify.h"
wpa_supplicant and dbus code separation This patch completely separates supplicant's code from dbus. It introduces three new notifications which copes with all remaining dbus stuff. wpas_notify_unregister_interface() was renamed to wpas_notify_iface_removed().
2009-10-15 20:15:10 +02:00
int wpas_notify_supplicant_initialized(struct wpa_global *global)
{
dbus: Share common initialization code for both old and new interface This was mostly identical code that had been copied for the new D-Bus API implementation and as such, should really have been shared from the beginning. In addition, the copied code ended up generating interesting stack traces since the actual D-Bus connection was being shared even though the pointer to it was stored in two distinct data structures. The old D-Bus code ended up dispatching some D-Bus callbacks which ended up running the new D-Bus code. Since the private context pointers were mostly identical, everything seemed to more or less work, but this design was just making things more complex and potentially very easy to break.
2009-12-30 23:15:56 +01:00
#ifdef CONFIG_DBUS
wpa_supplicant and dbus code separation This patch completely separates supplicant's code from dbus. It introduces three new notifications which copes with all remaining dbus stuff. wpas_notify_unregister_interface() was renamed to wpas_notify_iface_removed().
2009-10-15 20:15:10 +02:00
if (global->params.dbus_ctrl_interface) {
dbus: Share common initialization code for both old and new interface This was mostly identical code that had been copied for the new D-Bus API implementation and as such, should really have been shared from the beginning. In addition, the copied code ended up generating interesting stack traces since the actual D-Bus connection was being shared even though the pointer to it was stored in two distinct data structures. The old D-Bus code ended up dispatching some D-Bus callbacks which ended up running the new D-Bus code. Since the private context pointers were mostly identical, everything seemed to more or less work, but this design was just making things more complex and potentially very easy to break.
2009-12-30 23:15:56 +01:00
global->dbus = wpas_dbus_init(global);
if (global->dbus == NULL)
dbus: switch dbus APIs initialization order Initialize the new DBus API before the old one, so new applications which can use both, the old and the new API will be notified first that new API is available.
2009-12-03 20:17:49 +01:00
return -1;
wpa_supplicant and dbus code separation This patch completely separates supplicant's code from dbus. It introduces three new notifications which copes with all remaining dbus stuff. wpas_notify_unregister_interface() was renamed to wpas_notify_iface_removed().
2009-10-15 20:15:10 +02:00
}
dbus: Share common initialization code for both old and new interface This was mostly identical code that had been copied for the new D-Bus API implementation and as such, should really have been shared from the beginning. In addition, the copied code ended up generating interesting stack traces since the actual D-Bus connection was being shared even though the pointer to it was stored in two distinct data structures. The old D-Bus code ended up dispatching some D-Bus callbacks which ended up running the new D-Bus code. Since the private context pointers were mostly identical, everything seemed to more or less work, but this design was just making things more complex and potentially very easy to break.
2009-12-30 23:15:56 +01:00
#endif /* CONFIG_DBUS */
wpa_supplicant and dbus code separation This patch completely separates supplicant's code from dbus. It introduces three new notifications which copes with all remaining dbus stuff. wpas_notify_unregister_interface() was renamed to wpas_notify_iface_removed().
2009-10-15 20:15:10 +02:00
return 0;
}
void wpas_notify_supplicant_deinitialized(struct wpa_global *global)
{
dbus: Share common initialization code for both old and new interface This was mostly identical code that had been copied for the new D-Bus API implementation and as such, should really have been shared from the beginning. In addition, the copied code ended up generating interesting stack traces since the actual D-Bus connection was being shared even though the pointer to it was stored in two distinct data structures. The old D-Bus code ended up dispatching some D-Bus callbacks which ended up running the new D-Bus code. Since the private context pointers were mostly identical, everything seemed to more or less work, but this design was just making things more complex and potentially very easy to break.
2009-12-30 23:15:56 +01:00
#ifdef CONFIG_DBUS
if (global->dbus)
wpas_dbus_deinit(global->dbus);
#endif /* CONFIG_DBUS */
wpa_supplicant and dbus code separation This patch completely separates supplicant's code from dbus. It introduces three new notifications which copes with all remaining dbus stuff. wpas_notify_unregister_interface() was renamed to wpas_notify_iface_removed().
2009-10-15 20:15:10 +02:00
}
int wpas_notify_iface_added(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return 0;
wpa_supplicant and dbus code separation This patch completely separates supplicant's code from dbus. It introduces three new notifications which copes with all remaining dbus stuff. wpas_notify_unregister_interface() was renamed to wpas_notify_iface_removed().
2009-10-15 20:15:10 +02:00
if (wpas_dbus_register_iface(wpa_s))
return -1;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
if (wpas_dbus_register_interface(wpa_s))
wpa_supplicant: new DBus API implementation This patch implements the new DBus API. Both, the new and the previous API may work concurrently and may be turned on or off separately in .config file. Some features of the new API are: - more wpa_supplicant's events are signaled with DBus signals, - introspection data (requires libxml2 and may be disabled), - CurrentBSS and CurrentNetwork properties, - PropertyChanged signal for most of properties, - Relatively easy to extend. .config options for the new API are: CONFIG_CTRL_IFACE_DBUS_NEW=y and CONFIG_CTRL_IFACE_DBUS_INTRO=y for introspection. This commit misses couple of parts from the full implementation (these are still under review): - fetching all configuration parameters for learning WPS information - scan result BSS add/remove notification (register_bss() and unregister_bss() notification callbacks)
2009-11-09 22:51:59 +01:00
return -1;
wpa_supplicant and dbus code separation This patch completely separates supplicant's code from dbus. It introduces three new notifications which copes with all remaining dbus stuff. wpas_notify_unregister_interface() was renamed to wpas_notify_iface_removed().
2009-10-15 20:15:10 +02:00
return 0;
}
void wpas_notify_iface_removed(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
wpa_supplicant and dbus code separation This patch completely separates supplicant's code from dbus. It introduces three new notifications which copes with all remaining dbus stuff. wpas_notify_unregister_interface() was renamed to wpas_notify_iface_removed().
2009-10-15 20:15:10 +02:00
/* unregister interface in old DBus ctrl iface */
wpas_dbus_unregister_iface(wpa_s);
wpa_supplicant: new DBus API implementation This patch implements the new DBus API. Both, the new and the previous API may work concurrently and may be turned on or off separately in .config file. Some features of the new API are: - more wpa_supplicant's events are signaled with DBus signals, - introspection data (requires libxml2 and may be disabled), - CurrentBSS and CurrentNetwork properties, - PropertyChanged signal for most of properties, - Relatively easy to extend. .config options for the new API are: CONFIG_CTRL_IFACE_DBUS_NEW=y and CONFIG_CTRL_IFACE_DBUS_INTRO=y for introspection. This commit misses couple of parts from the full implementation (these are still under review): - fetching all configuration parameters for learning WPS information - scan result BSS add/remove notification (register_bss() and unregister_bss() notification callbacks)
2009-11-09 22:51:59 +01:00
/* unregister interface in new DBus ctrl iface */
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_unregister_interface(wpa_s);
wpa_supplicant and dbus code separation This patch completely separates supplicant's code from dbus. It introduces three new notifications which copes with all remaining dbus stuff. wpas_notify_unregister_interface() was renamed to wpas_notify_iface_removed().
2009-10-15 20:15:10 +02:00
}
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
void wpas_notify_state_changed(struct wpa_supplicant *wpa_s,
Get rid of unnecessary typedefs for enums.
2009-12-26 09:35:08 +01:00
enum wpa_states new_state,
enum wpa_states old_state)
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
/* notify the old DBus API */
wpa_supplicant_dbus_notify_state_change(wpa_s, new_state,
old_state);
wpa_supplicant: new DBus API implementation This patch implements the new DBus API. Both, the new and the previous API may work concurrently and may be turned on or off separately in .config file. Some features of the new API are: - more wpa_supplicant's events are signaled with DBus signals, - introspection data (requires libxml2 and may be disabled), - CurrentBSS and CurrentNetwork properties, - PropertyChanged signal for most of properties, - Relatively easy to extend. .config options for the new API are: CONFIG_CTRL_IFACE_DBUS_NEW=y and CONFIG_CTRL_IFACE_DBUS_INTRO=y for introspection. This commit misses couple of parts from the full implementation (these are still under review): - fetching all configuration parameters for learning WPS information - scan result BSS add/remove notification (register_bss() and unregister_bss() notification callbacks)
2009-11-09 22:51:59 +01:00
/* notify the new DBus API */
dbus: Replace StateChanged with PropertiesChanged signal The actual supplicant state is exposed via a property on the interface object. So having a separate signal StateChanged for notifying about changes is a bad idea. The standard PropertiesChanged signal should be used for this. The advantage of StateChanged signal was that it includes the previous state, but not even NetworkManager is making use of this. And tracking the old state via the property and this signal is easily possible anyway.
2010-01-04 15:33:44 +01:00
wpas_dbus_signal_prop_changed(wpa_s, WPAS_DBUS_PROP_STATE);
P2P: Add support for cross connection If enabled, cross connection allows GO to forward IPv4 packets using masquerading NAT from the P2P clients in the group to an uplink WLAN connection. This is disabled by default and can be enabled with "wpa_cli p2p_set cross_connect 1" on the P2P device interface.
2010-07-10 19:19:34 +02:00
FST: Integration into wpa_supplicant This commit integrates the FST into the wpa_supplicant. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
2014-11-16 16:28:53 +01:00
#ifdef CONFIG_FST
if (wpa_s->fst && !is_zero_ether_addr(wpa_s->bssid)) {
if (new_state == WPA_COMPLETED)
fst_notify_peer_connected(wpa_s->fst, wpa_s->bssid);
else if (old_state >= WPA_ASSOCIATED &&
new_state < WPA_ASSOCIATED)
fst_notify_peer_disconnected(wpa_s->fst, wpa_s->bssid);
}
#endif /* CONFIG_FST */
P2P: Add support for cross connection If enabled, cross connection allows GO to forward IPv4 packets using masquerading NAT from the P2P clients in the group to an uplink WLAN connection. This is disabled by default and can be enabled with "wpa_cli p2p_set cross_connect 1" on the P2P device interface.
2010-07-10 19:19:34 +02:00
if (new_state == WPA_COMPLETED)
wpas_p2p_notif_connected(wpa_s);
P2P: Notify about disconnection only when needed wpas_notify_state_changed() notified about disconnection when new_state < WPA_ASSOCIATED, without checking the old state. This results in extra processing which can be avoided by checking that old_state was connected. Signed-hostap: Eliad Peller <eliad@wizery.com> intended-for: hostap-1
2012-04-01 20:49:03 +02:00
else if (old_state >= WPA_ASSOCIATED && new_state < WPA_ASSOCIATED)
P2P: Add support for cross connection If enabled, cross connection allows GO to forward IPv4 packets using masquerading NAT from the P2P clients in the group to an uplink WLAN connection. This is disabled by default and can be enabled with "wpa_cli p2p_set cross_connect 1" on the P2P device interface.
2010-07-10 19:19:34 +02:00
wpas_p2p_notif_disconnected(wpa_s);
SME: Add timers for authentication and asscoiation mac80211 authentication or association operation may get stuck for some reasons, so wpa_supplicant better use an internal timer to recover from this. Signed-off-by: Ben Greear <greearb@candelatech.com>
2011-02-24 15:59:46 +01:00
sme_state_changed(wpa_s);
Add wpa_supplicant state change event for Android network manager Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
2011-02-26 12:20:16 +01:00
#ifdef ANDROID
wpa_msg_ctrl(wpa_s, MSG_INFO, WPA_EVENT_STATE_CHANGE
Android: Add SSID in supplicant change event In addition, change wpa_s->pending_bssid to wpa_s->bssid for the BSSID value in the event. Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
2013-11-11 21:25:17 +01:00
"id=%d state=%d BSSID=" MACSTR " SSID=%s",
Add wpa_supplicant state change event for Android network manager Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
2011-02-26 12:20:16 +01:00
wpa_s->current_ssid ? wpa_s->current_ssid->id : -1,
Android: Add SSID in supplicant change event In addition, change wpa_s->pending_bssid to wpa_s->bssid for the BSSID value in the event. Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
2013-11-11 21:25:17 +01:00
new_state,
MAC2STR(wpa_s->bssid),
wpa_s->current_ssid && wpa_s->current_ssid->ssid ?
wpa_ssid_txt(wpa_s->current_ssid->ssid,
wpa_s->current_ssid->ssid_len) : "");
Add wpa_supplicant state change event for Android network manager Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
2011-02-26 12:20:16 +01:00
#endif /* ANDROID */
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
Export disconnect reason code to dbus In the properties changed signal, added a new property "DisconnectReason", which carries the IEEE 802.11 reason code of the most recent disassociation or deauthentication event. The reason code is negative if it is locally generated. The property is sent to the DBUS immediately so as to prevent it from being coalesced with other disconnect events. Signed-off-by: Gary Morain <gmorain@chromium.org>
2012-06-30 15:43:50 +02:00
void wpas_notify_disconnect_reason(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
Export disconnect reason code to dbus In the properties changed signal, added a new property "DisconnectReason", which carries the IEEE 802.11 reason code of the most recent disassociation or deauthentication event. The reason code is negative if it is locally generated. The property is sent to the DBUS immediately so as to prevent it from being coalesced with other disconnect events. Signed-off-by: Gary Morain <gmorain@chromium.org>
2012-06-30 15:43:50 +02:00
wpas_dbus_signal_prop_changed(wpa_s, WPAS_DBUS_PROP_DISCONNECT_REASON);
}
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
void wpas_notify_network_changed(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_prop_changed(wpa_s, WPAS_DBUS_PROP_CURRENT_NETWORK);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
void wpas_notify_ap_scan_changed(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_prop_changed(wpa_s, WPAS_DBUS_PROP_AP_SCAN);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
void wpas_notify_bssid_changed(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_prop_changed(wpa_s, WPAS_DBUS_PROP_CURRENT_BSS);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
Add DBus state change notification for AuthMode property Signed-off-by: Paul Stewart <pstew@google.com>
2011-03-15 12:54:59 +01:00
void wpas_notify_auth_changed(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
Add DBus state change notification for AuthMode property Signed-off-by: Paul Stewart <pstew@google.com>
2011-03-15 12:54:59 +01:00
wpas_dbus_signal_prop_changed(wpa_s, WPAS_DBUS_PROP_CURRENT_AUTH_MODE);
}
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
void wpas_notify_network_enabled_changed(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_network_enabled_changed(wpa_s, ssid);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
void wpas_notify_network_selected(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_network_selected(wpa_s, ssid->id);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
dbus: Implement EAP SM control request signals Add a D-Bus signal for EAP SM requests. This signal is emitted on the Interface object so that clients only have to listen to one object for requests rather than to all network objects. This signal is analogous to the socket control interface's CTRL-REQ- request. Signed-off-by: Dan Williams <dcbw@redhat.com>
2011-10-24 18:03:04 +02:00
void wpas_notify_network_request(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid,
enum wpa_ctrl_req_type rtype,
const char *default_txt)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Implement EAP SM control request signals Add a D-Bus signal for EAP SM requests. This signal is emitted on the Interface object so that clients only have to listen to one object for requests rather than to all network objects. This signal is analogous to the socket control interface's CTRL-REQ- request. Signed-off-by: Dan Williams <dcbw@redhat.com>
2011-10-24 18:03:04 +02:00
wpas_dbus_signal_network_request(wpa_s, ssid, rtype, default_txt);
}
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
void wpas_notify_scanning(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
/* notify the old DBus API */
wpa_supplicant_dbus_notify_scanning(wpa_s);
dbus: Replace StateChanged with PropertiesChanged signal The actual supplicant state is exposed via a property on the interface object. So having a separate signal StateChanged for notifying about changes is a bad idea. The standard PropertiesChanged signal should be used for this. The advantage of StateChanged signal was that it includes the previous state, but not even NetworkManager is making use of this. And tracking the old state via the property and this signal is easily possible anyway.
2010-01-04 15:33:44 +01:00
wpa_supplicant: new DBus API implementation This patch implements the new DBus API. Both, the new and the previous API may work concurrently and may be turned on or off separately in .config file. Some features of the new API are: - more wpa_supplicant's events are signaled with DBus signals, - introspection data (requires libxml2 and may be disabled), - CurrentBSS and CurrentNetwork properties, - PropertyChanged signal for most of properties, - Relatively easy to extend. .config options for the new API are: CONFIG_CTRL_IFACE_DBUS_NEW=y and CONFIG_CTRL_IFACE_DBUS_INTRO=y for introspection. This commit misses couple of parts from the full implementation (these are still under review): - fetching all configuration parameters for learning WPS information - scan result BSS add/remove notification (register_bss() and unregister_bss() notification callbacks)
2009-11-09 22:51:59 +01:00
/* notify the new DBus API */
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_prop_changed(wpa_s, WPAS_DBUS_PROP_SCANNING);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
void wpas_notify_scan_done(struct wpa_supplicant *wpa_s, int success)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_scan_done(wpa_s, success);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
void wpas_notify_scan_results(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
/* notify the old DBus API */
wpa_supplicant_dbus_notify_scan_results(wpa_s);
wpas_wps_notify_scan_results(wpa_s);
}
void wpas_notify_wps_credential(struct wpa_supplicant *wpa_s,
const struct wps_credential *cred)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
Fix non-WPS build
2009-11-10 10:35:25 +01:00
#ifdef CONFIG_WPS
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
/* notify the old DBus API */
wpa_supplicant_dbus_notify_wps_cred(wpa_s, cred);
wpa_supplicant: new DBus API implementation This patch implements the new DBus API. Both, the new and the previous API may work concurrently and may be turned on or off separately in .config file. Some features of the new API are: - more wpa_supplicant's events are signaled with DBus signals, - introspection data (requires libxml2 and may be disabled), - CurrentBSS and CurrentNetwork properties, - PropertyChanged signal for most of properties, - Relatively easy to extend. .config options for the new API are: CONFIG_CTRL_IFACE_DBUS_NEW=y and CONFIG_CTRL_IFACE_DBUS_INTRO=y for introspection. This commit misses couple of parts from the full implementation (these are still under review): - fetching all configuration parameters for learning WPS information - scan result BSS add/remove notification (register_bss() and unregister_bss() notification callbacks)
2009-11-09 22:51:59 +01:00
/* notify the new DBus API */
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_wps_cred(wpa_s, cred);
Fix non-WPS build
2009-11-10 10:35:25 +01:00
#endif /* CONFIG_WPS */
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
void wpas_notify_wps_event_m2d(struct wpa_supplicant *wpa_s,
struct wps_event_m2d *m2d)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
Fix non-WPS build
2009-11-10 10:35:25 +01:00
#ifdef CONFIG_WPS
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_wps_event_m2d(wpa_s, m2d);
Fix non-WPS build
2009-11-10 10:35:25 +01:00
#endif /* CONFIG_WPS */
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
void wpas_notify_wps_event_fail(struct wpa_supplicant *wpa_s,
struct wps_event_fail *fail)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
Fix non-WPS build
2009-11-10 10:35:25 +01:00
#ifdef CONFIG_WPS
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_wps_event_fail(wpa_s, fail);
Fix non-WPS build
2009-11-10 10:35:25 +01:00
#endif /* CONFIG_WPS */
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
void wpas_notify_wps_event_success(struct wpa_supplicant *wpa_s)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
Fix non-WPS build
2009-11-10 10:35:25 +01:00
#ifdef CONFIG_WPS
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_wps_event_success(wpa_s);
Fix non-WPS build
2009-11-10 10:35:25 +01:00
#endif /* CONFIG_WPS */
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
D-Bus: Add WPS pbc-overlap Event This sends an Event D-Bus signal with name "pbc-overlap" for WPS-EVENT-OVERLAP. Signed-off-by: Avichal Agarwal <avichal.a@samsung.com>
2015-06-05 14:46:51 +02:00
void wpas_notify_wps_event_pbc_overlap(struct wpa_supplicant *wpa_s)
{
if (wpa_s->p2p_mgmt)
return;
#ifdef CONFIG_WPS
wpas_dbus_signal_wps_event_pbc_overlap(wpa_s);
#endif /* CONFIG_WPS */
}
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
void wpas_notify_network_added(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
P2P: Update D-Bus network object semantics during group formation Do not emit network objects during P2P group formation since such network objects can confuse certain apps. Instead, a persistent group object is created to allow apps to keep track of persistent groups. Persistent group objects only represent the info needed to recreate the group. Also fixes a minor bug in the handling of persistent group objects during WPS operations. Signed-off-by: Jayant Sane <jayant.sane@intel.com>
2011-06-23 20:25:13 +02:00
/*
* Networks objects created during any P2P activities should not be
* exposed out. They might/will confuse certain non-P2P aware
* applications since these network objects won't behave like
* regular ones.
*/
D-Bus: Do not send network notification for all P2P groups Previously, network added event was skipping during group formation. However, this did not necessarily catch all cases of temporary P2P network blocks. Check ssid->p2p_group to make this behavior more consistent by avoiding all P2P groups. Signed-hostap: Jouni Malinen <j@w1.fi>
2013-08-31 15:44:42 +02:00
if (!ssid->p2p_group && wpa_s->global->p2p_group_formation != wpa_s)
P2P: Update D-Bus network object semantics during group formation Do not emit network objects during P2P group formation since such network objects can confuse certain apps. Instead, a persistent group object is created to allow apps to keep track of persistent groups. Persistent group objects only represent the info needed to recreate the group. Also fixes a minor bug in the handling of persistent group objects during WPS operations. Signed-off-by: Jayant Sane <jayant.sane@intel.com>
2011-06-23 20:25:13 +02:00
wpas_dbus_register_network(wpa_s, ssid);
}
void wpas_notify_persistent_group_added(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid)
{
Fix D-Bus build without CONFIG_P2P=y
2011-06-27 20:23:22 +02:00
#ifdef CONFIG_P2P
P2P: Update D-Bus network object semantics during group formation Do not emit network objects during P2P group formation since such network objects can confuse certain apps. Instead, a persistent group object is created to allow apps to keep track of persistent groups. Persistent group objects only represent the info needed to recreate the group. Also fixes a minor bug in the handling of persistent group objects during WPS operations. Signed-off-by: Jayant Sane <jayant.sane@intel.com>
2011-06-23 20:25:13 +02:00
wpas_dbus_register_persistent_group(wpa_s, ssid);
Fix D-Bus build without CONFIG_P2P=y
2011-06-27 20:23:22 +02:00
#endif /* CONFIG_P2P */
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
P2P: More complete persistent group management over D-Bus Extend commit c2762e410fa319f75a174aeb12343beddf99fce4 to allow applications to manage (add/remove) persistent groups and accepted network object paths while invoking a persistent group.
2011-06-24 10:20:19 +02:00
void wpas_notify_persistent_group_removed(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid)
{
Fix D-Bus build without CONFIG_P2P=y
2011-06-27 20:23:22 +02:00
#ifdef CONFIG_P2P
P2P: More complete persistent group management over D-Bus Extend commit c2762e410fa319f75a174aeb12343beddf99fce4 to allow applications to manage (add/remove) persistent groups and accepted network object paths while invoking a persistent group.
2011-06-24 10:20:19 +02:00
wpas_dbus_unregister_persistent_group(wpa_s, ssid->id);
Fix D-Bus build without CONFIG_P2P=y
2011-06-27 20:23:22 +02:00
#endif /* CONFIG_P2P */
P2P: More complete persistent group management over D-Bus Extend commit c2762e410fa319f75a174aeb12343beddf99fce4 to allow applications to manage (add/remove) persistent groups and accepted network object paths while invoking a persistent group.
2011-06-24 10:20:19 +02:00
}
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
void wpas_notify_network_removed(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid)
{
Interworking: Prefer last added network during network selection Previously, any network block could be used to select the BSS to connect to when processing scan results after Interworking network selection. This can result in somewhat unexpected network selection in cases where credential preferences indicated that a specific network was selected, but another network ended up getting used for the connection. While the older networks continue to be valid, add special processing for this initial post-interworking-connect case to get more consistent network selection to match with the Interworking network selection result. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
2014-02-25 21:37:57 +01:00
if (wpa_s->next_ssid == ssid)
wpa_s->next_ssid = NULL;
Fix segfault on error path if driver initialization fails wpa_s->wpa is NULL in this case and we better not call WPA state machine functions.
2011-10-20 20:10:22 +02:00
if (wpa_s->wpa)
wpa_sm_pmksa_cache_flush(wpa_s->wpa, ssid);
Fix wpas_notify_network_removed() Commit bb3df9a569e4a33445c89ebc50019ba46b4f6704 ('notify: Do not raise any signal from a P2P management interface') was supposed to only change D-Bus behavior, but it ended up disabling non-D-Bus functionality as well for some sequences where the P2P Device interface is used. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
2015-04-29 19:47:14 +02:00
if (!ssid->p2p_group && wpa_s->global->p2p_group_formation != wpa_s &&
!wpa_s->p2p_mgmt)
P2P: Update D-Bus network object semantics during group formation Do not emit network objects during P2P group formation since such network objects can confuse certain apps. Instead, a persistent group object is created to allow apps to keep track of persistent groups. Persistent group objects only represent the info needed to recreate the group. Also fixes a minor bug in the handling of persistent group objects during WPS operations. Signed-off-by: Jayant Sane <jayant.sane@intel.com>
2011-06-23 20:25:13 +02:00
wpas_dbus_unregister_network(wpa_s, ssid->id);
D-Bus: Fix P2P persistent group removal from non-D-Bus triggers It is possible for the persistent group object to be added and removed by non-D-Bus triggers (e.g., ctrl_iface commands). The add part was already handled, but removal was not. That resulted in memory leaks when a P2P persistent group was removed without using an explicit D-Bus command for this even if the object was added without D-Bus involvement. Signed-off-by: Jouni Malinen <j@w1.fi>
2014-12-27 20:00:11 +01:00
if (network_is_persistent_group(ssid))
wpas_notify_persistent_group_removed(wpa_s, ssid);
P2P: Clean up group formation on network block removal If a P2P group network block is removed for any reason (e.g., wps_cancel command) while the interface is in group formation, remove the group formation timeout and indicate failure immediately. Previously, this type of operations could end up leaving the timeout running and result in somewhat unexpected group formation failure events later. Signed-hostap: Jouni Malinen <j@w1.fi>
2011-12-10 11:56:42 +01:00
wpas_p2p_network_removed(wpa_s, ssid);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
Add notifications for scan result BSS changes (added/removed) If scan results introduce new BSSs or discards some previously known, new wpas_notify_bss_added or wpas_notify_bss_removed notifications are called.
2009-11-11 16:07:53 +01:00
void wpas_notify_bss_added(struct wpa_supplicant *wpa_s,
Add ctrl_iface events for BSS added/removed
2009-12-27 23:42:51 +01:00
u8 bssid[], unsigned int id)
Add notifications for scan result BSS changes (added/removed) If scan results introduce new BSSs or discards some previously known, new wpas_notify_bss_added or wpas_notify_bss_removed notifications are called.
2009-11-11 16:07:53 +01:00
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_register_bss(wpa_s, bssid, id);
Add ctrl_iface events for BSS added/removed
2009-12-27 23:42:51 +01:00
wpa_msg_ctrl(wpa_s, MSG_INFO, WPA_EVENT_BSS_ADDED "%u " MACSTR,
id, MAC2STR(bssid));
Add notifications for scan result BSS changes (added/removed) If scan results introduce new BSSs or discards some previously known, new wpas_notify_bss_added or wpas_notify_bss_removed notifications are called.
2009-11-11 16:07:53 +01:00
}
void wpas_notify_bss_removed(struct wpa_supplicant *wpa_s,
Add ctrl_iface events for BSS added/removed
2009-12-27 23:42:51 +01:00
u8 bssid[], unsigned int id)
Add notifications for scan result BSS changes (added/removed) If scan results introduce new BSSs or discards some previously known, new wpas_notify_bss_added or wpas_notify_bss_removed notifications are called.
2009-11-11 16:07:53 +01:00
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_unregister_bss(wpa_s, bssid, id);
Add ctrl_iface events for BSS added/removed
2009-12-27 23:42:51 +01:00
wpa_msg_ctrl(wpa_s, MSG_INFO, WPA_EVENT_BSS_REMOVED "%u " MACSTR,
id, MAC2STR(bssid));
Add notifications for scan result BSS changes (added/removed) If scan results introduce new BSSs or discards some previously known, new wpas_notify_bss_added or wpas_notify_bss_removed notifications are called.
2009-11-11 16:07:53 +01:00
}
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
void wpas_notify_bss_freq_changed(struct wpa_supplicant *wpa_s,
unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_FREQ, id);
}
void wpas_notify_bss_signal_changed(struct wpa_supplicant *wpa_s,
unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_SIGNAL,
id);
}
void wpas_notify_bss_privacy_changed(struct wpa_supplicant *wpa_s,
unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_PRIVACY,
id);
}
void wpas_notify_bss_mode_changed(struct wpa_supplicant *wpa_s,
unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_MODE, id);
}
void wpas_notify_bss_wpaie_changed(struct wpa_supplicant *wpa_s,
unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Change WPA/RSNIE byte array props to dicts Expose RSN and WPA properties for BSS objects containing information about key management and cipher suites. Get rid of WPA/RSN/WPSIE byte array properties and add IEs byte array property with all IE data instead.
2010-01-16 15:37:37 +01:00
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_WPA, id);
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
}
void wpas_notify_bss_rsnie_changed(struct wpa_supplicant *wpa_s,
unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Change WPA/RSNIE byte array props to dicts Expose RSN and WPA properties for BSS objects containing information about key management and cipher suites. Get rid of WPA/RSN/WPSIE byte array properties and add IEs byte array property with all IE data instead.
2010-01-16 15:37:37 +01:00
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_RSN, id);
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
}
void wpas_notify_bss_wps_changed(struct wpa_supplicant *wpa_s,
dbus: Change WPA/RSNIE byte array props to dicts Expose RSN and WPA properties for BSS objects containing information about key management and cipher suites. Get rid of WPA/RSN/WPSIE byte array properties and add IEs byte array property with all IE data instead.
2010-01-16 15:37:37 +01:00
unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Add getter for WPS properties Add "WPS" property to the DBus interface that allows to identify the active WPS method of a BSS. Signed-hostap: Sven Neumann <s.neumann@raumfeld.com>
2012-11-03 17:37:20 +01:00
#ifdef CONFIG_WPS
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_WPS, id);
#endif /* CONFIG_WPS */
dbus: Change WPA/RSNIE byte array props to dicts Expose RSN and WPA properties for BSS objects containing information about key management and cipher suites. Get rid of WPA/RSN/WPSIE byte array properties and add IEs byte array property with all IE data instead.
2010-01-16 15:37:37 +01:00
}
void wpas_notify_bss_ies_changed(struct wpa_supplicant *wpa_s,
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Change WPA/RSNIE byte array props to dicts Expose RSN and WPA properties for BSS objects containing information about key management and cipher suites. Get rid of WPA/RSN/WPSIE byte array properties and add IEs byte array property with all IE data instead.
2010-01-16 15:37:37 +01:00
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_IES, id);
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
}
void wpas_notify_bss_rates_changed(struct wpa_supplicant *wpa_s,
unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Add BSS property change notifications
2010-01-06 19:03:01 +01:00
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_RATES, id);
}
dbus: add BSS Age property to indicate last-seen time "Age" is the age in seconds since the BSS was last seen, and is emitted as a PropertyChanged signal whenever the BSS is updated from a scan result. It also returns the correct age when queried directly. This property can be used to resolve issues where, if no other properties of the BSS changed from scan results (for example, if the BSS always had 100% signal) no D-Bus signals would be emitted to indicate that the BSS had just been seen in the scan. Signed-hostap: Dan Williams <dcbw@redhat.com>
2014-09-04 20:10:54 +02:00
void wpas_notify_bss_seen(struct wpa_supplicant *wpa_s, unsigned int id)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: add BSS Age property to indicate last-seen time "Age" is the age in seconds since the BSS was last seen, and is emitted as a PropertyChanged signal whenever the BSS is updated from a scan result. It also returns the correct age when queried directly. This property can be used to resolve issues where, if no other properties of the BSS changed from scan results (for example, if the BSS always had 100% signal) no D-Bus signals would be emitted to indicate that the BSS had just been seen in the scan. Signed-hostap: Dan Williams <dcbw@redhat.com>
2014-09-04 20:10:54 +02:00
wpas_dbus_bss_signal_prop_changed(wpa_s, WPAS_DBUS_BSS_PROP_AGE, id);
}
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
void wpas_notify_blob_added(struct wpa_supplicant *wpa_s, const char *name)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_blob_added(wpa_s, name);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
void wpas_notify_blob_removed(struct wpa_supplicant *wpa_s, const char *name)
{
notify: Do not raise any signal from a P2P management interface Such interface is not registered on DBus, thus there is no need to raise any signal from it. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-10-23 10:31:20 +02:00
if (wpa_s->p2p_mgmt)
return;
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_blob_removed(wpa_s, name);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
dbus: Divide DebugParams property to three separate properties
2010-01-01 12:00:22 +01:00
void wpas_notify_debug_level_changed(struct wpa_global *global)
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
{
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_debug_level_changed(global);
dbus: Divide DebugParams property to three separate properties
2010-01-01 12:00:22 +01:00
}
void wpas_notify_debug_timestamp_changed(struct wpa_global *global)
{
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_debug_timestamp_changed(global);
dbus: Divide DebugParams property to three separate properties
2010-01-01 12:00:22 +01:00
}
void wpas_notify_debug_show_keys_changed(struct wpa_global *global)
{
dbus: Remove wpas_dbus_callbacks abstraction This callback structure was specific to the new D-Bus API which makes it more or less pointless. It is just simpler to call the notification functions directly. More proper design could be to use a generic mechanism for registering notification callbacks into notify.c, but that is not yet available and should not be designed just based on a single user.
2010-01-01 17:45:29 +01:00
wpas_dbus_signal_debug_show_keys_changed(global);
Add wpa_supplicant notification calls This introduces a new mechanism for collecting notification calls into a single place (notify.c). As a result of this, most of the wpa_supplicant code does not need to know about dbus (etc. mechanisms that could use the notifications). Some empty placeholder functions are also added in preparation of new dbus code that needs more event notifications.
2009-09-13 19:53:32 +02:00
}
Add suspend/resume notifications wpa_supplicant can now be notified of suspend/resume events, e.g., from pm-action scripts. This allows wpa_supplicant to clear information that may become invalid during a suspend operation.
2010-02-27 17:46:02 +01:00
void wpas_notify_suspend(struct wpa_global *global)
{
struct wpa_supplicant *wpa_s;
os_get_time(&global->suspend_time);
wpa_printf(MSG_DEBUG, "System suspend notification");
for (wpa_s = global->ifaces; wpa_s; wpa_s = wpa_s->next)
wpa_drv_suspend(wpa_s);
}
void wpas_notify_resume(struct wpa_global *global)
{
struct os_time now;
int slept;
struct wpa_supplicant *wpa_s;
if (global->suspend_time.sec == 0)
slept = -1;
else {
os_get_time(&now);
slept = now.sec - global->suspend_time.sec;
}
wpa_printf(MSG_DEBUG, "System resume notification (slept %d seconds)",
slept);
for (wpa_s = global->ifaces; wpa_s; wpa_s = wpa_s->next) {
wpa_drv_resume(wpa_s);
if (wpa_s->wpa_state == WPA_DISCONNECTED)
wpa_supplicant_req_scan(wpa_s, 0, 100000);
}
}
P2P: Add notification for P2P device found Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:08:18 +01:00
#ifdef CONFIG_P2P
P2P: Add method to signal lost device This signal is used to notify users of the P2P state machine or wpa_supplicant of lost devices. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:22:16 +01:00
P2P: Add D-Bus FindStopped to notify P2P-FIND-STOPPED event Add D-Bus notification mechanism of P2P-FIND-STOPPED event on fi.w1.wpa_supplicant1.Interface.P2PDevice interface. Signed-off-by: Nishant Chaprana <n.chaprana@samsung.com>
2015-05-13 14:03:48 +02:00
void wpas_notify_p2p_find_stopped(struct wpa_supplicant *wpa_s)
{
/* Notify P2P find has stopped */
wpas_dbus_signal_p2p_find_stopped(wpa_s);
}
P2P: Add notification for P2P device found Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:08:18 +01:00
void wpas_notify_p2p_device_found(struct wpa_supplicant *wpa_s,
const u8 *dev_addr, int new_device)
{
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
if (new_device) {
/* Create the new peer object */
wpas_dbus_register_peer(wpa_s, dev_addr);
}
/* Notify a new peer has been detected*/
wpas_dbus_signal_peer_device_found(wpa_s, dev_addr);
P2P: Add notification for P2P device found Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:08:18 +01:00
}
P2P: Add method to signal lost device This signal is used to notify users of the P2P state machine or wpa_supplicant of lost devices. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:22:16 +01:00
void wpas_notify_p2p_device_lost(struct wpa_supplicant *wpa_s,
const u8 *dev_addr)
{
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
wpas_dbus_unregister_peer(wpa_s, dev_addr);
/* Create signal on interface object*/
wpas_dbus_signal_peer_device_lost(wpa_s, dev_addr);
P2P: Add method to signal lost device This signal is used to notify users of the P2P state machine or wpa_supplicant of lost devices. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:22:16 +01:00
}
P2P: Add group removed notification Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:27:23 +01:00
void wpas_notify_p2p_group_removed(struct wpa_supplicant *wpa_s,
const struct wpa_ssid *ssid,
const char *role)
{
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
wpas_dbus_signal_p2p_group_removed(wpa_s, role);
dbus: Declare and implement GroupFinished as for GroupStarted First for better concistancy but also to tell about the group_object that is getting removed, thus the client will know about it and will be able to act accordingly. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-07-08 14:56:11 +02:00
wpas_dbus_unregister_p2p_group(wpa_s, ssid);
P2P: Add group removed notification Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:27:23 +01:00
}
P2P: Add wpas_notify_p2p_go_neg_req Add a notification for received GO negotiation requests. Signed-off-by: Konguraj(Raj) Kulanthaivel <konguraj.kulanthaivel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:30:19 +01:00
void wpas_notify_p2p_go_neg_req(struct wpa_supplicant *wpa_s,
P2P: Add GO Intent of connecting device in GO Negotiation Request event Add GO Intent information of connecting device in GO Negotiation Request event which will help applications to decide its own GO intent value in advance and can avoid failure cases when both devices use GO Intent 15 depending on application requirement. Signed-off-by: Mayank Haarit <mayank.h@samsung.com>
2015-06-02 07:47:33 +02:00
const u8 *src, u16 dev_passwd_id, u8 go_intent)
P2P: Add wpas_notify_p2p_go_neg_req Add a notification for received GO negotiation requests. Signed-off-by: Konguraj(Raj) Kulanthaivel <konguraj.kulanthaivel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:30:19 +01:00
{
P2P: Add GO Intent of connecting device in GO Negotiation Request event Add GO Intent information of connecting device in GO Negotiation Request event which will help applications to decide its own GO intent value in advance and can avoid failure cases when both devices use GO Intent 15 depending on application requirement. Signed-off-by: Mayank Haarit <mayank.h@samsung.com>
2015-06-02 07:47:33 +02:00
wpas_dbus_signal_p2p_go_neg_req(wpa_s, src, dev_passwd_id, go_intent);
P2P: Add wpas_notify_p2p_go_neg_req Add a notification for received GO negotiation requests. Signed-off-by: Konguraj(Raj) Kulanthaivel <konguraj.kulanthaivel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:30:19 +01:00
}
P2P: Add GO negotiation status notification Signed-off-by: Jayant Sane <jayant.sane@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:34:52 +01:00
P2P: Make GO negotiation peer and group information available over D-Bus The GO negotiation response is very cryptic at the moment. For a success message we only know on which interface the negotiation succeeded, not which peer. For a failure we know the interface also and a status code (number). It will be very useful for clients to know upon receipt of such a message which peer the negotiation occurred with. Now that the peer information is available and the API is changed already, the function composing the D-Bus message might as well include all GO negotiation information. This is done with a dict to make things easier on clients if this result information changes down the line. Signed-hostap: Reinette Chatre <reinette.chatre@intel.com> Signed-hostap: Johannes Berg <johannes.berg@intel.com>
2011-12-18 15:52:33 +01:00
void wpas_notify_p2p_go_neg_completed(struct wpa_supplicant *wpa_s,
struct p2p_go_neg_results *res)
P2P: Add GO negotiation status notification Signed-off-by: Jayant Sane <jayant.sane@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:34:52 +01:00
{
P2P: Make GO negotiation peer and group information available over D-Bus The GO negotiation response is very cryptic at the moment. For a success message we only know on which interface the negotiation succeeded, not which peer. For a failure we know the interface also and a status code (number). It will be very useful for clients to know upon receipt of such a message which peer the negotiation occurred with. Now that the peer information is available and the API is changed already, the function composing the D-Bus message might as well include all GO negotiation information. This is done with a dict to make things easier on clients if this result information changes down the line. Signed-hostap: Reinette Chatre <reinette.chatre@intel.com> Signed-hostap: Johannes Berg <johannes.berg@intel.com>
2011-12-18 15:52:33 +01:00
wpas_dbus_signal_p2p_go_neg_resp(wpa_s, res);
P2P: Add GO negotiation status notification Signed-off-by: Jayant Sane <jayant.sane@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:34:52 +01:00
}
P2P: Add invitation result notification Add a notification function for the result of an invitation. Signed-off-by: Jean-Michel Bachot <jean-michelx.bachot@linux.intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:40:21 +01:00
void wpas_notify_p2p_invitation_result(struct wpa_supplicant *wpa_s,
int status, const u8 *bssid)
{
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
wpas_dbus_signal_p2p_invitation_result(wpa_s, status, bssid);
P2P: Add invitation result notification Add a notification function for the result of an invitation. Signed-off-by: Jean-Michel Bachot <jean-michelx.bachot@linux.intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:40:21 +01:00
}
P2P: Add wpas_notify_p2p_sd_request Signed-off-by: Konguraj(Raj) Kulanthaivel <konguraj.kulanthaivel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:45:39 +01:00
void wpas_notify_p2p_sd_request(struct wpa_supplicant *wpa_s,
int freq, const u8 *sa, u8 dialog_token,
u16 update_indic, const u8 *tlvs,
size_t tlvs_len)
{
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
wpas_dbus_signal_p2p_sd_request(wpa_s, freq, sa, dialog_token,
update_indic, tlvs, tlvs_len);
P2P: Add wpas_notify_p2p_sd_request Signed-off-by: Konguraj(Raj) Kulanthaivel <konguraj.kulanthaivel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:45:39 +01:00
}
P2P: Add wpas_notify_p2p_sd_response Signed-off-by: Konguraj(Raj) Kulanthaivel <konguraj.kulanthaivel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:47:34 +01:00
void wpas_notify_p2p_sd_response(struct wpa_supplicant *wpa_s,
const u8 *sa, u16 update_indic,
const u8 *tlvs, size_t tlvs_len)
{
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
wpas_dbus_signal_p2p_sd_response(wpa_s, sa, update_indic,
tlvs, tlvs_len);
P2P: Add wpas_notify_p2p_sd_response Signed-off-by: Konguraj(Raj) Kulanthaivel <konguraj.kulanthaivel@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:47:34 +01:00
}
P2P: Add wpas_notify_p2p_provision_discovery() Add a notification for P2P provision discovery status/result. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-12 23:31:56 +02:00
/**
* wpas_notify_p2p_provision_discovery - Notification of provision discovery
* @dev_addr: Who sent the request or responded to our request.
* @request: Will be 1 if request, 0 for response.
* @status: Valid only in case of response (0 in case of success)
* @config_methods: WPS config methods
* @generated_pin: PIN to be displayed in case of WPS_CONFIG_DISPLAY method
*
* This can be used to notify:
* - Requests or responses
* - Various config methods
* - Failure condition in case of response
*/
void wpas_notify_p2p_provision_discovery(struct wpa_supplicant *wpa_s,
const u8 *dev_addr, int request,
enum p2p_prov_disc_status status,
u16 config_methods,
unsigned int generated_pin)
{
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
wpas_dbus_signal_p2p_provision_discovery(wpa_s, dev_addr, request,
status, config_methods,
generated_pin);
P2P: Add wpas_notify_p2p_provision_discovery() Add a notification for P2P provision discovery status/result. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-12 23:31:56 +02:00
}
P2P: Add group started notification Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-12 23:35:37 +02:00
void wpas_notify_p2p_group_started(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid, int network_id,
int client)
{
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
/* Notify a group has been started */
wpas_dbus_register_p2p_group(wpa_s, ssid);
wpas_dbus_signal_p2p_group_started(wpa_s, ssid, client, network_id);
P2P: Add group started notification Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-12 23:35:37 +02:00
}
P2P: Add WpsFailed signal in P2P D-Bus Signal is triggered if an error occurs during WPS provisioning phase. Signed-off-by: Jean-Michel.Bachot <jean-michelx.bachot@intel.com> Signed-off-by: Jayant Sane <jayant.sane@intel.com>
2011-06-25 10:47:04 +02:00
P2P: Add D-Bus signal GroupFormationFailure This is similar to the control interface event P2P-GROUP-FORMATION-FAILURE. Signed-off-by: Nishant Chaprana <n.chaprana@samsung.com>
2015-08-20 12:58:33 +02:00
void wpas_notify_p2p_group_formation_failure(struct wpa_supplicant *wpa_s,
const char *reason)
{
/* Notify a group formation failed */
wpas_dbus_signal_p2p_group_formation_failure(wpa_s, reason);
}
P2P: Add WpsFailed signal in P2P D-Bus Signal is triggered if an error occurs during WPS provisioning phase. Signed-off-by: Jean-Michel.Bachot <jean-michelx.bachot@intel.com> Signed-off-by: Jayant Sane <jayant.sane@intel.com>
2011-06-25 10:47:04 +02:00
void wpas_notify_p2p_wps_failed(struct wpa_supplicant *wpa_s,
struct wps_event_fail *fail)
{
wpas_dbus_signal_p2p_wps_failed(wpa_s, fail);
}
P2P: Add notification for P2P device found Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-02-24 21:08:18 +01:00
#endif /* CONFIG_P2P */
wpa_s AP mode: Add notification functions for STA authorized Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-03-16 14:58:41 +01:00
static void wpas_notify_ap_sta_authorized(struct wpa_supplicant *wpa_s,
P2P: Maintain a list of P2P Clients for persistent group on GO Add a new persistent group network block field, p2p_client_list, to maintain a list of P2P Clients that have connected to a persistent group. This allows GO of a persistent group to figure out more easily whether re-invocation of a persistent group can be used with a specific peer device. Signed-hostap: Jouni Malinen <j@w1.fi>
2011-12-22 21:47:41 +01:00
const u8 *sta,
const u8 *p2p_dev_addr)
wpa_s AP mode: Add notification functions for STA authorized Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-03-16 14:58:41 +01:00
{
Fix non-P2P D-Bus build
2011-06-20 08:02:41 +02:00
#ifdef CONFIG_P2P
P2P: Maintain a list of P2P Clients for persistent group on GO Add a new persistent group network block field, p2p_client_list, to maintain a list of P2P Clients that have connected to a persistent group. This allows GO of a persistent group to figure out more easily whether re-invocation of a persistent group can be used with a specific peer device. Signed-hostap: Jouni Malinen <j@w1.fi>
2011-12-22 21:47:41 +01:00
wpas_p2p_notify_ap_sta_authorized(wpa_s, p2p_dev_addr);
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
/*
* Create 'peer-joined' signal on group object -- will also
* check P2P itself.
*/
D-Bus: Fix P2P peer joined/disconnected handlers It is possible for the peer to be a non-P2P device and as such, for p2p_dev_addr to be NULL. This resulted in NULL pointer dereference if D-Bus interface was enabled for the interface when a legacy STA joined a group. Signed-off-by: Jouni Malinen <j@w1.fi>
2014-12-26 17:19:36 +01:00
if (p2p_dev_addr)
wpas_dbus_signal_p2p_peer_joined(wpa_s, p2p_dev_addr);
Fix non-P2P D-Bus build
2011-06-20 08:02:41 +02:00
#endif /* CONFIG_P2P */
D-Bus: Emit signal when a station is authorized or deauthorized Add "StaAuthorized" and "StaDeauthorized" D-Bus interface in AP mode. After enabling the AP mode of wpa_supplicant, the other process need to get the MAC address and authorization status of every station, so wpa_supplicant emits signal when the station is authorized or deauthorized. Signed-hostap: Chengyi Zhao <chengyix.zhao@gmail.com>
2013-06-22 11:09:09 +02:00
/* Notify listeners a new station has been authorized */
wpas_dbus_signal_sta_authorized(wpa_s, sta);
wpa_s AP mode: Add notification functions for STA authorized Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-03-16 14:58:41 +01:00
}
static void wpas_notify_ap_sta_deauthorized(struct wpa_supplicant *wpa_s,
dbus: Remove GroupMember object type and use Peer instead GroupMember is unusable in itself and all the necessary informations are stored in Peer objects, thus replace the use of GroupMember by Peer. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-06-02 16:42:06 +02:00
const u8 *sta,
const u8 *p2p_dev_addr)
wpa_s AP mode: Add notification functions for STA authorized Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-03-16 14:58:41 +01:00
{
Fix non-P2P D-Bus build
2011-06-20 08:02:41 +02:00
#ifdef CONFIG_P2P
DBus: Add support for P2P primitives Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-06-13 00:08:19 +02:00
/*
* Create 'peer-disconnected' signal on group object if this
* is a P2P group.
*/
D-Bus: Fix P2P peer joined/disconnected handlers It is possible for the peer to be a non-P2P device and as such, for p2p_dev_addr to be NULL. This resulted in NULL pointer dereference if D-Bus interface was enabled for the interface when a legacy STA joined a group. Signed-off-by: Jouni Malinen <j@w1.fi>
2014-12-26 17:19:36 +01:00
if (p2p_dev_addr)
wpas_dbus_signal_p2p_peer_disconnected(wpa_s, p2p_dev_addr);
Fix non-P2P D-Bus build
2011-06-20 08:02:41 +02:00
#endif /* CONFIG_P2P */
D-Bus: Emit signal when a station is authorized or deauthorized Add "StaAuthorized" and "StaDeauthorized" D-Bus interface in AP mode. After enabling the AP mode of wpa_supplicant, the other process need to get the MAC address and authorization status of every station, so wpa_supplicant emits signal when the station is authorized or deauthorized. Signed-hostap: Chengyi Zhao <chengyix.zhao@gmail.com>
2013-06-22 11:09:09 +02:00
/* Notify listeners a station has been deauthorized */
wpas_dbus_signal_sta_deauthorized(wpa_s, sta);
wpa_s AP mode: Add notification functions for STA authorized Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-03-16 14:58:41 +01:00
}
void wpas_notify_sta_authorized(struct wpa_supplicant *wpa_s,
P2P: Maintain a list of P2P Clients for persistent group on GO Add a new persistent group network block field, p2p_client_list, to maintain a list of P2P Clients that have connected to a persistent group. This allows GO of a persistent group to figure out more easily whether re-invocation of a persistent group can be used with a specific peer device. Signed-hostap: Jouni Malinen <j@w1.fi>
2011-12-22 21:47:41 +01:00
const u8 *mac_addr, int authorized,
const u8 *p2p_dev_addr)
wpa_s AP mode: Add notification functions for STA authorized Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-03-16 14:58:41 +01:00
{
if (authorized)
P2P: Maintain a list of P2P Clients for persistent group on GO Add a new persistent group network block field, p2p_client_list, to maintain a list of P2P Clients that have connected to a persistent group. This allows GO of a persistent group to figure out more easily whether re-invocation of a persistent group can be used with a specific peer device. Signed-hostap: Jouni Malinen <j@w1.fi>
2011-12-22 21:47:41 +01:00
wpas_notify_ap_sta_authorized(wpa_s, mac_addr, p2p_dev_addr);
wpa_s AP mode: Add notification functions for STA authorized Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-03-16 14:58:41 +01:00
else
dbus: Remove GroupMember object type and use Peer instead GroupMember is unusable in itself and all the necessary informations are stored in Peer objects, thus replace the use of GroupMember by Peer. Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2014-06-02 16:42:06 +02:00
wpas_notify_ap_sta_deauthorized(wpa_s, mac_addr, p2p_dev_addr);
wpa_s AP mode: Add notification functions for STA authorized Signed-off-by: Johannes Berg <johannes.berg@intel.com>
2011-03-16 14:58:41 +01:00
}
Add dbus signal for information about server certification In general, this patch attemps to extend commit 00468b4650998144f794762206c695c962c54734 with dbus support. This can be used by dbus client to implement subject match text entry with preset value probed from server. This preset value, if user accepts it, is remembered and passed to subject_match config for any future authentication. Signed-off-by: Michael Chang <mchang@novell.com>
2011-07-05 11:22:32 +02:00
void wpas_notify_certification(struct wpa_supplicant *wpa_s, int depth,
Add peer certificate alt subject name information to EAP events A new "CTRL-EVENT-EAP-PEER-ALT depth=<i> <alt name>" event is now used to provide information about server certificate chain alternative subject names for upper layers, e.g., to make it easier to configure constraints on the server certificate. For example: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:server.example.com Currently, this includes DNS, EMAIL, and URI components from the certificates. Similar information is priovided to D-Bus Certification signal in the new altsubject argument which is a string array of these items. Signed-off-by: Jouni Malinen <j@w1.fi>
2015-01-14 12:29:40 +01:00
const char *subject, const char *altsubject[],
int num_altsubject, const char *cert_hash,
Add dbus signal for information about server certification In general, this patch attemps to extend commit 00468b4650998144f794762206c695c962c54734 with dbus support. This can be used by dbus client to implement subject match text entry with preset value probed from server. This preset value, if user accepts it, is remembered and passed to subject_match config for any future authentication. Signed-off-by: Michael Chang <mchang@novell.com>
2011-07-05 11:22:32 +02:00
const struct wpabuf *cert)
{
Move peer certificate wpa_msg() calls to notify.c This type of wpa_supplicant specific message construction does not need to be at the EAP implementation, so better move it up to notify.c.
2011-07-05 11:40:37 +02:00
wpa_msg(wpa_s, MSG_INFO, WPA_EVENT_EAP_PEER_CERT
"depth=%d subject='%s'%s%s",
Add peer certificate alt subject name information to EAP events A new "CTRL-EVENT-EAP-PEER-ALT depth=<i> <alt name>" event is now used to provide information about server certificate chain alternative subject names for upper layers, e.g., to make it easier to configure constraints on the server certificate. For example: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:server.example.com Currently, this includes DNS, EMAIL, and URI components from the certificates. Similar information is priovided to D-Bus Certification signal in the new altsubject argument which is a string array of these items. Signed-off-by: Jouni Malinen <j@w1.fi>
2015-01-14 12:29:40 +01:00
depth, subject, cert_hash ? " hash=" : "",
Move peer certificate wpa_msg() calls to notify.c This type of wpa_supplicant specific message construction does not need to be at the EAP implementation, so better move it up to notify.c.
2011-07-05 11:40:37 +02:00
cert_hash ? cert_hash : "");
if (cert) {
char *cert_hex;
size_t len = wpabuf_len(cert) * 2 + 1;
cert_hex = os_malloc(len);
if (cert_hex) {
wpa_snprintf_hex(cert_hex, len, wpabuf_head(cert),
wpabuf_len(cert));
wpa_msg_ctrl(wpa_s, MSG_INFO,
WPA_EVENT_EAP_PEER_CERT
"depth=%d subject='%s' cert=%s",
depth, subject, cert_hex);
os_free(cert_hex);
}
}
Add peer certificate alt subject name information to EAP events A new "CTRL-EVENT-EAP-PEER-ALT depth=<i> <alt name>" event is now used to provide information about server certificate chain alternative subject names for upper layers, e.g., to make it easier to configure constraints on the server certificate. For example: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:server.example.com Currently, this includes DNS, EMAIL, and URI components from the certificates. Similar information is priovided to D-Bus Certification signal in the new altsubject argument which is a string array of these items. Signed-off-by: Jouni Malinen <j@w1.fi>
2015-01-14 12:29:40 +01:00
if (altsubject) {
int i;
for (i = 0; i < num_altsubject; i++)
wpa_msg(wpa_s, MSG_INFO, WPA_EVENT_EAP_PEER_ALT
"depth=%d %s", depth, altsubject[i]);
}
Add dbus signal for information about server certification In general, this patch attemps to extend commit 00468b4650998144f794762206c695c962c54734 with dbus support. This can be used by dbus client to implement subject match text entry with preset value probed from server. This preset value, if user accepts it, is remembered and passed to subject_match config for any future authentication. Signed-off-by: Michael Chang <mchang@novell.com>
2011-07-05 11:22:32 +02:00
/* notify the old DBus API */
wpa_supplicant_dbus_notify_certification(wpa_s, depth, subject,
cert_hash, cert);
/* notify the new DBus API */
Add peer certificate alt subject name information to EAP events A new "CTRL-EVENT-EAP-PEER-ALT depth=<i> <alt name>" event is now used to provide information about server certificate chain alternative subject names for upper layers, e.g., to make it easier to configure constraints on the server certificate. For example: CTRL-EVENT-EAP-PEER-ALT depth=0 DNS:server.example.com Currently, this includes DNS, EMAIL, and URI components from the certificates. Similar information is priovided to D-Bus Certification signal in the new altsubject argument which is a string array of these items. Signed-off-by: Jouni Malinen <j@w1.fi>
2015-01-14 12:29:40 +01:00
wpas_dbus_signal_certification(wpa_s, depth, subject, altsubject,
num_altsubject, cert_hash, cert);
Add dbus signal for information about server certification In general, this patch attemps to extend commit 00468b4650998144f794762206c695c962c54734 with dbus support. This can be used by dbus client to implement subject match text entry with preset value probed from server. This preset value, if user accepts it, is remembered and passed to subject_match config for any future authentication. Signed-off-by: Michael Chang <mchang@novell.com>
2011-07-05 11:22:32 +02:00
}
DBus: Add ability to report probe requests Some applications require knowing about probe requests to identify devices. This can be the case in AP mode to see the devices before they connect, or even in P2P mode when operating as a P2P device to identify non-P2P peers (P2P peers are identified via PeerFound signals). As there are typically a lot of probe requests, require that an interested application subscribes to this signal so the bus isn't always flooded with these notifications. The notifications in DBus are then unicast only to that application. A small test script is also included. Signed-hostap: Johannes Berg <johannes.berg@intel.com>
2012-04-01 20:13:38 +02:00
void wpas_notify_preq(struct wpa_supplicant *wpa_s,
const u8 *addr, const u8 *dst, const u8 *bssid,
const u8 *ie, size_t ie_len, u32 ssi_signal)
{
#ifdef CONFIG_AP
wpas_dbus_signal_preq(wpa_s, addr, dst, bssid, ie, ie_len, ssi_signal);
#endif /* CONFIG_AP */
}
wpa_supplicant: Report EAP connection progress to DBus Send an "EAP" signal via the new DBus interface under various conditions during EAP authentication: - During method selection (ACK and NAK) - During certificate verification - While sending and receiving TLS alert messages - EAP success and failure messages This provides DBus callers a number of new tools: - The ability to probe an AP for available EAP methods (given an identity). - The ability to identify why the remote certificate was not verified. - The ability to identify why the remote peer refused a TLS connection. Signed-hostap: Paul Stewart <pstew@chromium.org>
2012-06-04 20:10:01 +02:00
void wpas_notify_eap_status(struct wpa_supplicant *wpa_s, const char *status,
const char *parameter)
{
wpas_dbus_signal_eap_status(wpa_s, status, parameter);
Provide TLS alerts to CLI/UI over control interface Harmonize EAP status events over control interface to provide same functionality as existing D-Bus callback. Signed-hostap: Chris Hessing <chris.hessing@cloudpath.net>
2013-04-23 15:46:02 +02:00
wpa_msg_ctrl(wpa_s, MSG_INFO, WPA_EVENT_EAP_STATUS
"status='%s' parameter='%s'",
status, parameter);
wpa_supplicant: Report EAP connection progress to DBus Send an "EAP" signal via the new DBus interface under various conditions during EAP authentication: - During method selection (ACK and NAK) - During certificate verification - While sending and receiving TLS alert messages - EAP success and failure messages This provides DBus callers a number of new tools: - The ability to probe an AP for available EAP methods (given an identity). - The ability to identify why the remote certificate was not verified. - The ability to identify why the remote peer refused a TLS connection. Signed-hostap: Paul Stewart <pstew@chromium.org>
2012-06-04 20:10:01 +02:00
}
Add support for driver command to update roaming policy The network block bssid parameter can be used to force a specific BSS to be used for a connection. It is also possible to modify this parameter during an association. Previously, that did not result in any notification to the driver which was somewhat problematic with drivers that take care of BSS selection. Add a new mechanism to allow wpa_supplicant to provide a driver update if the bssid parameter change for the current connection modifies roaming policy (roaming allowed/disallowed within ESS). Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
2014-09-11 14:52:37 +02:00
void wpas_notify_network_bssid_set_changed(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid)
{
if (wpa_s->current_ssid != ssid)
return;
wpa_dbg(wpa_s, MSG_DEBUG,
"Network bssid config changed for the current network - within-ESS roaming %s",
ssid->bssid_set ? "disabled" : "enabled");
wpa_drv_roaming(wpa_s, !ssid->bssid_set,
ssid->bssid_set ? ssid->bssid : NULL);
}
D-Bus: Fix network block type change It is possible for a network profile to change its type from P2P persistent group to a normal network and back. The D-Bus interface uses different types of objects for those, so the object needs to re-registered in case of type change. This fixes issues in leaving behind an incorrect type of object and leaking memory when freeing such a network block that has had its disabled parameter changed. Signed-off-by: Jouni Malinen <j@w1.fi>
2015-02-07 15:17:11 +01:00
void wpas_notify_network_type_changed(struct wpa_supplicant *wpa_s,
struct wpa_ssid *ssid)
{
#ifdef CONFIG_P2P
if (ssid->disabled == 2) {
/* Changed from normal network profile to persistent group */
ssid->disabled = 0;
wpas_dbus_unregister_network(wpa_s, ssid->id);
ssid->disabled = 2;
P2P: Fix persistent group profile on manual disabled=2 change ssid->p2p_persistent_group was left to its old value when changing a network profile to/from P2P persistent group type (disabled=2). This could result in unexpected behavior when using an incomplete persistent group profile. This was mainly visible through D-Bus network profile handling where a persistent group would not be unregistered insome cases. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
2015-06-10 22:58:21 +02:00
ssid->p2p_persistent_group = 1;
D-Bus: Fix network block type change It is possible for a network profile to change its type from P2P persistent group to a normal network and back. The D-Bus interface uses different types of objects for those, so the object needs to re-registered in case of type change. This fixes issues in leaving behind an incorrect type of object and leaking memory when freeing such a network block that has had its disabled parameter changed. Signed-off-by: Jouni Malinen <j@w1.fi>
2015-02-07 15:17:11 +01:00
wpas_dbus_register_persistent_group(wpa_s, ssid);
} else {
/* Changed from persistent group to normal network profile */
wpas_dbus_unregister_persistent_group(wpa_s, ssid->id);
P2P: Fix persistent group profile on manual disabled=2 change ssid->p2p_persistent_group was left to its old value when changing a network profile to/from P2P persistent group type (disabled=2). This could result in unexpected behavior when using an incomplete persistent group profile. This was mainly visible through D-Bus network profile handling where a persistent group would not be unregistered insome cases. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
2015-06-10 22:58:21 +02:00
ssid->p2p_persistent_group = 0;
D-Bus: Fix network block type change It is possible for a network profile to change its type from P2P persistent group to a normal network and back. The D-Bus interface uses different types of objects for those, so the object needs to re-registered in case of type change. This fixes issues in leaving behind an incorrect type of object and leaking memory when freeing such a network block that has had its disabled parameter changed. Signed-off-by: Jouni Malinen <j@w1.fi>
2015-02-07 15:17:11 +01:00
wpas_dbus_register_network(wpa_s, ssid);
}
#endif /* CONFIG_P2P */
}
Reference in a new issue Copy permalink