Network Manager cannot connect to Unsecured wireless networks, unless...
Bug #60088 reported by
aubrey
This bug report is a duplicate of:
Bug #46136: ndiswrapper does not work with Network Manager.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
The Network Manager in Ubuntu stops working for wireless networks using ndiswrapper once I try connecting with WEP and selecting a wireless network from the drop down. Once I want to connect back to an unsecured network, I have to put any as essid (in network manager in ubuntu) and off in wep (which is not normal for new users). I think any and off should be the default for the network manager in Ubuntu.
Revision history for this message
| Scott Robinson (scott-ubuntu) wrote | #1 |
To post a comment you must log in.
This is a known and basically unfixable issue in Dapper. I would recommend upgrading to edgy, but bug 46136 prevents that. (and documents this problem too)
If you are using a bcm43xx, I recommend not using ndiswrapper and instead using the in-kernel drivers. They have their own share of problems (mostly power management) but work fine with all network types.