Hi all;

I installed SuSE 9.1 Pro. on IBM Thinkpad A31p and got a Cisco Aironet 350 wi
reless card to connect to linksys 802.11b router. I can get on to the internet,
but every time I have to log in as root and do the following

(a) ifdown eth0
(b) ifup eth1
(c) iwconfig eth1 key xxxxxxx

some time I have to repeat (c) a few time before I can connect to the internet.

(1) Is there a way I can put the above 3 steps in a startup file so that I do
not need to this evertime I power up?

(2) I installed the Cisco driver that I download from Cisco site, and every tim
e I try to invokes Cisco's ACU
I get a blink of some image and an error message "NO RADIO FOUND", does any one
know what does it means?

(3) from my window 2k I knew that the Cisco ACU firmware version number is V5.02.19

(4) Can any one who know how to get the Cisco Aironet ACU works please give me some tips.


Thank you.

I run (c) before (b), but I'm not sure if that matters or not. Also, I associate eth1 with an ESSID before running ifup.

1) I believe you can do that in the file where you have commands like:

iface eth1 inet dhcp

In Debian it's in /etc/network/interfaces. But I'm not doing that myself, so I'm not sure about the syntax... I don't connect a network at boot, instead I use a script to bring up eth0 or eth1 when I need to.

2) Hmm, have you loaded the airo module? I don't use ACU under Linux at all. Firmware updates are done under WinXP.

3) There is a newly released Linux package from Cisco with new firmware and new ACU. Make sure you have the latest. I'm running 5.30.17. The airo module in the latests kernel is supposed to be able to handle even newer firmware.

4) I use the above mentioned firmware with the airo module (kernel 2.6.8). eth1 is defined as in 1) Then I run:

iwconfig eth1 essid "someID"
iwconfig eth1 key xxxxxxx
ifup eth1

/TLV

TLV, many thanks. I will try it out.

In Yast under ...I think it's internet-> or network->harware-> then the card-your-using-> you should be able to configure everything you need. including your key(s)
It sounds like you have the module loaded at startup without the card in place -just guessing-(however eth0 should'nt block eth1 from working unless both are config.d to the same card) I have my card (ath0 in my case eth1 in yours) to start when 'hotplugged'. and if your not using eth0 just disable it or have it start 'when called' (it's a pull down list of choices of 'when to start').

hope that helped more than it confused.