[SOLVED] Wireless connection w/Aironet 340
Posts: 7
Well, I haven't tried everything, but I've tried what should have worked. I'm trying to make my wireless connection work with a Cisco Aironet 340 pcmcia card.
I can make both my eth1 and wifi0 connections show Connected status by using MEPIS Network Assistant to set them to static IP addresses, but they don't function. While "connected", I can't even ping my gateway.
Here is some info for you while MEPIS Network Assistant has settings of Manual, use DHCP for DNS, my SSID and WEP encryption key are defined correctly, my eth1 interface is set to start on boot and when plugged, my wifi0 interface is not set to start at all. Eth1's status is Started but failed to connect, wifi0's status is Was not started.
Here we go:
I'm using Simply Mepis 6.5.02_32 loaded on my hard drive.
root@2[neighbor]# uname -a
Linux Sager 2.6.15-27-desktop #1 PREEMPT Sun Mar 11 21:36:14 EDT 2007 i686 GNU/Linux (###The date and time are not correct)
root@2[neighbor]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:90:F5:08:63:B1
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0x3200
eth1 Link encap:Ethernet HWaddr 00:40:96:2A:06:28
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:3826 dropped:0 overruns:0 frame:3826 ### Dropped packets??
TX packets:1029 errors:366 dropped:0 overruns:0 carrier:366
collisions:5901 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:609076 (594.8 KiB)
Interrupt:3 Base address:0x100
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:190 errors:0 dropped:0 overruns:0 frame:0
TX packets:190 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19007 (18.5 KiB) TX bytes:19007 (18.5 KiB)
root@2[neighbor]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11-DS ESSID:"2WIRE970" Nickname:"default" ### 2wire970 is my router.
Mode:Managed Frequency:2.442 GHz Access Point: 00:19:E4:07:DA:A1
Bit Rate:11 Mb/s Tx-Power=15 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Encryption key:****-****-** [4] Security mode:open
Power Management:off
Link Quality=100/100 Signal level=-28 dBm Noise level=-95 dBm
Rx invalid nwid:14334 Rx invalid crypt:4779 Rx invalid frag:0
Tx excessive retries:366 Invalid misc:8467 Missed beacon:0
wifi0 IEEE 802.11-DS ESSID:"2WIRE970" Nickname:"default"
Mode:Managed Frequency:2.442 GHz Access Point: 00:19:E4:07:DA:A1
Bit Rate:11 Mb/s Tx-Power=15 dBm Sensitivity=0/65535
Retry limit:16 RTS thr:off Fragment thr:off
Encryption key:****-****-** [4] Security mode:open
Power Management:off
Link Quality=100/100 Signal level=-28 dBm Noise level=-95 dBm
Rx invalid nwid:14334 Rx invalid crypt:4779 Rx invalid frag:0
Tx excessive retries:366 Invalid misc:8467 Missed beacon:0
### eth1 and wifi0 always seem to have identical configurations. I'm not sure which one is primary or if I should have them both activated. I've tried all combos.
root@2[neighbor]# lspci | grep -i network
root@2[neighbor]# ndiswrapper -l
airplus : driver installed
bcmwl5 : driver installed
bcmwl5a : driver installed
lsbcmnds : driver installed
lsbcmnds6 : driver installed
lstinds : driver installed
mrv8k51 : driver installed
netr33x : driver installed
prismnic : driver installed
wlanuig : driver installed
wlipnds : driver installed
root@2[neighbor]# dhclient
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/eth1/00:40:96:2a:06:28
Sending on LPF/eth1/00:40:96:2a:06:28
Listening on LPF/eth0/00:90:f5:08:63:b1
Sending on LPF/eth0/00:90:f5:08:63:b1
Listening on LPF/wifi0/
Sending on LPF/wifi0/
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 2
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
root@2[neighbor]# iwlist eth1 scanning
eth1 Scan completed :
Cell 01 - Address: 00:19:E4:07:DA:A1
ESSID:"2WIRE970"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=100/100 Signal level=-27 dBm Noise level:-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
root@2[neighbor]# uptime
01:14:59 up 1:48, 1 user, load average: 0.01, 0.10, 0.15
root@2[neighbor]# ping 192.168.0.1
connect: Network is unreachable
To me, it seems like I'm attempting but failing to communicate with DHCP. It should be noted that I can pick up an IP address just fine through my wired interface eth0, and through eth0 I can be fully operational network wise. Oh, and I'm not attempting to have eth0 and eth1 active simultaneously.
Sorry my tone tonight is not more amicable. I will truly appreciate any help you can give me and will thank you profusely if I can get it up and running.
Aironet 340
Posts: 7
Thanks for the info. My time is already obligated for the Labor Day weekend but I will be getting back on this as soon as I can after Monday. I hope you have a good weekend too.
jst
Up and Running
Posts: 7
So it appears the problem was indeed the firmware, however the solution had some bumps in it. It turns out the linux script provided at the referenced site called a couple programs by (old) version number, and my Mepis distribution's versions of those programs were newer so the script kept bombing out. Not knowing what other problems installing the older versions would create, plus not even having access to the older versions through the package manager, I decided not to dig that hole deeper.
Sadly, I replaced the Aironet 340's firmware with the Windows 98 version via the Cisco utility on a Windows laptop. Then I inserted the card into my Mepis laptop, powered it on, and it came up like a champ.
Thank you very much for turning me on to the actual solution. I like the Mepis distribution very much.
jst
Would you care to send this
Posts: 2299
Would you care to send this to dev-at-mepis.org. Might be interesting for Warren.
Newbie or not Newbie, there's always a question
Forwarding
Posts: 7
I would not object at all. Hopefully one day it might save someone else some grief.
jst
As of 2007.08.03, this is
Posts: 1634
As of 2007.08.03, this is Cisco's recommendation for your particular WLAN client card:
http://www.cisco.com/warp/public/102/wlan/linux.html
See also: http://www.goonda.org/wireless/aironet/
How's my posting?
Please call: 1-800-DEV-NULL