Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESP32 STA deauth frame causing reconnect issues (IDFGH-6544) #8192

Closed
tablatronix opened this issue Jan 4, 2022 · 60 comments
Closed

ESP32 STA deauth frame causing reconnect issues (IDFGH-6544) #8192

tablatronix opened this issue Jan 4, 2022 · 60 comments
Assignees
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally

Comments

@tablatronix
Copy link

tablatronix commented Jan 4, 2022

Environment

  • Development Kit: Custom
  • Kit version NA
  • Module or chip used: ESP32-WROOM-32D

I am not yet up and running with an IDF example, as this was discovered downstream in arduino.
I finally had time to look into this long time issue and am trying to identify/resolve the 2-3 issues this is encompassing.
espressif/arduino-esp32#2501

Problem Description

The Frame in question

This change was made sometime in late 3.x SDK I think. I am assuming this is maybe from a CVE patch , but I cannot find the exact documentation for this, maybe someone can tip me off, most of the dos/injections are against enterprise WPA2, not WPA2 PSK shrug.. I am not wifi expert.

I am hoping PMF/WPA3 solves this.. I have not been able to confirm that yet.

The immediate issue is that this causes some APs to (within a timeout period of last assoc, so device resets mostly!) respond to these sta deauths with a deauth reasoncode 2 or some other bizarro responses, i have seen 4way fails etc.

Screen Shot 2022-01-04 at 10 05 23 AM
Screen Shot 2022-01-04 at 10 05 37 AM

The router response

This is my unifi nanohd ap sending a deauth back

Nov 20 22:24:01 nanohd f492bf7f354a,UAP-nanoHD-5.60.9+12980: stahtd: stahtd[2269]: [STA-TRACKER].stahtd_dump_event(): {"message_type":"STA_ASSOC_TRACKER","assoc_delta":"0","wpa_auth_failures":"1","mac":"7c:df:a1:00:77:ec","vap":"ra0","event_type":"failure","assoc_status":"0","event_id":"12","auth_delta":"0","auth_ts":"2360096.826707"}

Nov 20 22:49:10 nanohd f492bf7f354a,UAP-nanoHD-5.60.9+12980: hostapd: ra0: STA 7c:df:a1:00:77:ec IEEE 802.11: disassociated
Nov 20 22:49:10 nanohd f492bf7f354a,UAP-nanoHD-5.60.9+12980: kernel: ra0: AUTH - receive DE-AUTH(seq-3796) from 7c:df:a1:00:77:ec, reason=3
Nov 20 22:49:10 nanohd f492bf7f354a,UAP-nanoHD-5.60.9+12980: kernel: ra0: (MlmeDeAuthAction)Send DEAUTH frame with ReasonCode(2) to 7c:df:a1:00:77:ec
Nov 20 22:49:10 nanohd f492bf7f354a,UAP-nanoHD-5.60.9+12980: : wevent[2268]: wevent.ubnt_custom_event(): EVENT_STA_LEAVE ra0: 7c:df:a1:00:77:ec / 9
Nov 20 22:49:10 nanohd f492bf7f354a,UAP-nanoHD-5.60.9+12980: hostapd: ra0: STA 7c:df:a1:00:77:ec IEEE 802.11: disassociated

143319428-0fe1da18-c1fd-4659-9a49-8541fbc9451d

[  1479][V][WiFiGeneric.cpp:96] set_esp_interface_ip(): Configuring Station static IP: 0.0.0.0, MASK: 0.0.0.0, GW: 0.0.0.0
[WIFI] Connecting to wifi... [20000 ms]

.....................E (7394) wifi:Association refused temporarily, comeback time 1048 mSec
.....................[  5611][V][WiFiGeneric.cpp:289] _arduino_event_cb(): STA Disconnected: SSID: ssid, BSSID: f4:92:bf:7f:35:4b, Reason: 203
[  5612][D][WiFiGeneric.cpp:831] _eventCallback(): Arduino Event: 5 - STA_DISCONNECTED
[  5619][W][WiFiGeneric.cpp:852] _eventCallback(): Reason: 203 - ASSOC_FAIL

Now there are 2 things going on here.

  1. Why is this behavior happening? De-auth protection mechanism on both sides maybe? Can we turn it off, should it be turned off for some 80211 protos? or something ? Is it a security mechanism and thats it, we are stuck with it?

1.b Even with a workaround and reconnect, we are looking at connection times of 8-16 seconds over 1.6s in previous SDKs. Making bssid, and channel caching an absolute requirement now and YET STILL having double the connect times of 3-5s. Battery power devices be damned.. lol

  1. Missing Event reason/codes to properly identify these in arduino and defer a reconnect to handle this independently from autoreconnect maybe? As of now this usually fails with no useful reason other than auth fail which is confusing. Again still looking at 8s reconnects.

refs#
espressif/arduino-esp32#2501 (comment)

@espressif-bot espressif-bot added the Status: Opened Issue is new label Jan 4, 2022
@github-actions github-actions bot changed the title ESP32 STA deauth frame causing reconnect issues ESP32 STA deauth frame causing reconnect issues (IDFGH-6544) Jan 4, 2022
@tablatronix
Copy link
Author

If you want to test this on arduino, be sure to turn off autoreconnect or you will be fighting 2 things as there is a async state issue in there. WiFi.setAutoReconnect(false);

@nishanth-radja
Copy link
Collaborator

Hi @tablatronix , can we have the complete capture to understand the issue better?

@tablatronix
Copy link
Author

tablatronix commented Jan 6, 2022

First assoc succeeds, second fails

esp32_deauthissue_reset.pcapng.zip

Screen Shot 2022-01-05 at 9 05 23 PM

@jack0c
Copy link
Collaborator

jack0c commented Jan 6, 2022

@tablatronix Reason code 2 means: Previous authentication no longer valid, no communication between the devices for long? There should be a QoS NULL keep alive frame sent from ESP32 every 5s, do you see the frames. It looks the deauth frame sent from ESP32, it is likely that the router didn't send ACK frame to the QoS NULL frame. Or maybe when ESP32 wake up from sleep, and send NULL data to router, and fail. Your capture looks didn't include 802.11 Ack frames, you can capture with them. Another option is to disable sleep and test again.

@tablatronix
Copy link
Author

Sure let me check those and see if I am not capturing,

this is a reboot not sleep.

this is a popular issue in arduino , 3 years old hundreds of comments.

@tablatronix
Copy link
Author

tablatronix commented Jan 6, 2022

Acks are there, let me clean up my filters

Screen Shot 2022-01-06 at 8 13 50 AM

@tablatronix
Copy link
Author

qos and acks are in capture..

esp32_deauthissue_doublereset.pcapng.zip

Screen Shot 2022-01-06 at 8 29 49 AM

@nishanth-radja
Copy link
Collaborator

@tablatronix From the capture,We can see that the sta is getting deauthed because there is a shift in beacon time.I see that there is multiple BSSID and couple of beacons have not been transmitted by the AP after STA comes out of power save.since there is a time shift now the STA will not be able to see the consecutive beacons and eventually will scan again and go for reconnect. scan starts from pkt 24709.Once there is probe-response from AP,STA will send deauth and associate again as expected pkt(26849).
But AP is has not cleared the STA from it's list yet. Hence the ap sends deauth when sta sends authentication and does not reply to assoc req from STA.

@nishanth-radja
Copy link
Collaborator

image

@nishanth-radja
Copy link
Collaborator

Beacon interval in 1024 ms,but we see a 2053 ms difference.To confirm if this is causing the issue,Can you disable the power save on esp32 and check, Also if you have captures during other instance of disconnect ,can you pls share them. we can verify if this is the case every time.

@tablatronix
Copy link
Author

What other instance of disconnect are you interested in? Not sure I understand, this is every time device is reset, well every other time, as the ap goes back and forth with the sta state tracking toggle like. I will capture a bunch of stuff and make a new test so you can see it better.

@tablatronix
Copy link
Author

tablatronix commented Jan 7, 2022

I wrote some new tests and found something that agrees with a timing issue, This only occurs on hardware resets, not soft resets, what could that imply ?

@tablatronix
Copy link
Author

tablatronix commented Jan 7, 2022

Well here is me hardware reseting every 10 seconds, its clear that every second boot fails with auth fail.
obviously AP state is a player, if sta was connected and reconnects it always fails with an auth fail.

