LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 02-14-2005, 01:28 PM   #1
henry_huckem
Member
 
Registered: Jan 2005
Distribution: Mandrake Linux 10.1
Posts: 34

Rep: Reputation: 15
Aironet 350 (PCI) and FC3, can't connect?


Hello-
I have a Cisco Aironet 350 PCI WiFi card and I am running Fedora Core 3. I cant seem to get it to work for some reason. I have gotten so far as to have the card recognized and initialized so it shows up as 'active' in my network devices screen, so I am assuming that is a good thing. My problem is this: I can't seem to get it to connect to my network at all... I have tried using NetworkManager, and it only sees my network sometimes, other times all it sees are my neighbors networks (which I also cant coonect to) lol. I dont really like the Network Manager interface, so I would like to use the ACU client utility from Cisco. I have downloaded the the source for this program and it tells me that I need to install libraries that I KNOW FOR A FACT are already installed. I downloaded the 2 rpms for the libs its asking for and installed those yesterday, and they appear in the list when I got ->sytem settings ->syste logs->RPM's. Here is the error I am getting:

ldcmd ldconfig
Checking for libsigc++ ...
libsigc++ not installed.
Checking for gtkmm ...
libgtkmm not installed.

The libraries can be downloaded from the web.

Sources are available from sourceforge.net (projects gtkmm and
libsigc++). Be sure that you download the correct versions (1.2.10
of gtkmm and 1.0.4 of libsigc++). You must install libsigc++ before
you can install gtkmm.

RPM packages of the libraries can be obtained from freshrpms.net.


Sooo.... I'm kind of at a loss. I guess I dont really understand what it is I have to do (IE: what info I need and what I have to tell my system) in order to connect my Linux Box to my network... Sure is frustrating cause I bought this card specifically for the system and I really want to get the linux machine online so I can download all the updates and such and get it all up to date so I can get my 3d card working. Long Story.

So in closing, if anyone knows what to do, please, let me know. What I need is really some step by step directions on how to connect my Linux machine to an existing network using FC3 and a Cisco Aironet 350 PCI WiFi card. SOMEBODY PLEASE HELP!!!!!!!


Thanks in advance for any advice.

-matt
 
Old 02-14-2005, 02:26 PM   #2
darkleaf
Senior Member
 
Registered: Jun 2004
Location: the Netherlands
Distribution: debian SID
Posts: 2,170

Rep: Reputation: 45
Have you set your essid and then tried connecting to it with DHCP or setting your numbers manually?

With "iwconfig interface essid ****" you set the essid **** on interface you have your card connected to. Then you can try to use "dhcpcd interface" to connect and get the settings from your access point.
 
Old 02-14-2005, 06:21 PM   #3
henry_huckem
Member
 
Registered: Jan 2005
Distribution: Mandrake Linux 10.1
Posts: 34

Original Poster
Rep: Reputation: 15
IWAS setting them manually as DHCP always failed to get the numbers on startup. when I do the iwconfig interface **** command, do I enter eth0 or wifi0? Both are set up to use the card I have installed. thanks for your help
 
Old 02-14-2005, 09:03 PM   #4
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 19,591

Rep: Reputation: 3508Reputation: 3508Reputation: 3508Reputation: 3508Reputation: 3508Reputation: 3508Reputation: 3508Reputation: 3508Reputation: 3508Reputation: 3508Reputation: 3508
PCI or PCMCIA ???
I have an old PCMCIA 350 card for my laptop on RH9.
Driver updates render this useless under Linux. I dual-boot that laptop, and if I allow Windows to update the ACU it automatically updates the firmware. Dead card under Linux.
I keep an old copy of the firmware around to rectify this when it happens.
Haven't checked to see if a fix has shipped in the last couple of years, but the doco on the web site still looks awfully similar.
 
Old 02-15-2005, 07:02 AM   #5
darkleaf
Senior Member
 
Registered: Jun 2004
Location: the Netherlands
Distribution: debian SID
Posts: 2,170

Rep: Reputation: 45
You have to use the interface you choose. If you don't have a particular reason to have those two interfaces for one card you can safely delete one.
 
Old 02-21-2005, 08:02 PM   #6
Stormproof
LQ Newbie
 
Registered: Aug 2002
Location: Slackware, KS
Distribution: Slackware
Posts: 12

Rep: Reputation: 0
henry. the easy way out would just be to install suse 9.2 and it would recongnize your card right off the bat.

Even slackware 9.1 will recongnize your card right off as well. I know this because I have 2 systems on my LAN that are using the PCI 350 card.

