After a lot of trial and error and *learning* I was able to get my
Linksys WUSB11 configured (downloaded drivers, installed,
etc.)..

Anyway, I have been able to connect to my LAN, and here's what I can
(and can't) do:

1) CAN ping the WAP/router/gateway, and 2 other Windoze 2K machines on
the wireless LAN from the Linux box

2) CAN ping the Linux box from both the 2 Win boxes

3) CAN NOT see the Internet from the Linux box

4) CAN NOT bring up the Linux box on the DHCP client listing on the
Linksys WAP/router

(NOTE: when I configured the WUSB11 as wlan0, I "hard coded" the
"next" IP address (192..168.1.102 -- I didn't see any way to set the
config of wlan0 for DHCP -- could that be the problem?)

Sorry if this is vague and general...it seems s-o-o-o-o close, I'm
hoping it's some minor "gothca" that someone can quickly direct me
to. If more info is required, I will gladly dump all that I have.

Any suggestions?

TIA....

Have you tried setting the gateway?

Of course replace 192.168.0.1 with your gateway's address. Also make sure the right DNS servers are listed in /etc/resolv.conf

yep...did that too...

it seems so-o-o-o close...

any other suggestions out there?

Should just be able to edit
/etc/sysconfig/network-scripts/ifcfg-wlan0

make sure you add any of the following lines not already there
GATEWAY=192.168.1.1
NETMASK=255.255.255.0
BROADCAST=192.168.1.255

with this you wont need to do route add

You can also add wireless parameter settings to this file, look at
ifup-wireless script in the same directory.

Also make sure you have (make sure you have ESSID and CHANNEL set to your values)

DEVICE=wlan0
BOOTPROTO=dhcp
ONBOOT=yes


MODE=Managed
ESSID=myessid
CHANNEL=6
KEY="restricted [1] XXXXXXXXXX"

Also don't forget to unhardcode the IP address of the machine.

well...
I went back and checked all that..everything seems to be in order.
Unless I manually set the IP address for this device, it sits there and blinks.
If I set the IP manually, it joins the network, and can ping (and be pinged by) other boxes on the LAN.
It just does not want to join the DHCP party.
Arrrggghhh...
Anything else I might be doing wrong?
Can I post specifics to help analyze?
Thanks!

Yeah, the following info would be helpful:

/etc/sysconfig/network-scripts/ifcfg-wlan0
/etc/hosts
/etc/resolv.conf
/etc/HOSTNAME

netstat -rn
ifconfig
iwconfig

Any chance you might share the step by step instructions you used to get this far. I cannot even get my WUSB recognized?

Well...

First I went to the www.linksys.com and downloaded the latest drivers tarball, and followed the instructions in the README to build and install the drivers.

After a lot of fiddling and asking about on newsgroups, wound up with the following file contents:

/etc/sysconfig/network-scripts/ifcg-wlan0
--------------
MODE=Auto
DEVICE=wlan0
BOOTPROTO=dhcp
DHCP_HOSTNAME=192.168.1.1
GATEWAY=192.168.1.1
PEERDNS=yes
NETMASK=255.255.255.0
ONBOOT=yes
ESSID=mylan1234
CHANNEL=9

Some quirkiness, though...

I put the following at the end of my /etc/rc.local

modprobe prism2_usb prism2_doreset=1
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 lnxreq_autojoin ssid=mylan1234 authtype=opensystem
route add default gw 192.168.1.1
dhclient wlan0

This is supposed to start up the wlan0 adapter on boot - but it doesn't... :-(

However, I persevere...

What I do is unplug the USB cable from the device, then plug it back in, and run thse same commands from a shell script, and that seems to work.

The USB adapter seems to lose its connection occasionally, and I do the same routine (unplug, re-connect, and run the shell script)

HTH...

And all comments and suggestions on how to make this less of a kludge would be appreciated...I know I have a lot to learn...I'm just happy to be on the LAN and Internet wirelessly!

I know WUSB11 v2.6 and v2.8 are both different Atmel chips, what version of the WUSB11 device do you have? Also check from the linksys site to see how current the driver it is and for what version.

I have v 2.5 of WUSB11 (Prism 2 chipset)

Check this:
http://lists.linux-wlan.com/pipermai...ry/003478.html

Also check /etc/modules.conf

from
http://leaf.sourceforge.net/devel/jn...ux-wlan-ng.txt

Q: My prism2.5-based USB adapter won't come up if it's plugged in at boot!

Thanks to buggy firmware, it is often necessary to perform a
device reset on initialization. You can perform this by adding
"options prism2_usb prism2_doreset=1" in your /etc/modules.conf

Intersil has released Primary firmware 1.1.2, which seems to
have resolved this problem, at least on our test machines.
Contact your vendor for a firmware update.

To check the firmware version, run: "dmesg |grep ident"