I've used the ndis driver to use the Windows drivers for my Broadcom 802.11g card. The driver seems to load and work fine, but when I try to configure the essid with iwconfig, it doesn't work. Nothing happens. If I try to use dhcpcd on the wlan0 interface, it fails, and the interface goes down.Unfortunately this is the problem with using ndiswrapper, it is not fully functional and so you run into problems like this. I have found that using ndiswrapper with the same driver i can't:
Is there anybody out there who could shed some kind of light on this? If you need more information (log files, config files, etc.) let me know.
-Hyrum
use wavemon
scan for ap's reliably
use dhcp to atuomatically set things up (i'll explain)
set the essid to something other than default if there is not an ap with that essid with a strong signal
Basically what i have found is that in order to effectively use ndiswrapper you have to set up everything by hand. If you try to use dhcp before you have changed the essid or network type then it will look on the default essid and find no address so it will shutdown the interface. What you need to do is have an access point in range with a strong signal, then iwconfig everything so that the Mode is set to the correct thing, the key is set up correctly and then you change the essid, and THEN you can dhcp an address and it will work. If you don't have everything set up properly and try to change something such as essid and there is not an essid that corresponds to your settings then it will blink at you and do nothing.
Sorry it's such a pain but i guess that is what we get for using windows drivers in a linux world.
-Chris
____________________
BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
