public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH v2 03/11] station: handle NETDEV_RESULT_DISCONNECTED
Date: Thu, 18 Jul 2024 04:45:06 -0700	[thread overview]
Message-ID: <20240718114514.2916258-4-prestwoj@gmail.com> (raw)
In-Reply-To: <20240718114514.2916258-1-prestwoj@gmail.com>

This new event is sent during a connection if netdev recieves a
disconnect event. This patch cleans up station to handle this
case and leave the existing NETDEV_EVENT_DISCONNECTED_BY_{AP,SME}
handling only for CONNECTED, NETCONFIG, and FW_ROAMING states.
---
 src/station.c | 27 ++++++++++++++++++---------
 1 file changed, 18 insertions(+), 9 deletions(-)

diff --git a/src/station.c b/src/station.c
index 01f6b78e..abbfc3dd 100644
--- a/src/station.c
+++ b/src/station.c
@@ -3311,6 +3311,7 @@ static void station_connect_cb(struct netdev *netdev, enum netdev_result result,
 {
 	struct station *station = user_data;
 	bool continue_autoconnect;
+	uint16_t reason = MMPDU_REASON_CODE_UNSPECIFIED;
 
 	l_debug("%u, result: %d", netdev_get_ifindex(station->netdev), result);
 
@@ -3320,9 +3321,22 @@ static void station_connect_cb(struct netdev *netdev, enum netdev_result result,
 		station_connect_ok(station);
 		return;
 	case NETDEV_RESULT_DISCONNECTED:
+		reason = l_get_u16(event_data);
+
+		iwd_notice(IWD_NOTICE_DISCONNECT_INFO, "reason: %u", reason);
+
+		/* Disconnected while connecting */
+		network_blacklist_add(station->connected_network,
+						station->connected_bss);
+		if (station_try_next_bss(station))
+			return;
+
+		break;
 	case NETDEV_RESULT_HANDSHAKE_FAILED:
+		reason = l_get_u16(event_data);
+
 		/* reason code in this case */
-		if (station_retry_with_reason(station, l_get_u16(event_data)))
+		if (station_retry_with_reason(station, reason))
 			return;
 
 		break;
@@ -3383,17 +3397,12 @@ static void station_disconnect_event(struct station *station, void *event_data)
 	/*
 	 * If we're connecting, AP deauthenticated us, most likely because
 	 * we provided the wrong password or otherwise failed authentication
-	 * during the handshaking phase.  Treat this as a connection failure
+	 * during the handshaking phase. Connection failures should be handled
+	 * within station_connect_cb/station_reassociate_cb apart from netconfig
+	 * and FW roams.
 	 */
 	switch (station->state) {
-	case STATION_STATE_CONNECTING:
-	case STATION_STATE_CONNECTING_AUTO:
-		station_connect_cb(station->netdev,
-					NETDEV_RESULT_HANDSHAKE_FAILED,
-					event_data, station);
-		return;
 	case STATION_STATE_CONNECTED:
-	case STATION_STATE_FT_ROAMING:
 	case STATION_STATE_FW_ROAMING:
 	case STATION_STATE_NETCONFIG:
 		iwd_notice(IWD_NOTICE_DISCONNECT_INFO, "reason: %u",
-- 
2.34.1


  parent reply	other threads:[~2024-07-18 11:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 11:45 [PATCH v2 00/11] Refactor to unify connect failure code path James Prestwood
2024-07-18 11:45 ` [PATCH v2 01/11] station: print unknown channel number in neighbor report James Prestwood
2024-07-18 11:45 ` [PATCH v2 02/11] netdev: add NETDEV_RESULT_DISCONNECTED James Prestwood
2024-07-18 11:45 ` James Prestwood [this message]
2024-07-18 11:45 ` [PATCH v2 04/11] station: update logic for handshake failure James Prestwood
2024-07-18 11:45 ` [PATCH v2 05/11] netdev: handle disconnect event during a connection James Prestwood
2024-07-18 11:45 ` [PATCH v2 06/11] eapol: move HANDSHAKE_STARTED_EVENT to eapol_start() James Prestwood
2024-07-18 11:45 ` [PATCH v2 07/11] station: add handshake-started debug event James Prestwood
2024-07-18 11:45 ` [PATCH v2 08/11] auto-t: add clear_events() to IWD class James Prestwood
2024-07-18 11:45 ` [PATCH v2 09/11] auto-t: add reason/test arguments to hostapd deauthenticate James Prestwood
2024-07-18 11:45 ` [PATCH v2 10/11] auto-t: Add deauth during the 4-way handshake test James Prestwood
2024-07-18 11:45 ` [PATCH v2 11/11] auto-t: a few random autotest fixes James Prestwood
2024-07-18 21:11 ` [PATCH v2 00/11] Refactor to unify connect failure code path Denis Kenzior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240718114514.2916258-4-prestwoj@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox