Posted: Thu Jun 05, 2025 20:22 Post subject: ESP8266 devices frequently drop connection. Tp Link A7 C4
Hi, I did see post explaining resolution for R7800 by changing Frames Threshold back in Aug 2024 by Lexridge.
But this option is not there for Qualcomm QCA9563 based devices for me to test? I'm on DD-WRT v3.0-r59468 std (02/02/25)
And main question: if this still possible fix for the DDWRT FW in use?
May other options to consider?
Is this applicable?
# nvram show | grep frag
wl1_frag=1568
Just to mention, no problems with OTA, just connection. Signal quality is 100%
Thank you.
Joined: 08 May 2018 Posts: 17264 Location: Texas, USA
Posted: Thu Jun 05, 2025 22:57 Post subject:
I'm trying to surmise where the 1568 number came from per sir @lexridge outside of personal experience and extensive testing(?). Do you not have output for nvram show | grep frag? And if you do, what is it? I'm going to guess if it has not been modified and is present, it's going to be 2346 or 7. As someone with your tenure, I don't know how you cannot solve this. Here's a hint: nvram set. That's all the spoons I have, still recuperating from the girl child "facetiming" me to utter a rather long and obnoxiously loud string of obsenities because of this thread. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... RSS feed for DD-WRT releases (2025) RSS feed for DD-WRT releases (2024) RSS feed for DD-WRT releases (2023)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I'm trying to surmise where the 1568 number came from per sir @lexridge outside of personal experience and extensive testing(?).
It came completely from trial and error. I took it down to a low number then starting increasing it until the devices stopped working 100% again, then I backed it off from that number (no idea what that was now). I never noticed any negative issues on other devices caused by lowering the frag threshold.
My issue was not the same as @strobes however. My devices would connect and report to Home Assistant just fine. My issue was trying to access the logs of said devices and/or send firmware updates, neither of which worked (time outs) until lowering the frag threshold via nvram set.
Also, make sure you have Legacy Rates (11b) disabled in 2.4ghz wifi advanced settings. This setting also greatly affects esp8266 devices connection reliability.
EDIT: Just checked this number on my MX4300 and I now have it set to 1538. I don't remember why I did that now, but I'm sure I had a good reason.
well, I was here long time ago and back because a "new" project where I can take advantage of this FW and it's flexibility. Did not have reason to dig under the hood. And it is changing so fast that difficult to keep up. My apology, it was intentional to sound obnoxious.
Of course the question was if the frame threshold still applicable after a year of changes. I guess I have my answers. And was interested to know if any one else may have similar experience.
