The Cisco 350 card is recognized but I cannot activate it. I read somewhere that this has to be done manually, whatever that means. Any help would be appreciated.

Val

I think the old module package from cisco around the 2.2.x kernels required some hinkiness to get the card running. If the modules airo and airo_cs (I think that's the right pair), show up under the command:

/sbin/lsmod

Then it should just be a matter of ifconfig'ing the card up and giving it the "iwconfig" commands for your network... What happens with those?

Cheers,

Finegan

Thanks finegan, but I am a Linux newbie and don't know how to do what you suggest. I am on XP now and will not be able to follow instructions, but I will certainly write them down.

Oh, no problem... here's a little more step by step:

/sbin/lsmod will list all of the currently loaded modules. A module is driver support for some hardware/filesystem/doodad that wasn't compiled directly into the kernel.

One of the cute things about pcmcia is that you know the driver loaded and bound to the card when you hear two identically pitched beeps during startup.

ifconfig eth0 up

Will bring up the device if its the only ethernet device onboard. For instance if you have a normal 10/100 based whatever built-in, then the wireless card will most likely get assigned eth1.

iwconfig eth0 essid blahblahblah

Will configure the card to talk to the wireless network blahblahblah. You might want to check the man page on iwconfig, its actually well written unlike many others. Mostly you'll be worried about the arguments: "essid" and "enc".

Then manually invoking the dhcp client will probably grab a lease:

dhcpcd eth0

Then you should be connected, there's a hundred ways to automate all of that goop, post back if it works or where things get hung up, something might be different about your aironet card, but I doubt it.

Cheers,

Finegan

Thanks again finegan. The laptop is an IBM with built in ethernet plus a PCMCIA wireless card. RH8 recognizes both. I will do what you suggest and post back.

finegan,

1. /sbin/lsmod gives the following (among more data):

airo_cs 0 unused
airo 0 [airo_cs]
ds 1 [airo_cs]
yenta_socket 1
pcmcia_core 0 [airo_cs ds yenta_socket]
eepro 100 0

2. The two beeps are there, so the card is recognized at startup.

3. lconfig eth0, lconfig eth1, iwconfig eth0, iwconfig eth1 all give "command not found" message.

4. /etc/init.d/pcmcia restart is OK

5. When leaving network configuration, this message appears:
"eht1 has an alias to module airo_cs in modules.config, instead of currently loaded module airo!"

Val

1. cool, all there.
2. cool, working.

3. You have to be root, and if you used su to become root, you're going to need to type out the full path to the command, i.e.:

/sbin/iwconfig

or possibly (different by distro and I don't know RH's hijynx):

/usr/sbin/iwconfig

ifconfig should always be: /sbin/ifconfig

Or, better, use "su -" This will re-log in you entirely as root and all of those commands should work fine without the full path. /sbin means system binaries, stuff not normally usuable by a user, so they're not in a normal user's path. When you use 'su' to become root, you normally keep the old user's path. (this is a recent annoyance added to the bash shell)

Also "ifconfig", not "lconfig".

4. good.

5. Dunno what that'll mean in the long run, probably RH building stupid aliases for devices and not remembering that pcmcia handles stuff differently.

Cheers,

Finegan

Super thanks, finegan and sorry for my "lconfig" mistake. Yes, I have been doing all this in a terminal as root.

Number 5: I forgot to say that the message first appeared when rebooting after I had removed eth1 by mistake.

I will do ifconfig and iwconfig again with full paths.

Val

The procedure described by finegan actually worked for me, thanks !

The only thing is that it seems to be only working when using no encryption.

As soon as I enable 128 bit encryption on the Access Point I can still associate with it, but I don't get an IP address anymore via dhclient eth1.

It seems that the encryption mechanism used by the RH8 driver is different or not understood by the AP.

Any comments and hints welcome.

If iwconfig can't set the encryption right for you, you might want to try the actual utility from cisco. I've only ever gotten to play with an aironet once, and that was on a borrowed machine where iwconfig worked... so I dunno:

iwconfig eth0 enc 21321321321

Then check iwconfig again to see if you have a signal, or are getting a ton of invalid crypt frames that the laptop can't decrypt as its key doesn't truly match.

Cheers,

Finegan

Thanks again Finegan,

that's exactly what I see, a lot of crypt frames ....

Any thoughts where to go from here ?

Cheers,
Michael

It seems that I am making progress.... the critical part was setting the rate to auto ....
I am using a Cisco 350 card, Fw: 4.25.30!
Access-Point is also Cisco 1200 AP, Fw: 11.50

The following works, order of commands is critical:

after boot, logged in as root:
1. iwconfig eth1 rate auto
2. iwconfig eth1 essid [your SSID ]
3. iwconfig eth1 enc [26 hex characters ]

After this, you should see something like....

[root@localhost root]# iwconfig eth1

eth1 IEEE 802.11-DS ESSID:"natuschka"
Mode:Managed Frequency:2.412GHz Access Point: 00:02:8A:0E:365
Bit Rate:11Mb/s Tx-Power=17 dBm Sensitivity=0/65535
Retry limit:16 RTS thrff Fragment thrff
Encryption key:****-****-****-****-****-****-** Encryption modepen Power Managementff
Link Quality:14/10 Signal level:-43 dBm Noise level:-256 dBm
Rx invalid nwid:17412 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:3465 Missed beacon:0

the most important info here is the Access Point MAC address, because anything other than FF:FF:FF:FF:FF:FF:FF:FF means : YES you are associated!

ANd now, final step is :
dhclient eth1

and you're on air !

The above post is spot on. Thanks.

Now, how do I make redhat use that config on boot (or ifup) ?

Right now, ifup eth0 causes redhat to trample all over that config and I have to go through the iwconfig and dhclient steps above by hand...

Edit:

/etc/sysconfig/network-scripts/ifcg-eth0

with all of the specific iwconfig info.

Cheers,

Finegan

Thanks.