Scanning worked fine for me on my broadcom card via ndiswrapper (using the bcmwl5 driver).
Although it did lock up my machine every time I tried to switch networks after the initial connection, but that's another story. -j On Thu, 2005-12-15 at 12:07 -0800, Michael Blakeley wrote: > Dan Williams wrote: > > On Thu, 2005-12-15 at 09:28 -0800, Michael Blakeley wrote: > > > >>It almost works :-). The only WEP network I use is "closed" - that is, > >>it doesn't advertise its essid. So I have to set the essid manually, > >>from the command line. When I do that, "my-closed-network" shows up in > >>the nm-applet menu. If I select it, a gnome-keyring pops up to ask for > >>my password, and then nm-applet connects to the network and gets an IP. > > > > > > Which version of NetworkManager? > > > > This should work as long as you don't have a Cisco card as your main > > card. The Cisco firmware doesn't report the BSSID of hidden networks > > like other cards do. Therefore, we have no idea that the network is > > even present. > > > > If you do an 'iwlist eth<x> scanning', does the BSSID of your access > > point show up in the list? It will look something like: > > > > Cell 09 - Address: 00:06:25:E7:65:C5 > > ESSID:"" > > Protocol:IEEE 802.11b > > Mode:Master > > Channel:11 > > Encryption key:on > > Bit Rate:11 Mb/s > > Extra: Rates (Mb/s): 1 2 5.5 11 > > Quality=25/100 Signal level=-84 dBm > > Extra: Last beacon: 1476ms ago > > > > You might have to do a couple scans to get your AP in the list. If this > > doesn't work at all, what card, driver, and firmware version do you > > have? Hidden networks might usually take a few seconds to show up in > > NetworkManager, as not every AP is listed in every scan the card > > reports. Therefore, it takes a few scans to get a composite list that's > > complete enough to match the BSSID of your hidden AP with the BSSID > > we've got stored in GConf for it. > > $ apt-show-versions network-manager > network-manager/unknown uptodate 0.4.1+cvs20050817-0ubuntu4 > > My AP never shows up from a 'sudo iwlist wlan0 scan' at all - that's > kind of the point, as I understand it. If you don't know that it's > there, you can't access it. But I'm sure you know more about wifi than I do. > > My card is a broadcom, via ndiswrapper. Perhaps that's the problem? I > believe ndis (and thus ndiswrapper) doesn't support some scanning modes. > > $ lspci | grep 802 > 0000:02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g > Wireless LAN Controller (rev 02) > $ ndiswrapper -l > Installed ndis drivers: > bcmwl5 driver present, hardware present > > -- Mike > _______________________________________________ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list -- Jeremy Jongsma [EMAIL PROTECTED] http://jongsma.org _______________________________________________ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list