Posted: Wed Jul 06, 2022 16:50 Post subject: No Afterburner option (ASUS WL-520gC)
Hi all, today I was configurating my router (ASUS WL-520gC), and I decided to enable Afterburner option, but it wasn't anywhere! "wl cap" command says next:
ap sta wet led wme 802.11d 802.11h rm cqa mbss4 afterburner acktiming
In Wireless > Advances settings there's no afterburner option, only "Frame burst". Please help me!
Your only option is probably frameburst unless you flash an antique build (14929); historical stable builds aren't necessarily relevant due to security patches since dinosaurs ruled the earth. That, and any issues cannot be fixed on current releases if they aren't being used.
Happy hunting. _________________ "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
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Wed Jul 06, 2022 19:33 Post subject:
Afterburner is this not currently Frame burst?
IDK what a firmware from pre stone age looked like or what "oxymorons" some labels were meant to represent in actuality corresponding to real functions, what I know is some portions generally speaking until recently have been way off mark where their label is concerned, and this issue has not been entirely resolved to a accurate technically speaking and non oxymoronic manner in all areas and such (even if already renamed) remain on the chopping block until they are accurate.
We all know that through the ice age and stone age, things were named differently, but they do have a real impact if supporting code exists.
Afterburner and Frameburst coexisted at one point in DD-WRT. Afterburner was a WRT54GS* and clone model-specific feature from the days of Tomato/HyperWRT/Stock firmware. Anyone's guess as to why it was removed from DD-WRT. _________________ "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
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Wed Jul 06, 2022 19:58 Post subject:
Seems at first google afterburner is WDS related and maybe just Broadcom related, we all know how Broadcom love to trademark bullshit buzz (words) names and apply non standards compliant nonsense to their Broadcrap.
Kinda helps if you share something to reinforce words. It was a Broadcom feature, yes, available in stock Linksys firmware. Don't know where you got the idea that it relates to WDS, but I'm always willing to be educated by someone with your vast experience.
It's easy to get confused in all the conflicting misinformation on the interwebs (especially in this forum). I'm not going to take the time to research if any of the Asus WRT54* clones were exact matches to the WRT54GS models that included SpeedBooster® (Afterbuner™) bits. I don't believe that Afterburner capability was even functional or working for any of the 802.11n chipsets (which is what devices were relevant in that forum thread you linked), but without specific datasheets that I'm reluctant to take the time to look up... well... _________________ "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
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Thu Jul 07, 2022 9:28 Post subject:
OK some minor research.
Afterburner or whatever other trademarked names are associated, is a Broadcrap proprietary implementation that requires compatible clients in order to see any actual benefits.
Quote:
It shortens the timing between packets to squeeze more data through the constraints of the 802.11g specification, up to 40 percent throughput
Broadcom claims the technology maintained compatibility with the 802.11 specification. But yet only client adapters with support were able to benefit from this.
So no point enabling something if client side support doesn't exist. Im not even going to bother Brainslayer with this, I can hear his words right now.
Now... The firmware Op is using is insanely outdated and out of support.