Hope it helps figure something out.. Not sure what beacons have to do with it as it is not intermittent or random, its the same over and over, but it didn't do this on older IDFs, I will roll back and capture those too, hence why I thought the teardown was changing this behavior now.

every_other_hardware_reset.pcapng.zip

@tablatronix
Copy link
Author

tablatronix commented Jan 7, 2022

Here is a capture from
ESP-IDF version: v3.2.3-14-gd3e56290
connect succeeds on every boot ( fast too 1.3s! )
Auth issue not present.

every_other_hardware_reset_3_2_3.pcapng.zip

and the ino

#include <rom/rtc.h>
#include <WiFi.h>
#include <esp_wifi.h>
#include <ESPmDNS.h>

long start = 0;
uint16_t reboot = 10000;

void setup(){
	delay(1000);
	Serial.begin(115200);
	Serial.setDebugOutput(true);
	Serial.println("Starting...");

    // size_t freeHeap = heap_caps_get_free_size(MALLOC_CAP_8BIT);
    // DEBUGGER("Free heap:       ", freeHeap);
    Serial.println("ESP-IDF version: " + (String) esp_get_idf_version());

    // WiFi.mode(WIFI_STA);

	// WiFi.printDiag(Serial);

    // btStop();
    WiFi.setSleep(false);	
	WiFi.setAutoReconnect(false);
	WiFi.begin("SSID","PASS");
	uint8_t res = WiFi.waitForConnectResult();
	Serial.println(res);
	Serial.println(WiFi.status());
	Serial.println((String)((WiFi.status()== WL_CONNECTED)? "CONNECTED" : "NOT CONECTED"));
	Serial.println((String)millis());
	start = millis();
}


void loop(){
	if(millis()-start > reboot){ 
	// ESP.restart(); // doesn't work, issue only present on hardware reboots.
	}
	Serial.print(".");
	delay(100);
}

@nishanth-radja
Copy link
Collaborator

nishanth-radja commented Jan 10, 2022

