je viens d'installer la Kubuntu 8.04 et ma clé USB Ovislink basée sur le chipset ralink rt2570 est très bien supportée avec knetworkmanager. Tu as fais l'essai avec la version définitive ou avec une béta ?
en fait pour moi le soucis est que le driver présent dans le noyau ne fonctionne pas avec l'adaptateur USB de Linksys. Et c'est pour ça que je suis reparti sur le noyau non officiel de la version 7.10.
JerFirst, I have a small factual citoecrron to make for this article the RT3070 chipset is made by Ralink, not Realtek. And it's a very good chipset.I have the RT3070 chipset in my Alfa UBDo external wifi adapter and it works excellent with 2000 mW power and covers the N protocol as well. But the UBDo is an omni-directional antenna and my attempts to get into my local city's public wifi system were marginal (sometimes yes, for a little while, and sometimes no).So I bought an Alfa AWUS036NHR and an 18 dBi yagi antenna. The NHR model uses the Realtek 8188ru chipset (and the rtl8192cu driver in Linux). The unit functions perfectly good with Windows XP,. so I know there's no physical problem with the unit, and I know that the Windows driver works correctly in normal client usage. But there are lots of problems using this under Linux.Under Linux the monitor mode won't support channel changing. It's stuck on channel 1. So Kismet (my packet sniffer) won't work correctly. I don't know about injecting packets since I've never tried that.Even under normal client usage mode it won't lock up on APs that are fairly strong and steady under Windows. It acts like it's always on low power or something. The Realtek utility software in Windows has a selection box for three power modes. I haven't found any commands to access those modes in Linux yet, if the driver even supports power changing.I have searched the net and downloaded the newest drivers with patches that I could find. The latest mod date that I've tried is Feb 2013. And it still doesn't make any difference. I might have to buy another adapter and keep this one around until someone gets the Realtek 8192cu driver situation figured out for the 8188ru chipset.Reply
I only ask because you've cfusnoed me a bit I can understand that logic if you are turning down the TX power on your APs. However, if you are referring to the TX power on the clients I don't understand what bearing that has on roaming. The TX power of the client has nothing to-do with roaming it's the RX power of the signal from the AP that the client uses to determine if it should roam or not along with a host of other variables. Perhaps you're just turning down the TX power because of channel overlap and mobile device density? The variable of most importance will always be received signal strength. As the received signal from the original AP grows weaker and a station hears a stronger signal from another known access point, the station will initiate the roaming process. Thanks!
Hi Suner,Unfortunately I had to drop the D-Link adapter even with Fast rminaog enabled (85dB) the adapter seemed to throw fits from time to time. Initially we thought it might have to-do with the WPA/TKIP/802.1x configuration with Windows XP and the re-authentication as the STA roamed from AP to AP but even in a open network we had issues. While the adapter seems to work fine once your connected and in-mobile it was hit or miss once you started moving or if you just picked up walked 200 ft and tried to work again. It was definitely MUCH better behaved with Fast rminaog enabled but it was no where near where we needed it to be.We've since gone back and starting using the Netgear WDNA3100 which is based on an Atheros chipset. While this adapter might be a few more $$$ it appears to be much more consistent than the D-Link or Linksys adapters in terms of rminaog and even in terms of authentication time using WPA/TKIP/802.1x. Thanks for the comment!