Supercharging Your Linksys Wireless Access Point
kwishot writes "Xam over at www.wi2600.org has documented a relatively simple way to 'turn up the juice' on your Linksys WAP11 Wireless Access Point." Caveats: the outlined method requires a Windows box, recent firmware, and (some) bravery, but no going inside the box or special hardware.
From what i can tell, this doesn't have to be a Windows only hack. The piece of software that Xam states is only built for Win32 seems to be nothing more then an SNMP manager. Now, the Win32 tool might make it a bit easier, but you can hardly call it "requires a Windows box".
I'm against picketing, but I don't know how to show it.
Well, since your phone is probably some analog deal that just blasts out your voice, I'd say upping the power on the access point will just add a bit more noise to your conversation (and probably not help too much in keeping the signal strong when you pick up the phone, although it should help a little).
A better hack might be to change the channel on your access point to something on the other end of the spectrum since you phone may not be taking up the entire band (unless it's a DSS phone). Or you might try moving your phone's base station and access point to opposite ends of the house.
PS: Whoever modded this as a troll: what were you thinking?
I read the internet for the articles.
Adding WaveLAN Extender - This article discusses adding various antennae to base stations to improve their range.
Extending TheAirPort's Range - This article discusses some more radical procedures, including some neat stuff with Directional Antennae which allow 802.11b to work as far away as a 57 Kilometers. They also discuss various antennae to add to laptops in order to improve their range.
- Vincit qui patitur.
First, I never did upgrade the firmware to 1.4g5 or 1.4g7, I am running 1.4H3. I guess I should upgrade, but that would require me to actually get the AP next to my PC for the USB connection. The upgrade seems to work OK without the latest rev as long as you can connect via snmp. I think I must have the 1.0 hardware since I got this thing Jan 2001.
Second, I think you can also turn off the SSID on your WAP using these utilities. I have not tried this but perhaps it could help if you are paranoid...
Finally, The main reason I worked on trying to fugure this out is because my wireless network was running very slow. I finally figured out the reason was the wpc11 linksys pcmcia card that I have. If you have one of these cards make sure to DISABLE the PowerSaveMode in your network configuration (in Windows). Your network will now run significantly faster (500K/sec instead of 50K/Sec in my case). Also when exploring in windows use mapped drives instead of unc names. This seems to also help.
Hope that helps, BRian
enterprises.atmel.atmelmib.atmelSys.TestModeSettin gsGRP.TestModeRadioConfiguration.0 = Hex: CA CA CA CA CA CA C9 C9 C9 C9 C9 C9 C9 C9
Although not in the same configuration as the article describes, this may be due to the fact that I've never upgraded the firmware on the access point I snmpwalk'd this from. Perhaps I should get busy on that....
Any of you people out there with an upgraded firmware, you should try snmpset under Linux or your UNIX of choice and see what kind of results you get... extra points for verifying the change with the Windows stuff in the article.
Numerically, snmptranslate says that the correct field is .1.3.6.1.4.1.410.1.1.8.8.0, assuming I'm using it right (I called it with the commandline snmptranslate -m +ATMEL-MIB -IR enterprises.atmel.atmelmib.atmelSys.TestModeSettin gsGRP.TestModeRadioConfiguration.0.)