Re: [MLUG] Netgear MA111

[Ian Scott <EMAIL:PROTECTED>]

On Tue, Feb 03, 2004 at 04:30:33PM +0100, Robert West wrote:
> I don't really know.  I followed the tutorial from
> this list...
> 
> http://www.linuxquestions.org/questions/showthread.php?s=&postid=700104#post700104
> 
> Now on boot, right after bringing up eth0, it will say
> Bringing up interface wlan0, then fail saying it can't
> find the device.  It gives the same msg whether device
> is plugged in or not.

I've set up a D-Link Prism2-based WLAN adapter using the linux-wlan drivers.
I could only get things working bringing things up manually using
instructions from the README:

modprobe prism2_usb
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 lnxreq_autojoin ssid=<your APs SSID>
authtype=opensystem
ifconfig wlan0 <yourIP> netmask <yourNetmask> broadcast <yourBroadcast>
route add default gw <yourGateway>

I've got the feeling that you shouldn't be bringing wlan0 up explicitly like
your (assumed) hardwired eth0, and instead should rely on hotplug to load the
drivers and run the commands upon recognizing the USB device on
insertion/bootup.  There are scripts included in the wlan-ng distribution but
I'm not too sure on making them work.

Another option if this thing really is going to be plugged in all the time
would be to add an alias to your modules.conf file:
alias wlan0 prism2_usb
post-install prism2_usb /some/script/that/runs/wlanctl-ng.sh

This will cause the driver to be loaded and initialized when redhat tries to
bring up the wlan0 interface.

Ian
_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members