I have tried Fedora 2 in the past and had some issues however I did get lucky enough to make it work. What you need to do is try your best to find the missing rpms

Here they are

1.2.10 gtkmm
1.0.4 of libsigc++

Search google, good luck

If you find them I would excute the install similiar to this. rpm -Uvh gtkmm1.2.10 libsigc1.0.4

If you get them install, try running the cisco driver install process again. You might see some errors during the install however I ran into them as well but the card still worked. If everything works

search for the acu file and execute it.

If you had no luck try suse 9.2 or slackware 9.1 They will work with no problems guarenteed.

Last edited by Stormproof; 02-21-2005 at 08:04 PM.
 
Old 02-24-2005, 03:56 PM   #7
jmacdone
LQ Newbie
 
Registered: Feb 2005
Posts: 1

Rep: Reputation: 0
Google to the rescue again. The tip/script here worked with my mini-pci 350 v 4.95.08. This works with a "hidden" SSID. However, I haven't tried it with WEP yet.

https://bugzilla.redhat.com/beta/sho...?id=109394#c20
 
Old 04-14-2005, 08:23 PM   #8
philng
LQ Newbie
 
Registered: Apr 2005
Posts: 1

Rep: Reputation: 0
Hi there, I've managed to get them (Cisco 350 PCI with FC3) running after installing the 2 libs (from Sourceforge) + ACU + driver (from Cisco) and configuring the WEP and SSID on ACU. However, I also need to run a self-written scriipt to re-install the ACU after every reboot, otherwise it just wouldn't associate with the AP.

And yes, Suse 9.x works seamlessly indeed.

Phil. Ng
 
Old 05-11-2005, 01:43 PM   #9
msncookie
LQ Newbie
 
Registered: May 2005
Posts: 1

Rep: Reputation: 0
I had a very similar problem with that card which only happened with FC3. It turned out to be WEP related. For some reason, after I removed the WEP requirements on my access point, it started working. More strange, I added the WEP key back to my AP and things continued to work. Some point after removing WEP from my access point, everything suddenly started working.

I've never had that problem with any other Linux distro on that laptop. Just Fedora 2 and later. (I never tried anything older). I've used Redhat, Mandrake, and SuSE, all without trouble.

 
Old 09-18-2005, 01:53 AM   #10
mrperkins
LQ Newbie
 
Registered: Jun 2004
Location: Columbia Missouri
Distribution: SuSE 9.1
Posts: 23

Rep: Reputation: 15
disable wep

As perverse as it may sound, after all this time, you might have to disable wep for your wireless network. I have the same card and spent about 9 hours reading bits and pieces on the web until I found that suggestion. It works. I had the same problem with Fedora 2, and I am running Fedora 4 now.

One posting I found said that you can go in and redo your network wep security after the fact and the card will still work after configuring for the new key.

I have a netgear router but it is probably not related to that. I think it is an old RedHat bug which is still there.

I read another posting that described the bug but it was supposed to be fixed with a kernel upgrade. It isn't.

So, I now have Fedora 4 on a dual-boot IBM R40 and it works fine but my network is unsecured. I will try to fix that tommorrow.

I was ready to go out and buy a new wireless card.

Mike

Last edited by mrperkins; 09-18-2005 at 01:55 AM.
 
Old 01-25-2006, 01:17 AM   #11
legonz
LQ Newbie
 
Registered: Jan 2006
Posts: 3

Rep: Reputation: 0
Quote:
Originally Posted by philng
Hi there, I've managed to get them (Cisco 350 PCI with FC3) running after installing the 2 libs (from Sourceforge) + ACU + driver (from Cisco) and configuring the WEP and SSID on ACU. However, I also need to run a self-written scriipt to re-install the ACU after every reboot, otherwise it just wouldn't associate with the AP.

And yes, Suse 9.x works seamlessly indeed.

Phil. Ng
Hi. Would share what you exactly did to make it work. I have a similar problem with Aironet 350 on RHEL4-ES running on a notebook.

Thanks.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
FC3 and Cisco Aironet 350 sfunk1x Linux - Wireless Networking 12 12-13-2005 11:19 AM
Issues with RH FC3 and Cisco Aironet 350 ka9rqw Linux - Wireless Networking 4 01-05-2005 08:39 AM
RH 9 and Cisco Aironet 350 austindad Red Hat 3 02-07-2004 10:37 AM
aironet 350 anomalie Linux - Networking 1 01-22-2004 10:15 AM
350 Aironet...Again mrant Linux - Laptop and Netbook 0 08-25-2003 07:27 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 01:16 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration