Networking :: Cisco Aironet 350 PCMCIA setup problems

According to the Wiki this card should work with little config but not for me although I'm convinced I'm pretty close.

The card is detected fine on boot and running netcardconfig seems to fire the card up - green status light is on and slight interference to speakers suggesting activity. However I can ping nothing at all.

ifconfig -a shows the eth0 interace itself and wifi0 as I believe this card does. Using the tool all parameters seem fine but no connection. Wlanconig prings up the 2 interfaces - setting the same parameters for each doesn't help.

Anything obvious I'm doing wrong? Should I be using netcardconfig or wlanconfig or both? If I do things manually should I be using ifconfig or iwconfig?

Thanks for any help.

I use this card daily without issues. I program it via iwconfig commands.

I do have some small recollection about versions of firmware being an issue with this card. When I plugged it into a windows box, the driver under windows flashed the card's firmware to a more recent but linux-buggy version.

It took me a while to realize that this was happening, but I finally figured it out, flashed the card to a compatible version and slapped a "linux only" sticker on it.

Hope this helps. The aironet is a fantastic card, with one of the most powerful antennas I've ever seen on a laptop wireless card. It's my "coffee shop card" of choice.

Thanks for that. I've read about the firmware issues and do remember upgrading it some time ago on a windows box. Any chance you can post your full settings for eth0 and wif0 and the exact procedure I need to go through in DSL (netcard config then iwconfig? iwconfig only etc) before I try the reflash.

I have DHCP switched off in boot options for static IP and WEP encryption.

Thanks again.

Don't forget to include the DSL version number that you are using.

No problem.

Here's what I'm using to connect to my 802.11b WEP'ed AP, sans my keycodes, essid, etc:

sudo iwconfig eth0 essid "youressid" key s:key1 [1] key s:key2 [2] key s:key3 [3] key s:key4 [4] mode managed ap APMACADDRESSHERE commit

And then a:

sudo pump

Should get you an ip address.

As I recall, most ap setups don't actually require all four keys to be specified. If that's the case with yours, just set the first key s:ASCIIKEY (or key HEXKEY) and leave off the bracketed numbers.

As a guess, it's probably the "commit" command that is tripping you up. A handful of cards require it, and the rest toss errors at you about it.

Next Page...
original here.