I have checked svn for changes between 46220 and 46446. Most of the changes that were made, were made multiple times so I could not track it down. Maybe I am missing something.
I would appreciate it if someone would also take a look.
@gamerHD, perhaps the wds issues are affecting different chipsets differently.
The last release with stable WDS for me is 47695, all releases after that are unusable for wds. But not necessarily dropping connections , latency and throughput just randomly go to hell. 47695 seems very stable
7800->9000, but also used an archer c7 v2 with samne results. i just retired that box.
@gamerHD, perhaps the wds issues are affecting different chipsets differently.
The last release with stable WDS for me is 47695, all releases after that are unusable for wds. But not necessarily dropping connections , latency and throughput just randomly go to hell. 47695 seems very stable
7800->9000, but also used an archer c7 v2 with samne results. i just retired that box.
True, might (probably does) differ. However from my testing it appears as if 3 routers suffer from the same issues on the same builds (2x WR841ND v8 and 1x WR1043ND v2)
Narrowed it down to the range of builds between 46220 (working good) and 46316 (disconnecting after a few hours). There are 5 builds in between. On SVN I saw a kernel update on 46309, so right now I'm testing the earliest before that which is 46301.
@gamerhd please test newest build
My initial testing - though the real test will be when i have ten more devices later, is showing much better consistency of latency on this build. @kernelpanic69 may be right.
Though 47695 is still a bit peppier, i havent been able to very quickly break it like i have earlier builds. Time will tell
Thank you. I will give the newest builds a try as soon as I can. Right now I went back 2 years since it is the most stable WDS setup so far I've discovered.
I've been running r48494 (latest at the moment), performance is very good, however the WDS connection uptime wasn't longer than 12 hours, had 2 disconnects.
So after not having a stable WDS connection between the AP's and Stations with all devices running the same r48494 build - I've downgraded the WDS Stations back down to r44715 (just a random pick of a build I know doesn't have the disconnect issues) But I kept the WDS AP running the latest r48494 build. So far almost 2 days of connection uptime between them.
Once again,
WDS AP is an Archer C7 v5,
WDS Station 1 is a WR1043ND v2,
WDS Station 2 is a WR841ND v8 (without a VAP).
So I'm guessing the issue could be narrowed down to WDS Stations having disconnect issues while WDS AP's are fine.
Beacon interval 100, DTIM 2, ack timing 1350. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
I have 48954 running Vanilla and the "airtime fairness" is off. I did read that this can cause problems post a change in the code for the vanilla firmware
Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Sat Jun 25, 2022 4:30 Post subject:
BS reverted the airtime fairness and power saving code somewhere around 49273 and vanilla drivers are working again with no latency and you can use airtime fairness or not...I prefer to use it to make sure no client can monopolize the wifi bandwidth. _________________ FORUM RULES