network-manager-0.6 branch is broken with rt61

Bug #53788 reported by Simon Ruggier
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

It's kind of hard to be specific about the problem when dealing with a high level tool like network manager, so all I can say is that I've used 0.6 with bcm43xx, and it works, but it was periodically disconnecting. If I try to use 0.6 with ndiswrapper, it inexplicably fails to connect, it just stays with both circles being gray untl it times out. Today I downgraded to 0.5 on the suggestion of this page: https://help.ubuntu.com/community/WifiDocs/NetworkManager , and it can connect using ndiswrapper. This would imply that the newer version broke that.

I've also tried and failed to get 0.61 working with rt61, but I haven't tested downgrading it yet. The only way I've managed to get rt61 working so far is by running dhclient ra0 while nm-applet is trying to connect, however. I don't know enough about using wireless from the command line to figure out a better way.

edit: downgrading network-manager to 0.5 worked with rt61 as well.

Also, note that I'm using the latest rt61 from http://rt2x00.serialmonkey.com/wiki/index.php/Downloads, because nm doesn't seem to recognize the ralinktech rt61 that ships with Dapper

Simon Ruggier (simon80)
description: updated
Simon Ruggier (simon80)
description: updated
Simon Ruggier (simon80)
description: updated
Revision history for this message
Steve Alexander (stevea) wrote :

I'm seeing the same problem with a Sitecom WL-171 (RaLink RT2561/RT61), and NetworkManager Applet 0.6.4.

I can use the wireless network just fine if I connect using dhclient ra0. However, I can't get network manager to actually connect, even if I run dhclient while it is trying to connect.

Revision history for this message
Steve Alexander (stevea) wrote :

Why is this bug report a duplicate of bug #48473? That bug report is about using WPA supplicant, whereas my wireless network is entirely open.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.