On Tue, Oct 21, 2008 at 10:27:16AM -0400, Brian J. Murrell wrote: > On Tue, 2008-10-21 at 05:51 -0600, Otto Solares wrote: > > On Mon, Oct 20, 2008 at 11:36:08PM -0400, Brian J. Murrell wrote: > > > FWIW: my AP and the wireless client are two feet away from each other. > > > > RF saturation? > > Well, it's not a problem for the Linksys or Tomato firmware. Why should > it be a problem for b43?
Tomato with the proprietary bcm-wl driver under 2.4 kernel have enough differences to Kamikaze with the b43 driver under 2.6 kernel enough to investigate if the TX power differs and if it is causing RF saturation. I think your worst problem is that you don't have an open mind to debug all the possibilities, I was just trying to help you solve your problem but with that attitude is really hard. I administer like 150 WRTs and belive me the most insignificant and obvious problem is your worst enemy. > You never answered my request for a copy of your working OpenWrt > firmware. That would be the most straightforward way to eliminate all > these non-quantifiable variables. I just can share you my pwnx0r edition which I use at the University (where I'm the sysadmin) to pen-test our networks. This version differs slighty with Kamikaze HEAD in that we use the 2.6.25.18 kernel instead of the 2.6.25.17 and the 2 extra patches from aircrack-ng, one for the mac80211 to support fragmentation and the other to b43 for speeding the injection. Beware this version doesn't have a DHCP server and is filled with penetration software. http://home.galileo.edu/~solca/openwrt/openwrt-brcm47xx-pwnx0r.trx I just test it with a WRT54GSv3 and it works correctly too. If you want really rock solid stables APs suitable for production environments you should go with my custom firmware patch: http://forum.openwrt.org/viewtopic.php?pid=47293 -otto _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
