Starting on boot? Or even connecting automatically?
Harmon Seaver <[email protected]> Sat, 31 Dec 2005 23:31:08 -0600
| Newsgroups | gmane.linux.linux-wlan.user |
|---|---|
| Message-ID | <[email protected]> |
I'm running Debian 3.1 with a 2.6.14.5 kernel, and just upgraded both
primary and station firmware on my WUSB11 v2.5 wlan nic to the latest
applicable firmware, and also running the latest 2.3 linux-wlan driver.
Previously, when I was running Debian 3.0 and the 2.2 driver, wlan seemed to
connect to the AP without any special effort, other than having the correct
channel in the /etc/network/interfaces. Now, unless I give it a wlanctl-ng
command to connect to the actual essid and channel, it can't seem to find
any dns offer. Actually there are 3 ap's here it could connect to, but the
ifup wlan0 command doesn't do it, whether I do it as "wireless_mode managed"
or "wireless_mode ad-hoc" and even tho I've got the essid and the channel
set in interfaces. It only works with the wlanctl command.
Which, considering that it *did* work previously, seems weird. Also --
how can you make this work on boot? Unless I do the modprobe .... reset and
then the wlanctl....enable command by hand, the wlan doesn't come up at all,
even tho the module loads just fine.
--
Harmon Seaver
_______________________________________________
Linux-wlan-user mailing list
[email protected]
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user