Cisco Aironet 350 wireless in FC2-2.6.5

Rick Stevens rstevens at vitalstream.com
Tue Feb 1 17:30:01 UTC 2005 

Tapas Ranjan wrote:
> Hi :
> 	There is a little change to my last mail. I switch to 
> FC3 today, but has the same problem below. Please help.
> 
> On Mon, 31 Jan 2005, Rick Stevens wrote:
> 
> 
>>Tapas Ranjan wrote:
>>
>>>Hi :
>>>	I was trying to set up a Cisco wireless lan card on a dell 
>>>inspiron 2100 which has FC2 with 2.6.5 kernel version.
>>>	The card blinks with "modprobe yenta_socket" and xmit packets.
>>>But the Rx packet is always 0 and also it can't see the access point.
>>>After googling in for 3-4 hours, I couldn't get any solution to my 
>>>problem.
>>
>>I think I answered this in a previous posting by you.  If this is
>>related to your other question, PLEASE don't start another thread.
>>Just reply to your own posting and put in an "UPDATE" line in the body.
> 
> 
> 	This is completely a different problem. In the last one 
> everything works(at least manually), but for this one "NO". Probably
> the "UPDATE" word is better, but since I've started a new thread, please
> co-op with it.

Fine.

>>First, the vast majority of wireless cards under a 2.6 kernel are
>>"wlan0" rather than "eth1" but yours many be an exception.  We need
>>more details as to what kind of card it is.  Cisco makes a number of
>>wireless cards and since we don't know what kind it is, we can't
>>recommend which driver is the right one to use. 
> 
> 
>  	This is a "Cisco Aironet 350 series Wireless Lan Adapter".
> When I started the installation of FC2 with card inserted, it asked me
> whether to active "eth0, eth1, wifi0" devices during boot up. So
> that's how the "eth1" came.
> 	
> 
>>We need the output of
>>"cardmgr" or the contents of the "/var/lib/pcmcia/stab" file if cardmgr
>>is already running.
> 
> 
> The "cardmgr" is running and content of "/var/lib/pcmcia/stab" is :
> 
> Socket 0: 350 Series WLAN Adapter
> 0	network	 airo_cs  0 	eth1

Good.  It's using the airo_cs driver.

>>>	Since I don't have a "usb" drive with me write now, I am unable 
>>>to send you the "iwconfig eth1" results. If you need that with any other
>>>informations, I will be glad to send it to you. Hope to get some reply.
>>
>>You need to edit the /etc/sysconfig/network-scripts/ifcfg-eth1 (or
>>ifcfg-wlan0) file and make sure you have lines similar to:
>>
>>DEVICE=eth1 (or DEVICE=wlan0)
>>ONBOOT=yes
>>BOOTPROTO=dhcp
>>ESSID="youressid open"
>>
>>That is the ABSOLUTE MINIMUM for a wireless card.
> 
> 
> Absolutely perfect...I have everything already set. Here is what I see in 
> the same place.
> DEVICE=eth1
> BOOTPROTO=dhcp
> ONBOOT=no
> TYPE=Wireless
> NETMASK=
> DHCP_HOSTNAME=
> IPADDR=
> DOMAIN=
> HWADDR=00:09:7c:39:db:ad
> USERCTL=no
> PEERDNS=yes
> GATEWAY=
> IPV6INIT=no
> ESSID=tsubaki
> CHANNEL=1
> MODE=Auto
> RATE=11Mb/s
> key="s:2003ae0212 open"

That key is only 10 characters.  What WEP key size did you set up?
Most access point require AT LEAST a 64-bit WEP key (8 bytes or 16
characters), not a 40-bit, so check your access point's settings.
Remember also that an "s:" in the key tells the system it's an ASCII
string.  If your key is supposed to be in hex, remove the "s:",

> This is the result of iwconfig :
> 
> lo        no wireless extensions.
> 
> eth0      no wireless extensions.
> 
> sit0      no wireless extensions.
> 
> eth1      IEEE 802.11-DS  ESSID:"tsubaki"
>           Mode:Managed  Frequency:2.412GHz  Access Point: 
> FF:FF:FF:FF:FF:FF
>           Bit Rate=11Mb/s   Tx-Power=20 dBm   Sensitivity=0/65535
>           Retry limit:16   RTS thr:off   Fragment thr:off
>           Encryption key:****-****-**   Security mode:open
>           Power Management:off
>           Link Quality=0/160  Signal level=-107 dBm  Noise level=-91 dBm
>           Rx invalid nwid:1577  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:1614   Missed beacon:0
> 
> wifi0     IEEE 802.11-DS  ESSID:"tsubaki"
>           Mode:Managed  Frequency:2.412GHz  Access Point: 
> FF:FF:FF:FF:FF:FF
>           Bit Rate=11Mb/s   Tx-Power=20 dBm   Sensitivity=0/65535
>           Retry limit:16   RTS thr:off   Fragment thr:off
>           Encryption key:****-****-**   Security mode:open
>           Power Management:off
>           Link Quality=0/160  Signal level=-107 dBm  Noise level=-91 dBm
>           Rx invalid nwid:1577  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:1614   Missed beacon:0
> 	
> 	Here I don't have any idea from where this wifi0 is coming though 
> I have deleted it using network-conguration wizard. 

It's part of udev and the automatic hardware probe on boot.  I'd use it
rather than eth1, but it's your choice.  One of the issues you have here
is having two cards, so "ifdown" one of them.

> Result of ifconfig shows :
> 
> eth1      Link encap:Ethernet  HWaddr 00:09:7C:39:DB:AD
>           inet6 addr: fe80::209:7cff:fe39:dbad/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:820 dropped:0 overruns:0 frame:820
>           TX packets:43 errors:50 dropped:0 overruns:0 carrier:50

Notice the error counts on both.  On receive, they're all framing errors
and on transmit, they're all carrier errors.  That's because the card
isn't seeing the access point.

>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:15084 (14.7 KiB)
>           Interrupt:5 Base address:0x100
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:9628 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:9628 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:10498964 (10.0 MiB)  TX bytes:10498964 (10.0 MiB)
> 
> wifi0     Link encap:UNSPEC  HWaddr 
> 00-09-7C-39-DB-AD-F4-EF-00-00-00-00-00-00-00-00
>           UP BROADCAST RUNNING MULTICAST  MTU:2312  Metric:1
>           RX packets:0 errors:820 dropped:0 overruns:0 frame:820
>           TX packets:43 errors:50 dropped:0 overruns:0 carrier:50
>           collisions:0 txqueuelen:100
>           RX bytes:0 (0.0 b)  TX bytes:15084 (14.7 KiB)
>           Interrupt:5 Base address:0x100
> 
> 	As, I have said earlier you can see RX packets:0 all the time and 
> in iwconfig, it can't set the proper key. I tried to set the key manually
> but, no luck. Please help me out gurus...

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-   Errors have occurred. We won't tell you where or why.  We have   -
-                         lazy programmers.                          -
----------------------------------------------------------------------

More information about the Redhat-install-list mailing list