On Thu, Aug 16, 2012 at 4:25 PM, Bastian Bittorf <bitt...@bluebottle.com>wrote:
> > am on a WRT54GS. > > > > I tried: > > iw dev wlan0 set bitrates legacy-2.4 6 9 12 18 24 36 48 54 > > are you in adhoc or ap-mode? > I am in ap mode. > > > Should I be making the equivalent "iw set bitrates" on the client > > machine as well (I have a laptop connected to the router)? > > yes, ofcourse. otherwise it doesnt make sense, > because it seems that the situation will come up, > when mudulation changes (fast) between OFDM and > non-OFDM. (e.g. 11 vs. 12mbit or 5.5 vs. 6 mbit) > I tried the same bitrate setting on my linux laptop. It seemed to last much longer before eventually stalling. I configmed that the bitrates stayed within the desired set. By constantly running "iwconfig wlan0" on the laptop to see the current bitrate for the connection. It may be still eventually stalling because I am not on the latest development snapshot, so I will upgrade and try again. > > > If so that may not be practical since not all of my client > > machines > > are on linux (my wife's windows laptop, and my tivo doesn't expose > > advanced wireless config). > > but you can hardware them to 802.11g IMHO > I never thought of that. I'll see if I can find a way to do that. > > > Also, you mention putting "wifi up" in a cron script. Does doing > > that > > sever already extablished connections? So if I did this in the > > middle > > of a large file copy, would it break the connection? > > no, it will just continue, you can take this for a start: > http://intercity-vpn.de/files/openwrt/cron.minutely_checkwifi.sh > > Thanks for your cronscript. I will definitely try this. It may be enough to keep it working well enough until a real fix is here. > > I wonder if a temporary solution might be to hack the b43 driver > > such > > that it would refuse to change from g to b speeds regardless of > > client > > settings. I'm no kernel dev, but it might be worth toying with. > > yes, that would be a "solution" but i think thats not (easy) > possible: the decoding is done in hardware IMHO, but > maybe its enough to say in the beacons "i can only speak x.y" > > > One more question: What build of openwrt are you using? I am on > > Backfire 10.03.1, r29592. Perhaps I should be trying this trick on > > a > > development snapshot instead. > > yes, we are using recent trunk, e.g. r32764 or newer. > > bye, bastian > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
