If I had any hair I would have pulled it out by now.

I am running redhat 8.0 on an IBM T22 with a Cisco aironet 350 card. Using a dlink di713p as the wireless router. No problems with this configuration under XP so I know I don't have a hardware problem. ifconfig shows eth1 (which is the wireless card) with an associated address (it also shows high rx and tx errors - clearly, something is wrong with the config). iwconfig shows good info as well - correct essid, mode, and bit rate. Using the built in eepro 100 I downloaded and installed the newest cisco firmware for the card and the acu utility. ACU sees the card and tells me it is not associated. Looking at /proc/driver/aironet/eth1/Config I see that the channel is not correct (should be 2, shows up as 6). I modified BOTH the /etc/pcmcia/wireless.opts and /etc/sysconfig/network-scripts/ifcfg-eth1 with the correct info (not sure which one is used) but the channel still shows up wrong. Added entry in /etc/pcmcia/config.opts just to be on the safe side - that did not help either.

Any ideas on what I am missing to get this card to associate correctly? I think I just need to get the right channel defined at boot, but not sure.

Thanks for the help.

i dl'd acu v2.0 and pcmcia-cs-3.2.3 which is asked for in the acu install routine , cwinstall. i know my hardware works via w2k, but no go in rh8 stock install. sometimes i get an association in acu but the mac for the association comes up all 0's.

eth1 will come up in ifconfig with no ip. driving me nuts.

still searching for the solution...

success! used help from el kid and finegan in other threads on this subject. particularly , ran sh kpciinstall. also used the acu to confirm ssid and chanell. also used dhclient to get the ip lease. it seems as soon as the card associated with the base station all was well. you can tell if you are associated via iwconfig.

good luck and thanks all.

Hi siculars,

if I understood your post correctly, you are not using WEP encryption...
If you do, could you please outline how you got this to work....

Cheers,
Michael

Check the man page on iwconfig, its rock steady one of the better written man pages out there. But basically after you have the card recognized:

iwconfig ethX enc 12321312321

That's all,

Cheers,

Finegan

thanks Finegan,

well, tried that already... well, it seems that to use
128 bit encryption, the Cisco AP 1200 needs to have 26
hex digits.... and using the exact 26 dgits on the card
does get me associated, but dhclient fails getting an IP
address...

Cheers,
Michael

If its possible, can you turn off WEP and make sure its not on the driver side, I've got two threads going on the aironet 350, a card I haven't used in a long long time, actually I may have been using a 340, and besides the kernel driver, there is the binary-esque driver from Cisco and their config utility for Linux... I'm not certain of this, but I remember a while back something about WEP being set to firmware. My one 3 hour play session with aironet I had, I found that I didn't have to do that, although I might have been setting iwconfig settings to the clouds as the laptop I was borrowing was a dual boot, and the win side had already been set to talk to the same wireless LAN, hence, the card might have had firmcoded into it already the WEP key for that wlan.

These kids are usually so out of the box that I forget they're on the market, because I never get threads on them.

Check into the binary tools from Cisco, if you can't find 'em, I'll track them down. Normally I would do this and just post a link, but work sucks today.

Cheers,

Finegan

Whoops, ignore the above, the poster in the other thread figured it out, same card, same distro, same driver, same problem, just an odd iwconfig setting:

http://www.linuxquestions.org/questi...082#post215082

Cheers,

Finegan

thanks a lot again Finegan... you put me on the right track int the first place, saying that the Cisco driver is not needed at all ... and that's how I got it to work, plainly iwconifg .... I've posted the details on the other thread I am afraid..... but the trick was that I had to issue a:
iwconfig eth1 rate auto

to get me associated .... and the everything else was fine.
The only thing I realized is that the Firmware on the card needs to be 4.25.30, a higher version will cause the card not to be recognized,
with a lower version WEP encryption will not work the way is should
with the build in driver in RH8.

Yes, you're right , in former times the WEP key was written to the card, but that's not true anymore nowadays....

Cheers,
Michael ;-)

sorry finegan.... that was me posting to the other thread .....

Didn't want to confuse you !

Cheers,
Michael

I am a little late to this thread but the discussion seems relevant to my problem. I have a PCI Aironet 350 and I want to use it with a desktop PC runnig RH 7.2. I downloaded the latest drivers from Cisco.com and followed the various instructions for installing the driver for the PCI card. Everything seems to go as indicated in the documentation, the module airo.o is built and with insmod airo it gets loaded (lsmod shows it). However, the driver does not seem to recognize the card. The card LED's are as follows: green=off amber=on. This should be indicating problems with the driver according to the documentation. The ACU utility says "radio is disabled" and does not even show the Firmware version in the Status menu - i.e., the driver clearly can't "see" the card.

I have not been able to figure out what the problem is. I am not that experienced in installing new modules so I may be missing something.

Any