WUSB54GC and Ubuntu 7.10 situation

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4623

andersw

20-02-2008 06:19:28

Just to summarize my attempts to get this work flawless.

1) Just inserting the stick in vanilla 7.10 seems to work.
Can see APs, can connect APs, connecting to hidden APs works, connect to WEP enabled APs work).
UT, no IP communication possible over the link!

2) Downloaded the RT73 pack and compiled (and stripped) two days ago.
I can can't see any APs anylonger, but can connect to APs AND get a IP connection as long as I know the AP SSID etc. This with Networkmanager (manual configuration).
But I can't get it to work automatically at boot. iwconfig output looks ok and ifconfig output as well. But e.g. ping doesn't work. Need to go into Networkmanager and disable/enable the link. Then it works fine.

So, questions
1) Any way I can get both roaming mode AND TCP/IP to work at the same time?
2) What would the "right" combination of stuff be to get it to work during boot? Seen postings saying to disable networkmanager etc.

Regards
Anders

Spy84464

20-02-2008 18:39:08

Hello,

1) Any way I can get both roaming mode AND TCP/IP to work at the same time?[/quote10dkipjy]
Well, that should "just work". You said you installed rt73, did you disable the default driver before? Both drivers should not be loaded at the same time because that could lead to various issue. Post the output of "lsmod" if you're unsure.
2) What would the "right" combination of stuff be to get it to work during boot? Seen postings saying to disable networkmanager etc.[/quote10dkipjy]
Disabling NetworkManager could help, it doesn't work well with the legacy drivers (such as the one you installed), but solving the first issue could even more helpful.

Regards,
Romain

andersw

20-02-2008 20:31:35

Thanks for your quick response!

Hello,

1) Any way I can get both roaming mode AND TCP/IP to work at the same time?[/quote2bfaojtl]
Well, that should "just work". You said you installed rt73, did you disable the default driver before? Both drivers should not be loaded at the same time because that could lead to various issue. Post the output of "lsmod" if you're unsure.
[/quote2bfaojtl]
Yes, blacklisted all rt* that came with 7.10. Only rt73 loaded (and double checked with lsmod).
But I have ndiswrapper loaded (with a driver for a totally different chipset) since my tests with other cards. Can that interfere?


2) What would the "right" combination of stuff be to get it to work during boot? Seen postings saying to disable networkmanager etc.[/quote2bfaojtl]
Disabling NetworkManager could help, it doesn't work well with the legacy drivers (such as the one you installed), but solving the first issue could even more helpful.

Regards,
Romain[/quote2bfaojtl]
NetworkManager disabled. Wifi Radar "see" all available networks!
But wifi radar feels a bit "unstable" (latest version I found a few days ago and compiled).
What would you recommend if I would like a GUI based tool to configure my networks?
(I do move around a bit and hardcoding into files feel a bit cumbersome....)

Regards
Anders

stevenk

21-02-2008 00:18:32

Try using wicd, which is quite easy to configure. It is best suited if you have a lot of aerial networks and want to connect to a single one. You will have to disable network manager though...

StevenK

Spy84464

22-02-2008 21:07:05

Or RutilT, which is available in our download page. There have been some report about freeze on Ubuntu 7.10 though, but I don't know if it comes from the driver or RutilT, if you give it a try, thank you to tell me how things go.

Dunkirk

26-02-2008 16:24:39

I also can't get a Linksys WUSB54GC to inject reliably. I've done some injection, so I know that it CAN be done. But it's been very flaky. Sometimes it works; sometimes it doesn't, and I can't fathom what the differences are. I spent several hours last night trying different USB ports, on and off the laptop's base station, etc., etc.

This morning, I've wasted a couple hours trying different drivers. I'm running Gentoo on a 2.6.23 kernel (there IS no rt73 driver in it to get confused). I'm -- currently -- trying to run rt73-k2wrlz-2.0.1, but I've tried rt73-k2wrlz-1.1.0, 3 days worth of the the rt73-cvs-daily driver, and the old Dec06 drivers (referenced elsewhere). (I've even tried a 2.6.24 kernel in the Gentoo tree, but the rt2x00-cvs-daily drivers won't compile against it.)

