This is a new Centos 5.1 install on a HP nc2400 (that use to run XP). Completely clean install; blew away the XP partitions...
After applying all the updates, and configuring for the rpmforge repo, I used yumex to install dkms and the dkms-ipw3945, ipw3945-firmware, and ipw3945d rpms.
lsmod|grep ipw shows:
ipw3945 180391 1 ieeee80211 33417 1 ipw3945
and dmesg)grep ipw shows:
well a bunch of lines about the card including one with the Radio Frequency Kill Swithc is On
But the card does not show in Network Manager.
I added to modprobe.conf: alias wifi0 ipw3945 and rebooted (and power cycled) and no change.
ifconfig wifi0 up gets: device not found
Oh, this notebook has a Broadcom ethernet adapter that is working just fine at bootup
But I have to get the wireless working today! Well maybe by tomorrow. (off to IETF next week, and IEEE 802 the following).
ANy help would be greatly appreciated!
On Wed, Mar 5, 2008 at 9:30 AM, Robert Moskowitz rgm@htt-consult.com wrote:
This is a new Centos 5.1 install on a HP nc2400 (that use to run XP). Completely clean install; blew away the XP partitions...
After applying all the updates, and configuring for the rpmforge repo, I used yumex to install dkms and the dkms-ipw3945, ipw3945-firmware, and ipw3945d rpms.
lsmod|grep ipw shows:
ipw3945 180391 1 ieeee80211 33417 1 ipw3945
and dmesg)grep ipw shows:
well a bunch of lines about the card including one with the Radio Frequency Kill Swithc is On
Check to see if the physical switch is turned on. As long as the system thinks the Kill Switch is on it won't show up in Network Manager. [Having spent an hour debugging this a couple of months ago.] Basically it comes down to the first question of support: Is it plugged in? At the moment the computer does not think so.
Progress...
Stephen John Smoogen wrote:
On Wed, Mar 5, 2008 at 9:30 AM, Robert Moskowitz rgm@htt-consult.com wrote:
This is a new Centos 5.1 install on a HP nc2400 (that use to run XP). Completely clean install; blew away the XP partitions...
After applying all the updates, and configuring for the rpmforge repo, I used yumex to install dkms and the dkms-ipw3945, ipw3945-firmware, and ipw3945d rpms.
lsmod|grep ipw shows:
ipw3945 180391 1 ieeee80211 33417 1 ipw3945
and dmesg)grep ipw shows:
well a bunch of lines about the card including one with the Radio Frequency Kill Swithc is On
Check to see if the physical switch is turned on. As long as the system thinks the Kill Switch is on it won't show up in Network Manager. [Having spent an hour debugging this a couple of months ago.] Basically it comes down to the first question of support: Is it plugged in? At the moment the computer does not think so.
There is NO physical switch. XP had some way of enabling the radio. So I went into the bios and played around a bit. Tried an option and now NetworkManager sees the card!
But when I enter my WPA passphrase, I keep going back to being asked for the passphrase :(
I noticed that NetworkManager is using eth1 for the the wireless interface, not wifi0 that I put into modprobe.conf (alias wifi0 ipw3945).
I tried to use wpa_supplicant deamon as I do on my nc4010 that has an atheros pci card. man wpa_supplicant lists ipw as a valid device, but when I supply this, i get
Unsupported driver 'ipw'
SO why does it not like my passphrase that works just fine with my nc4010 and its ahteros card? Granted theweak passphrase I am using fails password checkers, but still.....
Or how to use wpa_supplicant instead of NetworkManager (which is pretty cool, where is its config files).
On Wed, Mar 5, 2008 at 9:17 AM, Robert Moskowitz rgm@htt-consult.com wrote:
Progress...
There is NO physical switch. XP had some way of enabling the radio. So I went into the bios and played around a bit. Tried an option and now NetworkManager sees the card!
But when I enter my WPA passphrase, I keep going back to being asked for the passphrase :(
I noticed that NetworkManager is using eth1 for the the wireless interface, not wifi0 that I put into modprobe.conf (alias wifi0 ipw3945).
I tried to use wpa_supplicant deamon as I do on my nc4010 that has an atheros pci card. man wpa_supplicant lists ipw as a valid device, but when I supply this, i get
Unsupported driver 'ipw'
SO why does it not like my passphrase that works just fine with my nc4010 and its ahteros card? Granted theweak passphrase I am using fails password checkers, but still.....
Or how to use wpa_supplicant instead of NetworkManager (which is pretty cool, where is its config files).
Not sure if this helps but might be worthwhile reading the forum thread at:
http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Moskowitz wrote:
ANy help would be greatly appreciated!
I'm using the ipw3945 on CentOS 5.1 with the following packages:
ipw3945d-1.7.22-4.nodist.rf ipw3945-firmware-1.14.2-1.nodist.rf dkms-ipw3945-1.2.1-1.nodist.rf
I installed mine using this:
yum install dkms-ipw3945 NetworkManagerDispatcher chkconfig --level 345 NetworkManager on chkconfig --level 345 NetworkManagerDispatcher on
After installation, reboot your laptop and your wireless adapter should now be seen by the NetworkManager application in Gnome. You can click on it and then connect to it in the taskbar on the right-hand side. I was successful at connecting to a WRT54G at G speed using WPA2 Pre-Shared Key Only and AES encryption algorithms.
This is all that was needed to install and connect to the wireless network. Also, the card is seeing 4 different neighbor's wireless connection points, so it's probing and searching appropriately.
Not sure if this helps you or not.
Regards, Max
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Max Hetrick wrote:
This is all that was needed to install and connect to the wireless network. Also, the card is seeing 4 different neighbor's wireless connection points, so it's probing and searching appropriately.
Also, mine shows up and works as eth1 and not wifi0.
Regards, Max
Thanks for helping.
Max Hetrick wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Moskowitz wrote:
ANy help would be greatly appreciated!
I'm using the ipw3945 on CentOS 5.1 with the following packages:
ipw3945d-1.7.22-4.nodist.rf ipw3945-firmware-1.14.2-1.nodist.rf dkms-ipw3945-1.2.1-1.nodist.rf
Save rpms off of rpmforge. Installed this morning.
I installed mine using this:
yum install dkms-ipw3945 NetworkManagerDispatcher
NetworkManager was part of the base install.
chkconfig --level 345 NetworkManager on chkconfig --level 345 NetworkManagerDispatcher on
I did this via the gnome services app, turning on all runlevels so I could activate 3,4,&5
After installation, reboot your laptop and your wireless adapter should now be seen by the NetworkManager application in Gnome.
I got to this point. Had to play around with the bios for the radio to come on at boot. I think the item that did this was NOT to enable LAN power management.
You can click on it and then connect to it in the taskbar on the right-hand side. I was successful at connecting to a WRT54G at G speed using WPA2 Pre-Shared Key Only and AES encryption algorithms.
My AP is WPA1 with TKIP. Even if I select TKIP (not go the auto route), I am not getting connected.
This is all that was needed to install and connect to the wireless network. Also, the card is seeing 4 different neighbor's wireless connection points, so it's probing and searching appropriately.
I should probably turn on one of my other APs. I do have a lot of them here when needed....
Not sure if this helps you or not.
Just tells me it is my problem, not a general problem. Good to know it works for someone!
Where does NetworkManager keep its information? There was no /etc/sysconf/network-scripts/ifcfg-eth1 file. I made one (but don't know how to get PTK passphrases into the file). No change.
ARGH!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Moskowitz wrote:
Where does NetworkManager keep its information? There was no /etc/sysconf/network-scripts/ifcfg-eth1 file. I made one (but don't know how to get PTK passphrases into the file). No change.
I'm not sure mine stores anything anywhere. Every time I connect it asks me for my passphrase information when I attempt to connect.
When I go home and turn the wireless on, I can search my logs to see if it's storing that anywhere and get back to you.
Regards, Max
thanks but I have a hunch....
Max Hetrick wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Moskowitz wrote:
Where does NetworkManager keep its information? There was no /etc/sysconf/network-scripts/ifcfg-eth1 file. I made one (but don't know how to get PTK passphrases into the file). No change.
I'm not sure mine stores anything anywhere. Every time I connect it asks me for my passphrase information when I attempt to connect.
Not good if you have a really good passphrase! You can be more secure if the passphrase is kept protected on your system and is hard to enter, than have one that is 'easy'to remember and enter.
When I go home and turn the wireless on, I can search my logs to see if it's storing that anywhere and get back to you.
What is NetworkManager using for its 802.1X supplicant code?
I think I can see that it cannot be teh wpa_supplicant. It only supports the ipw2200, I have figured out. Not the ipw3945. So I will uninstall that. The xsupplicant rpm? or something internal?
BTW, I turned on an AP with no security, and connected right to it with NetworkManager. This really tends to narrow my problem to WPA support.
More data....
Robert Moskowitz wrote:
thanks but I have a hunch....
Max Hetrick wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Moskowitz wrote:
Where does NetworkManager keep its information? There was no /etc/sysconf/network-scripts/ifcfg-eth1 file. I made one (but don't know how to get PTK passphrases into the file). No change.
I'm not sure mine stores anything anywhere. Every time I connect it asks me for my passphrase information when I attempt to connect.
Not good if you have a really good passphrase! You can be more secure if the passphrase is kept protected on your system and is hard to enter, than have one that is 'easy'to remember and enter.
When I go home and turn the wireless on, I can search my logs to see if it's storing that anywhere and get back to you.
What is NetworkManager using for its 802.1X supplicant code?
I think I can see that it cannot be teh wpa_supplicant. It only supports the ipw2200, I have figured out. Not the ipw3945. So I will uninstall that. The xsupplicant rpm? or something internal?
BTW, I turned on an AP with no security, and connected right to it with NetworkManager. This really tends to narrow my problem to WPA support.
I yum erased wpa*
this not only removed wpa_supplicant and wpa_supplicant_gui, but also NetworkManager and its gnome interface. I then
yum install NetworkManager*
This added wpa_supplicant back in.
rebooted.
I can connect to the AP with no security, but not the one with PSK Passphrase (which needs wpa_supplicant). And the man pages only lists ipw2200, not ipw3945.
So I am suspecting that there is no wpa support for my card?????
On Wed, 5 Mar 2008 at 3:09pm, Robert Moskowitz wrote
I yum erased wpa*
this not only removed wpa_supplicant and wpa_supplicant_gui, but also NetworkManager and its gnome interface. I then
yum install NetworkManager*
This added wpa_supplicant back in.
rebooted.
I can connect to the AP with no security, but not the one with PSK Passphrase (which needs wpa_supplicant). And the man pages only lists ipw2200, not ipw3945.
So I am suspecting that there is no wpa support for my card?????
I've used WPA with my 3945 card (in a ThinkPad Z61t) on both Fedora 7 w/ ipw3945 and Fedora 8 w/ iwl3945. So, it can work. On F7, I did the whole config manually (I don't use any DE, so I tend to have to do things this way) -- including editing /etc/sysconfig/network/ifcfg-eth1 to have the correct ESSID and editing /etc/wpa_supplicant/wpa_wupplicant.conf with my PSK. I'm *guessing* that would work for you.
I don't know how to get it working with NM -- sorry.
Joshua Baker-LePain wrote:
On Wed, 5 Mar 2008 at 3:09pm, Robert Moskowitz wrote
I yum erased wpa*
this not only removed wpa_supplicant and wpa_supplicant_gui, but also NetworkManager and its gnome interface. I then
yum install NetworkManager*
This added wpa_supplicant back in.
rebooted.
I can connect to the AP with no security, but not the one with PSK Passphrase (which needs wpa_supplicant). And the man pages only lists ipw2200, not ipw3945.
So I am suspecting that there is no wpa support for my card?????
I've used WPA with my 3945 card (in a ThinkPad Z61t) on both Fedora 7 w/ ipw3945 and Fedora 8 w/ iwl3945. So, it can work.
Good news, that.
On F7, I did the whole config manually (I don't use any DE, so I tend to have to do things this way) -- including editing /etc/sysconfig/network/ifcfg-eth1 to have the correct ESSID and editing /etc/wpa_supplicant/wpa_wupplicant.conf with my PSK. I'm *guessing* that would work for you.
I copied my wpa_supplicant.conf file from my nc4010 that has an atheros card (but did not use NetworkManager). My key and everything was in the file and works perfectly on the nc4010. Not hte nc2400 with the ipw3945...
I don't know how to get it working with NM -- sorry.
On Wed, 5 Mar 2008 at 4:35pm, Robert Moskowitz wrote
Joshua Baker-LePain wrote:
On F7, I did the whole config manually (I don't use any DE, so I tend to have to do things this way) -- including editing /etc/sysconfig/network/ifcfg-eth1 to have the correct ESSID and editing /etc/wpa_supplicant/wpa_wupplicant.conf with my PSK. I'm *guessing* that would work for you.
I copied my wpa_supplicant.conf file from my nc4010 that has an atheros card (but did not use NetworkManager). My key and everything was in the file and works perfectly on the nc4010. Not hte nc2400 with the ipw3945...
You may also want to have a look at /etc/sysconfig/wpa_supplicant and make sure that it is set up correctly.
Joshua Baker-LePain wrote:
On Wed, 5 Mar 2008 at 4:35pm, Robert Moskowitz wrote
Joshua Baker-LePain wrote:
On F7, I did the whole config manually (I don't use any DE, so I tend to have to do things this way) -- including editing /etc/sysconfig/network/ifcfg-eth1 to have the correct ESSID and editing /etc/wpa_supplicant/wpa_wupplicant.conf with my PSK. I'm *guessing* that would work for you.
I copied my wpa_supplicant.conf file from my nc4010 that has an atheros card (but did not use NetworkManager). My key and everything was in the file and works perfectly on the nc4010. Not hte nc2400 with the ipw3945...
You may also want to have a look at /etc/sysconfig/wpa_supplicant and make sure that it is set up correctly.
Joshua Baker-LePain wrote:
On Wed, 5 Mar 2008 at 4:35pm, Robert Moskowitz wrote
Joshua Baker-LePain wrote:
On F7, I did the whole config manually (I don't use any DE, so I tend to have to do things this way) -- including editing /etc/sysconfig/network/ifcfg-eth1 to have the correct ESSID and editing /etc/wpa_supplicant/wpa_wupplicant.conf with my PSK. I'm *guessing* that would work for you.
I copied my wpa_supplicant.conf file from my nc4010 that has an atheros card (but did not use NetworkManager). My key and everything was in the file and works perfectly on the nc4010. Not hte nc2400 with the ipw3945...
You may also want to have a look at /etc/sysconfig/wpa_supplicant and make sure that it is set up correctly.
Define 'correctly' Mine has:
# wlan0 and wifi0 # INTERFACES="-iwlan0 -iwifi0" INTERFACES="-iwlan0" # ndiswrapper and prism # DRIVERS="-Dndiswrapper -Dprism" DRIVERS="-Dndiswrapper"
On Wed, 5 Mar 2008 at 5:32pm, Robert Moskowitz wrote
Joshua Baker-LePain wrote:
You may also want to have a look at /etc/sysconfig/wpa_supplicant and make sure that it is set up correctly.
Define 'correctly' Mine has:
# wlan0 and wifi0 # INTERFACES="-iwlan0 -iwifi0" INTERFACES="-iwlan0" # ndiswrapper and prism # DRIVERS="-Dndiswrapper -Dprism" DRIVERS="-Dndiswrapper"
If you're using ipw3945, you're *not* using ndiswrapper. That should be
DRIVERS="-Dwext"
Joshua Baker-LePain wrote:
On Wed, 5 Mar 2008 at 5:32pm, Robert Moskowitz wrote
Joshua Baker-LePain wrote:
You may also want to have a look at /etc/sysconfig/wpa_supplicant and make sure that it is set up correctly.
Define 'correctly' Mine has:
# wlan0 and wifi0 # INTERFACES="-iwlan0 -iwifi0" INTERFACES="-iwlan0" # ndiswrapper and prism # DRIVERS="-Dndiswrapper -Dprism" DRIVERS="-Dndiswrapper"
If you're using ipw3945, you're *not* using ndiswrapper. That should be
DRIVERS="-Dwext"
Where is this documented?
And what for the Interface line?
YES!!!!
Joshua Baker-LePain wrote:
On Wed, 5 Mar 2008 at 5:32pm, Robert Moskowitz wrote
Joshua Baker-LePain wrote:
You may also want to have a look at /etc/sysconfig/wpa_supplicant and make sure that it is set up correctly.
Define 'correctly' Mine has:
# wlan0 and wifi0 # INTERFACES="-iwlan0 -iwifi0" INTERFACES="-iwlan0" # ndiswrapper and prism # DRIVERS="-Dndiswrapper -Dprism" DRIVERS="-Dndiswrapper"
If you're using ipw3945, you're *not* using ndiswrapper. That should be
DRIVERS="-Dwext"
YES!!! this did it.
And I got prompted for a password for the gnome-keyring that was created to hold my passphrase.
Next week it will be trying to get onto the secure wireless at the IETF meeting, instead of the insecured... (BTW, all the secured wireless does there is stop wireless attacks. Does not stop IP level attacks).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Moskowitz wrote:
What is NetworkManager using for its 802.1X supplicant code?
- From /usr/share/doc/NetworkManager-0.6.4/README:
The nm-applet provides a DBUS service called NetworkManagerInfo, which should provide to NetworkManager the Preferred Networks lists upon request. It also should be able to display a dialog to retrieve a WEP/WPA key or passphrase from the user when NetworkManager requests it. The GNOME version of NetworkManagerInfo, for example, stores Preferred Networks in GConf and WEP/WPA keys in gnome-keyring, and proxies that information to NetworkManager upon request.
gnome-keyring
thanks
Max Hetrick wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Moskowitz wrote:
hat is NetworkManager using for its 802.1X supplicant code?
- From /usr/share/doc/NetworkManager-0.6.4/README:
The nm-applet provides a DBUS service called NetworkManagerInfo, which should provide to NetworkManager the Preferred Networks lists upon request. It also should be able to display a dialog to retrieve a WEP/WPA key or passphrase from the user when NetworkManager requests it. The GNOME version of NetworkManagerInfo, for example, stores Preferred Networks in GConf
OK. I see this.
and WEP/WPA keys in gnome-keyring, and proxies that information to NetworkManager upon request.
Well if I can ever get it to take my passphrase we will see how it stores things in the keyring...
Still no dice on wpa passphrase.
On Wed, Mar 5, 2008 at 11:42 AM, Max Hetrick maxhetrick@verizon.net wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Robert Moskowitz wrote:
Where does NetworkManager keep its information? There was no /etc/sysconf/network-scripts/ifcfg-eth1 file. I made one (but don't know how to get PTK passphrases into the file). No change.
I'm not sure mine stores anything anywhere. Every time I connect it asks me for my passphrase information when I attempt to connect.
When I go home and turn the wireless on, I can search my logs to see if it's storing that anywhere and get back to you.
If you have passphrases turned on in Gnome it stores them in
Network manager stores its data via dbus which gets its stuff usually from user configs.
/home/$USER/.gconf/system/networking/wireless
Now I will say I had similar problems with the DAG ipw3945 and some AP's. I had to recompile with some options turned off to get it to work better. In the end, I switched to some Intel made rpms and tada it all worked better. However, I can't use the device to do airsnort etc so its a wash in my opinion.
-
Akemi Yagi -
Joshua Baker-LePain -
Max Hetrick -
Robert Moskowitz -
Stephen John Smoogen