Hi @tablatronix , what is the latest build on which you are seeing the issue?
From both the captures we were able to figure out the issue,
The issue is that sta sends deauth to AP before starting a fresh connection.(This behavior was introduced lately as a fix for an another issue).
so the sequence is as follows.
1.Sta sends Deauth to AP before Auth
2.AP Acks the Deauth
3.Sta starts the Auth Process.
4.AP takes time to process the deauth hence is sending the Deauth in between the Auth process. (This issue is not seen on other Ap's)
5.So Sta is not replying to the further packets from AP.

On the build on which issue is not seen,Deauth is not sent before assoc and hence there is no issue in re connection.
If you can point the build on which the issue is observed,we can port the fix on that build.
Also can you mention the AP model which you are using?

@tablatronix
Copy link
Author

tablatronix commented Jan 10, 2022

Yup, pretty much what I was seeing hence the title, just wasn't sure how it was causing failures.

I am using a UNIFI Nano HD AP, there are some others in the arduino thread that might have more types.

I will have to do more testing to see what versions, but its been around a while, I have not tested staging yet though
I think the first capture was on ESP-IDF version: v3.3.5-1-g85c43024c But I assume its sometime after 3.1 maybe?
Ill see if I can get pio to cooperate and narrow down with some version tagging

@csobrinho
Copy link
Contributor

I believe I'm having the same issue. I'm using ESP-IDF directly and I'm synced to 5968bf6.

I can see the wifi trying to connect and getting a deauth several times. The connection time went from 2s to 10-20-40s.

Please find attached the filtered pcap file.

The device is remote so I can only get the logs later tomorrow but the symptoms are similar to these logs over and over:

I (23440) wifi:state: init -> auth (b0)
I (23480) wifi:state: auth -> assoc (0)
I (23520) wifi:state: assoc -> run (10)
I (26630) wifi:state: run -> init (fc0)
I (26630) wifi:new:<2,0>, old:<2,0>, ap:<255,255>, sta:<2,0>, prof:1
I (26630) wifi:new:<2,0>, old:<2,0>, ap:<255,255>, sta:<2,0>, prof:1

I have a mesh network:

  • Nest Wifi Router is at 7c:d9:5c:9a:7a:e0 on channel 11
  • Nest Wifi Point is at 7c:d9:5c:9a:7a:e6 on channel 1

My wifi code is here:
https://github.com/csobrinho/hydroponics/blob/master/main/network/wifi.c

Sometimes a hard reboot fixes the issue but the device loses wifi later on.

Thanks for the help.

@tablatronix
Copy link
Author

tablatronix commented Jan 11, 2022

@csobrinho looks like a different issue, you seem to be getting deuths during and after EAPOL which is strange, seems like an unstable connection or a ton of packet loss also considering you are losing connection later, whereas this issue occurs every single time with the exact same timing at the same stage of negotiation before assoc.

@csobrinho
Copy link
Contributor

Portion of the logs:

I (10209) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (10209) nwifi: Disconnected from Sobrinho, bssid: c6:f5:47:19:5c:64, reason: 2
I (12279) nwifi: Disconnected from Sobrinho, bssid: 00:00:00:00:00:00, reason: 205
I (14329) wifi:new:<11,0>, old:<1,0>, ap:<255,255>, sta:<11,0>, prof:1
I (14339) wifi:state: init -> auth (b0)
I (14339) wifi:state: auth -> assoc (0)
I (14349) wifi:state: assoc -> run (10)
I (17359) wifi:state: run -> init (fc0)
I (17369) wifi:new:<11,0>, old:<11,0>, ap:<255,255>, sta:<11,0>, prof:1
I (17369) wifi:new:<11,0>, old:<11,0>, ap:<255,255>, sta:<11,0>, prof:1
I (17379) wifi:new:<1,0>, old:<11,0>, ap:<255,255>, sta:<1,0>, prof:1
I (17379) wifi:state: init -> auth (b0)
I (17419) wifi:state: auth -> assoc (0)
I (17419) wifi:state: assoc -> run (10)
I (21429) wifi:state: run -> init (2c0)
I (21429) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (21429) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (21439) nwifi: Disconnected from Sobrinho, bssid: c6:f5:47:19:5c:64, reason: 2
I (23499) nwifi: Disconnected from Sobrinho, bssid: 00:00:00:00:00:00, reason: 205
I (25559) wifi:new:<11,0>, old:<1,0>, ap:<255,255>, sta:<11,0>, prof:1
I (25559) wifi:state: init -> auth (b0)
I (25569) wifi:state: auth -> assoc (0)
I (25579) wifi:state: assoc -> run (10)
I (28589) wifi:state: run -> init (fc0)
I (28589) wifi:new:<11,0>, old:<11,0>, ap:<255,255>, sta:<11,0>, prof:1
I (28589) wifi:new:<11,0>, old:<11,0>, ap:<255,255>, sta:<11,0>, prof:1
I (28599) wifi:new:<1,0>, old:<11,0>, ap:<255,255>, sta:<1,0>, prof:1
I (28609) wifi:state: init -> auth (b0)
I (28669) wifi:state: auth -> assoc (0)
I (28669) wifi:state: assoc -> run (10)
I (28719) wifi:connected with Sobrinho, aid = 1, channel 1, BW20, bssid = c6:f5:47:19:5c:64
I (28719) wifi:security: WPA2-PSK, phy: bgn, rssi: -68
I (28779) wifi:pm start, type: 0
I (28779) wifi:AP's beacon interval = 102400 us, DTIM period = 2
I (31799) wifi:state: run -> init (2c0)
I (31799) wifi:pm stop, total sleep time: 0 us / 3014037 us
I (31799) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:1
I (31799) nwifi: Disconnected from Sobrinho, bssid: c6:f5:47:19:5c:64, reason: 2
I (33869) wifi:new:<11,0>, old:<1,0>, ap:<255,255>, sta:<11,0>, prof:1
I (33869) wifi:state: init -> auth (b0)
I (33879) wifi:state: auth -> assoc (0)
I (33889) wifi:state: assoc -> run (10)
I (35929) wifi:connected with Sobrinho, aid = 4, channel 11, BW20, bssid = 7c:d9:5c:9a:7a:e6
I (35929) wifi:security: WPA2-PSK, phy: bgn, rssi: -67
I (35939) wifi:pm start, type: 0
I (35979) wifi:AP's beacon interval = 102400 us, DTIM period = 2
W (36139) wifi:<ba-add>idx:0 (ifx:0, 7c:d9:5c:9a:7a:e6), tid:0, ssn:0, winSize:64
W (219339) wifi:<ba-add>idx:1 (ifx:0, 7c:d9:5c:9a:7a:e6), tid:6, ssn:4, winSize:64
W (219369) wifi:<ba-del>idx
W (219379) wifi:<ba-add>idx:1 (ifx:0, 7c:d9:5c:9a:7a:e6), tid:6, ssn:5, winSize:64
I (220309) esp_netif_handlers: sta ip: 192.168.86.10, mask: 255.255.255.0, gw: 192.168.86.1

@tablatronix
Copy link
Author

tablatronix commented Jan 11, 2022

I (21439) nwifi: Disconnected from Sobrinho, bssid: c6:f5:47:19:5c:64, reason: 2
I (23499) nwifi: Disconnected from Sobrinho, bssid: 00:00:00:00:00:00, reason: 205

Reasons Are AUTH EXPIRE and WIFI_REASON_CONNECTION_FAIL, more than likely unrelated, have you tried a different router, also your rssi is pretty bad

Have you turned off sleep ?

@csobrinho
Copy link
Contributor

Hi tablatronix, thanks for the help. Yes, I'm using the esp_wifi_set_ps(WIFI_PS_NONE). I already moved the Nest wifi Point closer to the device but I'm still getting -68 for one and -65 for the other. I think the device is trying to connect to both APs on the mesh network and keeps getting bounced around.

@AxelLin
Copy link
Contributor

AxelLin commented Jan 12, 2022

I (21439) nwifi: Disconnected from Sobrinho, bssid: c6:f5:47:19:5c:64, reason: 2 I (23499) nwifi: Disconnected from Sobrinho, bssid: 00:00:00:00:00:00, reason: 205

Reasons Are AUTH EXPIRE and WIFI_REASON_CONNECTION_FAIL, more than likely unrelated,

@csobrinho
Please create a new issue.

@AxelLin
Copy link
Contributor

AxelLin commented Jan 17, 2022

I will have to do more testing to see what versions, but its been around a while, I have not tested staging yet though I think the first capture was on ESP-IDF version: v3.3.5-1-g85c43024c But I assume its sometime after 3.1 maybe? Ill see if I can get pio to cooperate and narrow down with some version tagging

Since it's reproducable, you can use "git bisect" to find the first bad commit.

@tablatronix
Copy link
Author

I can but my env is not setup to , it will take a while, its easier for someone that knows the idf to know when this was introduced and why.

Platformio uses its own repo for esp32 releases, and using upstream doesn't always build

@nishanth-radja
Copy link
Collaborator

Hi @tablatronix Can you pls try this patch.
These files needs to be replaced in the following location.
$IDF_HOME/components/esp32/lib
clean the already existing build and rebuild again.
idf.py fullclean
idf.py build

Also pls take the sniffer capture during association using this patch.

patch_for_reconnect_issue.zip
.

@tablatronix
Copy link
Author

Sure thing

@tablatronix
Copy link
Author

If I am using PIO can I do a normal clean and compile?
Also what version of IDF do I need to patch from ?

@tablatronix
Copy link
Author

tablatronix commented Feb 17, 2022

here is a longer capture of 3 restarts, looks like that previous might be missing a capture not sure... Not seeing a deauth on the first after starting wireshark for some reason

Screen Shot 2022-02-17 at 9 32 35 AM

ESP-IDF v4.4-172-g730ca0ea43-dirty_PATCH3_X3.pcapng.zip

@AxelLin
Copy link
Contributor

AxelLin commented Feb 18, 2022

@nishanth-radja

I'm wondering if espressif/esp32-wifi-lib@5a4e7d2 is related to this or not?
What was fixed by espressif/esp32-wifi-lib@5a4e7d2 from user's point of view.

@tablatronix
Copy link
Author

huh? That commit says 2 days ago, so no. unrelated

@nishanth-radja
Copy link
Collaborator

Hi @tablatronix,Thanks for the capture and the initial issue of AP not responding to Assoc req is solved.
Capture before patch -
image

From the above capture ,we see that the AP sends deauth after auth and does not respond to assoc req.
after the patch ,
image

we see that the AP responds with the Assoc resp ,with a come back time of 1 sec.This is expected as PMF is enabled and the STA info is not cleared from the AP. But AP is not sending any SA query packets.
And the pkt 16407 is an Ack to the STA but the pkt before is not captured.Which could be the Assoc resp. To confirm this can you take the sniffer capture again.
Also can you disable the PMF on the STA and see if it can connect.Once the PMF is disabled AP will accept the connection the second time without delay.

@tablatronix
Copy link
Author

tablatronix commented Feb 18, 2022

AHHH yes, sorry, I had it off in my original test, but not in the IDF example I am now using for these..
I will test again, I will have to find out how to do that in IDF

@tablatronix
Copy link
Author

tablatronix commented Feb 19, 2022

It works with STA PMF off

ESP-IDF v4.4-172-g730ca0ea43-dirty_PATCH3_pmfcapableFALSE.pcapng.zip

Only issue I can think of is that the IDF says that PMF cannot be disabled on the S2.
So I am assuming that this WILL work with PMF on and PMF required on ap, and wpa3 ?

I can test all these things this week.

Test PMF

  • AP required / STA Optional
  • AP disabled / STA Optional
  • AP WP3

@AxelLin
Copy link
Contributor

AxelLin commented Feb 19, 2022

Also can you disable the PMF on the STA and see if it can connect.Once the PMF is disabled AP will accept the connection the second time without delay.

@nishanth-radja

I though below setting on STA should always work.
.pmf_cfg = {
.capable = true,
.required = false
}

Did I misunderstand something?

@tablatronix
Copy link
Author

tablatronix commented Feb 19, 2022

It depends on the AP setting, both AP and STA have disabled, capable(optional), required.
Here is the matrix

https://docs.espressif.com/projects/esp-idf/en/latest/esp32s2/api-guides/wifi-security.html#protected-management-frames-pmf

@nishanth-radja
Copy link
Collaborator

nishanth-radja commented Feb 21, 2022

@tablatronix yes,Pls test with PMF setting on and pls provide the sniffer capture for the same.
@AxelLin Yes,with that PMF setting It is supposed to work with all the AP's.We need more captures with the PMF enabled scenario on why it failed to connect with PMF enabled.

@tablatronix
Copy link
Author

Sorry I have not had a chance to do more testing will try soon

@espressif-bot espressif-bot added Status: In Progress Work is in progress and removed Status: Opened Issue is new labels Mar 14, 2022
@AxelLin
Copy link
Contributor

AxelLin commented May 10, 2022

Sorry I have not had a chance to do more testing will try soon

@tablatronix
Any update?
The PMF is always enabled now, so if it failed there must be some bug needs fix.

@tablatronix
Copy link
Author

@nishanth-radja Is this patched in 4.4.1?

Is this this issue?

Fixed Assoc comeback causing invalid state bug and cleanup in some FTM failure cases

If so can you tag this issue# in release

@nishanth-radja
Copy link
Collaborator

@tablatronix No ,That is not the patch for the above mentioned issue.

@espressif-bot espressif-bot added Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally Resolution: Done Issue is done internally and removed Status: In Progress Work is in progress Resolution: NA Issue resolution is unavailable labels Jul 5, 2022
@AxelLin
Copy link
Contributor

AxelLin commented Jul 25, 2022

hi @nishanth-radja
Could you share the commit of this fix? (Since this is marked as resolution done).
I'd like to check if the fix is in v4.3 and v4.4 or not.

@jack0c
Copy link
Collaborator

jack0c commented Jun 2, 2023

master: ce1ab73
v4.4: 53c186a
v4.3: 53c186a

@tablatronix
Copy link
Author

Anyone notice this fixed? I have not been working much on esp32 lately, I will do some testing, but I have not noticed this issue as much or seen increased or slow connection tries

@thorrak
Copy link

thorrak commented Aug 5, 2023

Anyone notice this fixed? I have not been working much on esp32 lately, I will do some testing, but I have not noticed this issue as much or seen increased or slow connection tries

I haven't noticed it with the latest ESP32 frameworks, thankfully. Keeping my fingers crossed that it stays fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally
Projects
None yet
Development

No branches or pull requests

8 participants