Linksys WUSB11 (no version number)

[CSciCT]

My best guess is that it is version 1.0 or 2.0. I haven't been able to confirm that though. I do know it is the model with an internal antenna. I'm trying to get it working under Redhat 8.0 (2.4.20-19.8).

Device Info:
Model - WUSB11
FCC ID - PKW-WUSB11
Chipset - Atmel AT76C503A
Radio - Intersil (not RMFD)

I downloaded the last version of the driver source that will still support Intersil radios from http://atmelwlandriver.sourceforge.net/downloads.html which is CVS build 2002-12-09. Had no problems building the module. I can configure the adapter with either the included tool (lvnet) or also with iwconfig. I know the adapter can see the access point/router (Linksys WRT54G Firmware: 1.30.7) because iwconfig reports the MAC for the router, signal quality, and signal strength. The module is aliased to eth1 (I have a NIC set to eth0). And I've given it a static IP (Disabled DHCP on the router). My problem is when I go to ping the router, I get back Destination Host unreachable.

Any advice would be appreciated, Thanks in advance.

[CSciCT]

Perusing the FCC database and looking at external photos revealed that it is infact version 1.0 of this model. Which is what I guessed based on the lack of a version number on the product itself. I looked at internal photos of it as well, however I couldn't make out anything that will confirm the chipset identity. So basically I'm going on what I've read online about the earlier versions of the WUSB11 containing Atmel chipsets. And the fact that I'm currently using an Atmel driver and it sees my access point. What gets me is that from this device's release, Linksys has been supplying people with a driver for a chipset that isn't even in the device. I am aware that other versions of the device actually do contain the Prism2 (uses linux-wlan-ng driver) chipset. I'm just slightly annoyed that Linksys didn't know any better for version 1.0. Still no luck with pinging the access point. I'm wondering if it is a problem with the driver, or a bad network configuration setting.

[swiftnet]

I had bad luck with the earliest atmel drivers, but it sounds like you're almost there.
Some silly questions/points, you probably have it all set correctly, but it is usually something silly after you go through the gruelling stuff.

encryption on?
if it is, turn it off on both the ap and the usblinksys - if it connects then turn it back on

is it in managed mode?
with an ap it has to be managed mode

is the default route set?
set it to your gw

Essid correct?
I know, but a typo can cause manual hair loss

[plattypus1]

My reccomendation- if you bought this from a dealer, then go back to them, tell them it's unsupported, and get one of the prism2-based widgets. As far as I've heard Atmel cards are sketchy at best.

I've got a WPC11, the latest version, with the prism2 chipset. It works like a charm.

Good luck to ya!

[CSciCT]

First things first, I got it working! But not with the Atmel driver. A group of guys at http://at76c503a.berlios.de/ have built a driver from scratch, and it works wonderfuly, and is much easier to set up than the Atmel driver.

plattypus1,
My dad bought this adapter a year or two ago (up until now we had it hooked up to a windows machine). So unfortunately taking it back wasn't an option. But believe me, I did consider buying a newer one that runs the Prism2 chip.

swiftnet,
Settings were correct, I went over them several times. I wasn't using encryption, knew it had to be in managed mode to use an ap, default gateway was always set to the router/ap's internal ip, and the essid I left as the router's default. As you have probably noticed, not too worried about security, as the signal barely reaches outside my house (old house, too much crap in the walls).

Thanks for the good suggestions, but I think the root of the problem laid within how the module initiated the networking device (eth1). I probably should have known better than to trust a CVS snapshot to perform error free, but it was the latest "version" that supported Intersil radios. But it's working now, and if any of you out there have Atmel based adapters, I would recommend moving to the alternate drivers, especially if your device has an Intersil radio, because their driver still supports them.

The next problem I'm trying to tackle is getting the adapter configured at boot time, but I'm a bit unfamiliar with the order in which things get initialized. In order for my setup to work properly, I would need the order to proceed as follows:

Load modules for USB interface
Load modules for WiFi adapter
Start networking support (ifcfg-eth0, ifcfg-wlan0)
Set firewall rules (for masquerading)

Right now the firewall is setup as a service (chkconfig --level 345 etc...) but if I need to I could probably start it in rc.local. For all I know, this is how things will be initialized and I don't have to worry about it, but if anyone knows for sure, don't hesitate to let me know.

But anyways, thanks again for your help, it was very much appreciated.