Posted: Wed Jul 26, 2006 4:46 Post subject: Lower download speed with Afterburner enabled on WHR-HP-G54
I have updated the original firmware to DD-WRT V.23 SP2 Standard. I have changed the wireless transmitter output on the wireless side power to 10mw and modified boardflags setting in nvram to as suggested by the installation Wiki. Everything seems to be fine except the transmitting speed between my wireless client (Buffalo WLI2-PCI-G54s) and router on Wireless Status page in DD-WRT. Basically, the rate has been fluctuated from 5 ~ 11 Mbps with Afterburner enabled. But, it will be another story if I set it “disable” that it can keep the rate on 54 Mbps. To verify that difference, I have compared the download speed shown on Flashget.
Afterburner disabled: (tried 5 times)
Speed: 1,000 ~ 1,100 KB (that is basically the same as if using the wired connection)
Afterburner enabled: (tried 5 times)
Speed: 150 ~ 220 KB
I am so surprised and frustrated about the result. The HP model is designed to produce higher performance and speed. However, the fact is telling me that it is not the case. My impression is that I got a product with higher cost while having a lower expected performance. I will probably restore back the original Buffalo firmware to check this issue.
After the whole night trial and error using the method suggested by the above link, I got nothing to improving the speed except to resort to disable the afterburner. Now, I got 2 questions hoping the members here can tell me.
1) I found the DD-WRT show my router as WHR-G54S. I suspect that is it somthings to do to my poor speed? Other HP users can tell me how about yours?
2) I basically will try to restore back the original firmwire. But, it seems that there are no any hints on doing so from WIKI. Can I just update the original firmware through the GUI in DD-WRT? Or something else?
Joined: 12 Jun 2006 Posts: 244 Location: Costa Rica
Posted: Thu Jul 27, 2006 13:25 Post subject:
alexwai wrote:
2) I basically will try to restore back the original firmwire. But, it seems that there are no any hints on doing so from WIKI. Can I just update the original firmware through the GUI in DD-WRT? Or something else?
If you are getting wired speed without speedbooster, why are you trying speedbooster?
OpsCenter
I don't understand why the Buffalo claim HP model with the newer technology is faster than normal G product while it is not true in my case. Enabling afterburner will result in lower speed. Thus, I probably do something wrong and ask for help from all of yours guys.
If you are getting wired speed without speedbooster, why are you trying speedbooster?
OpsCenter
I don't understand why the Buffalo claim HP model with the newer technology is faster than normal G product while it is not true in my case. Enabling afterburner will result in lower speed. Thus, I probably do something wrong and ask for help from all of yours guys.
Afterburner NOT = the amplifier found in the HP model. You need to set the proper boardflags first for your HP unit to activate the amplifier. As for the Afterburner, well you gotta test it out first as sometimes it causes problems.
2) I basically will try to restore back the original firmwire. But, it seems that there are no any hints on doing so from WIKI. Can I just update the original firmware through the GUI in DD-WRT? Or something else?
If you are getting wired speed without speedbooster, why are you trying speedbooster?
OpsCenter
I don't understand why the Buffalo claim HP model with the newer technology is faster than normal G product while it is not true in my case. Enabling afterburner will result in lower speed. Thus, I probably do something wrong and ask for help from all of yours guys.
Afterburner NOT = the amplifier found in the HP model. You need to set the proper boardflags first for your HP unit to activate the amplifier. As for the Afterburner, well you gotta test it out first as sometimes it causes problems.
Adi
I have already mentioned on my 1st post and checked that the boardflags has been successfully activated.
Oh, wow, i just realised why my speeds were SO CRAPPY for my WDS link... The after burner was set to AUTO. As soon as i set it to Disable on both routers, the link went from a ghetto 11mbps to 48mbps !!
So, i would highly recommend to anyone to disable this thig.
Oh, wow, i just realised why my speeds were SO CRAPPY for my WDS link... The after burner was set to AUTO. As soon as i set it to Disable on both routers, the link went from a ghetto 11mbps to 48mbps !!
So, i would highly recommend to anyone to disable this thig.
But the afterburner thing and other tricks may not be optimized with this firmware...as it is just a trick, designed to win PR wars. I think that we have all given up on it and other items like it long ago.
If the unit works great without it, then 'why' is a valid question.
Oh, wow, i just realised why my speeds were SO CRAPPY for my WDS link... The after burner was set to AUTO. As soon as i set it to Disable on both routers, the link went from a ghetto 11mbps to 48mbps !!
So, i would highly recommend to anyone to disable this thig.
Adi
That's mean I am not alone.
Definetly NOT alone. I've been doing some more tests with this and it seems that WDS combined with WPA encyption and SpeedBooster ON = no go. As soon as i turn off Afterburner/SpeedBooster, WDS with WPA instantly starts working.. tested with final SP1.
Joined: 08 Jun 2006 Posts: 59 Location: Pittsburgh, PA
Posted: Thu Jul 27, 2006 20:18 Post subject:
Doesn't Afterburner only work with appropriate Buffalo wireless NICs? _________________ PittMesh, a Meta Mesh Wireless Communities project.
Mi parolas Esperanton.
Everything seems to be fine except the transmitting speed between my wireless client (Buffalo WLI2-PCI-G54s) and router on Wireless Status page in DD-WRT. Basically, the rate has been fluctuated from 5 ~ 11 Mbps with Afterburner enabled. But, it will be another story if I set it “disable” that it can keep the rate on 54 Mbps. To verify that difference, I have compared the download speed shown on Flashget.
I will probably restore back the original Buffalo firmware to check this issue.