Today, I can't get it to work even once. I was ready to return the card to the store, but reading through aircrack-ng's recommendation page again leads me to conclude that this is the best option out there! Maybe the RTL8187L-based Alfa's might be better, but they seem to be twice the money (and have a wicked antenna...).

The problem is so bad that not even the rutilt applet can fix it. I can bring up the utility, tick the box that says "Injection in monitor mode," close the app, restart it, and the flag is cleared again. It simply won't stay on.

Yes, I use Network Manager, but I have it completely shut down for this testing. But -- and I would claim this in a court of law -- yesterday, I was injecting for HOURS with Network Manager running, and my ndiswrapper-based Broadcom 4312 active (though not used).

When it's worked, I haven't had to fool with iwpriv. Injection just worked when I put the card in monitor mode. I'm pretty sure that the only times I've had it working were with the rt73-cvs-daily driver, but, like I said, I can't get it working with ANY driver today.

Needless to say, I'm about ready to pull my hair out with this nonsense.

I guess it's not outside the realm of possibility that the card has just gone bad, since it seems to have "sloped off" till today, when it won't work at all. But the card seems to work just fine in general. I can see networks in Network Manager when I've got it in "managed" mode. If the chip were bad, I sure wouldn't think that would be the case.

So I'm at a loss. I've done a debug build of the driver, but it doesn't seem like there's anything interesting in there. But, hey, what the heck do I know about it? Any suggestions on how I sort this out?

IvD

26-02-2008 17:43:32

I've even tried a 2.6.24 kernel in the Gentoo tree, but the rt2x00-cvs-daily drivers won't compile against it.
[/quote3oz3rcoy]

2.6.24 already contains the rt2x00 driver, so no need to compile the cvs tarball against it.

Dunkirk

26-02-2008 19:52:22

Yeah, I tried to use that one too, and it wouldn't do injection either. -)

IvD

26-02-2008 20:01:54

well rt2x00 depends on mac80211 for injection support, and I do believe mac80211 has implemented support for it.
Though I am not sure from which version the support was added...

Dunkirk

26-02-2008 20:58:06

Well, you're getting at something that has been confusing me. I was just about to spend some "quality time" trying to figure out the difference between the IEEE802.11 and the MAC802.11 stuff. Maybe I'm getting conflicts trying to have support for bc43xx, ndiswrapper, and rt73 in the same kernel. Can all of these be active at the same time? Which ones use which stack? If not, which are mutually exclusive?

IvD

26-02-2008 21:00:17

You can use both stacks at the same time,
I am not sure about the broadcom drivers but I do believe there is a mac80211 version in the 2.6.24 kernel.
Note that they have a ieee80211 _and_ a mac80211 version and there were several kernels where both of those drivers were present.

Dunkirk

26-02-2008 21:04:56

Which one is the direction going forward, and which one is going to get phased out?

IvD

26-02-2008 21:06:04

ieee80211 is phased out, mac80211 is there to stay. All wireless drivers are encouraged to use mac80211.

Dunkirk

28-02-2008 02:13:52

Well, I bought what I thought was an Atheros-based PC Card, and it turned out that I got a "v2", which, of course, was based on a completely different chip, so I need to take that back. However, on a whim, and while I was at it, I tried out the latest CVS build of the rt73 legacy driver, and I got injection working 3 out of the 4 times I tried. I need to play a little more, but this is definitely better!

Dunkirk

28-02-2008 10:14:59

So I did some more testing. The thing that's really foxing me about this situation is that -- as a laptop -- I'm going to try to be injecting packets when I'm running on battery. I've been having major trouble getting this going. However, if I shut down the "laptop-mode" service (on Gentoo, remember), I seem have some luck in getting injection working. It seems to work about half the time.

For those who may be wondering, I'm talking about pushing the card into a USB slot, bringing it up and testing, then bringing it down, unloading the module, pulling the card and restarting the process. Nothing else is changing. I've tried to blame it on slots or using the USB extension cable that came with the card, but, no, it's really just that flaky.

Again, is there any sort of debug information I could be getting from the driver that would make fixing this possible for the developers?