Dear fellow testers,
I have a machine with wireless card that NetworkManager identifies but cannot connect. The Administrator at school tried to connect it, but gnome-keyring came out and asked for the password. I put in my own root password, but the connection failed :(. The network is encrypted and it has a key and he put the key, but gnome-keyring gets in the way and I am denied a connection. What can I do to make this machine connect with wireless?
In the other case, when a wire is present it connects without problems.
http://www.smolts.org/client/show/pub_52cf9c16-aa07-4697-8df6-7b47eb9855f4 (public)
The machine has a wireless nic supported by Atheros ath5k driver (Thanks to Mr. Linville and all other contributors to the project, the card is identified and it tries to connect)
The card is an Atheros Communications, Inc. AR5005G 802.11abg NIC
I do not know the password to the gnome-keyring. The network adminstrator can put the key in but that keyring pops up and destroys everything. On windoze the machine picks up without problems. I would like to have the same functionality on the Linux side if possible.
Thank you in advance for all your help/suggestions/advice.
Regards,
Antonio
On Wed, 2008-11-12 at 17:57 -0800, Antonio Olivares wrote:
Thank you in advance for all your help/suggestions/advice.
The gnome keyring is a secure storage of various passphrases that you may use during your session. It typically has one password to unlock the key, and then other passphrases can be fetched from the keyring for various applications. Quite often, the keyring has the same password as your login password, but this isn't required (nor should it be encouraged).
Now, if you've forgotten your gnome keyring password, that's going to be fun to recover. The easiest thing to do is remove the existing keyring so that upon next session you get the opportunity to create a new keyring (and this time set it to a password you remember). To do this, remove the files in .gnome2/keyrings/ and log back into gnome.
--- On Wed, 11/12/08, Jesse Keating jkeating@redhat.com wrote:
From: Jesse Keating jkeating@redhat.com Subject: Re: NetworkManager connection to encrypted Wireless Network To: fedora-test-list@redhat.com Date: Wednesday, November 12, 2008, 6:03 PM On Wed, 2008-11-12 at 17:57 -0800, Antonio Olivares wrote:
Thank you in advance for all your
help/suggestions/advice.
The gnome keyring is a secure storage of various passphrases that you may use during your session. It typically has one password to unlock the key, and then other passphrases can be fetched from the keyring for various applications. Quite often, the keyring has the same password as your login password, but this isn't required (nor should it be encouraged).
Now, if you've forgotten your gnome keyring password, that's going to be fun to recover. The easiest thing to do is remove the existing keyring so that upon next session you get the opportunity to create a new keyring (and this time set it to a password you remember). To do this, remove the files in .gnome2/keyrings/ and log back into gnome.
-- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating --
Thank you very much,
I will give it a try tomorrow. Upon success/failure, I will hopefully report back.
Regards,
Antonio
Jesse Keating wrote:
The gnome keyring is a secure storage of various passphrases that you may use during your session. It typically has one password to unlock the key, and then other passphrases can be fetched from the keyring for various applications. Quite often, the keyring has the same password as your login password, but this isn't required (nor should it be encouraged).
My experience (with KDE) is that NM sometimes gets into a state where it endlessly asks you for your keyring password. In general, NM seems to suffer from severe short-term memory failure, asking the same question over and over again.
On Thu, 2008-11-13 at 12:09 +0000, Timothy Murphy wrote:
My experience (with KDE) is that NM sometimes gets into a state where it endlessly asks you for your keyring password. In general, NM seems to suffer from severe short-term memory failure, asking the same question over and over again.
The interaction on KDE is likely not tested very well. For a time kde users had to use the gnome panel icon, which meant interaction with gnome-keyring-manager which /should/ work in a KDE environment but likely doesn't always.
Now there is a knetworkmanager type thing that uses KDE stuff, however I don't know how well tested or mature that interface to the underlying service is. You may just be having bugs with the KDE frontend, and not the service itself.
On Thursday 13 November 2008 17:47:04 Jesse Keating wrote:
On Thu, 2008-11-13 at 12:09 +0000, Timothy Murphy wrote:
My experience (with KDE) is that NM sometimes gets into a state where it endlessly asks you for your keyring password. In general, NM seems to suffer from severe short-term memory failure, asking the same question over and over again.
The interaction on KDE is likely not tested very well. For a time kde users had to use the gnome panel icon, which meant interaction with gnome-keyring-manager which /should/ work in a KDE environment but likely doesn't always.
Now there is a knetworkmanager type thing that uses KDE stuff, however I don't know how well tested or mature that interface to the underlying service is. You may just be having bugs with the KDE frontend, and not the service itself.
In that case, how can we act directly with NM?
Anne
On Thu, 2008-11-13 at 18:27 +0000, Anne Wilson wrote:
In that case, how can we act directly with NM?
There is /usr/bin/nm-tool , also not very well documented.
On Thursday 13 November 2008 18:38:36 Jesse Keating wrote:
On Thu, 2008-11-13 at 18:27 +0000, Anne Wilson
wrote:
In that case, how can we act directly with NM?
There is /usr/bin/nm-tool , also not very well
documented.
That seems to simply report, leaving no room for interaction. I don't see that it's going to help us much.
Anne
On Thu, Nov 13, 2008 at 09:47:04AM -0800, Jesse Keating wrote:
The interaction on KDE is likely not tested very well. For a time kde users had to use the gnome panel icon, which meant interaction with gnome-keyring-manager which /should/ work in a KDE environment but likely doesn't always.
For what it's worth, on two KDE-centric distros, Mepis Beta (with KDE 3. something ) and Mandriva 2009 with KDE 4, I had trouble. In all cases, I had to stop the various wpa and dhclient things being run and do it manually. In both cases, it would, according to iwconfig, connect, but it wouldn't get an address, whether I manually configured it or tried with DHCP.
On Friday 14 November 2008 00:04:08 Scott Robbins wrote:
On Thu, Nov 13, 2008 at 09:47:04AM -0800, Jesse Keating wrote:
The interaction on KDE is likely not tested very well. For a time kde users had to use the gnome panel icon, which meant interaction with gnome-keyring-manager which /should/ work in a KDE environment but likely doesn't always.
For what it's worth, on two KDE-centric distros, Mepis Beta (with KDE 3. something ) and Mandriva 2009 with KDE 4, I had trouble. In all cases, I had to stop the various wpa and dhclient things being run and do it manually. In both cases, it would, according to iwconfig, connect, but it wouldn't get an address, whether I manually configured it or tried with DHCP.
Equally FWIW, this laptop has Mandriva 2009 with KDE 4, and the wireless works flawlessly.
Anne
On Friday 14 November 2008 00:04:08 Scott Robbins wrote:
For what it's worth, on two KDE-centric distros, Mepis Beta (with KDE 3. something ) and Mandriva 2009 with KDE 4, I had trouble. In all cases, I had to stop the various wpa and dhclient things being run and do it manually. In both cases, it would, according to iwconfig, connect, but it wouldn't get an address, whether I manually configured it or tried with DHCP.
Surely that sounds like a problem with dhcp, not WiFi?
On Friday 14 November 2008 14:33:26 Timothy Murphy wrote:
On Friday 14 November 2008 00:04:08 Scott Robbins wrote:
For what it's worth, on two KDE-centric distros, Mepis Beta (with KDE 3. something ) and Mandriva 2009 with KDE 4, I had trouble. In all cases, I had to stop the various wpa and dhclient things being run and do it manually. In both cases, it would, according to iwconfig, connect, but it wouldn't get an address, whether I manually configured it or tried with DHCP.
Surely that sounds like a problem with dhcp, not WiFi?
Can't be. This laptop has Mandriva 2009 + KDE 4. It connects using wpa_supplicant and gets its address by dhcp.
At one point it was suggested that it was a kde problem, but the gnome live cd has exactly the same problem. This is purely a fedora problem. As it has been for several releases.
Anne
On Thu, Nov 13, 2008 at 11:47 AM, Jesse Keating jkeating@redhat.com wrote:
On Thu, 2008-11-13 at 12:09 +0000, Timothy Murphy wrote:
My experience (with KDE) is that NM sometimes gets into a state where it endlessly asks you for your keyring password. In general, NM seems to suffer from severe short-term memory failure, asking the same question over and over again.
The interaction on KDE is likely not tested very well. For a time kde
Ergo, this is everyone else's problem. We don't have to provide something that works, we just need to add something that wasn't there before. We're Redhat.
jerry
On Friday 14 November 2008 04:57:20 Jerry Amundson wrote:
On Thu, Nov 13, 2008 at 11:47 AM, Jesse Keating jkeating@redhat.com wrote:
On Thu, 2008-11-13 at 12:09 +0000, Timothy Murphy wrote:
My experience (with KDE) is that NM sometimes gets into a state where it endlessly asks you for your keyring password. In general, NM seems to suffer from severe short-term memory failure, asking the same question over and over again.
The interaction on KDE is likely not tested very well. For a time kde
Ergo, this is everyone else's problem. We don't have to provide something that works, we just need to add something that wasn't there before. We're Redhat.
Mandriva + KDE 4 works perfectly
Anne
On Fri, 2008-11-14 at 06:55 +0000, Anne Wilson wrote:
Mandriva + KDE 4 works perfectly
So lets do some comparison here. Do you know what application Mandriva is using to get you connected? What is the kernel level, and what is the output of modinfo of the module for your wireless card?
On Friday 14 November 2008 17:34:19 Jesse Keating wrote:
On Fri, 2008-11-14 at 06:55 +0000, Anne Wilson wrote:
Mandriva + KDE 4 works perfectly
So lets do some comparison here.
Sure, though I made that remark to refute the idea that KDE4 is the problem.
Do you know what application Mandriva is using to get you connected?
wpa_supplicant
What is the kernel level,
2.6.27.4-desktop-2mnb
and what is the output of modinfo of the module for your wireless card?
Remember that this is a different laptop. Wifi here is ipw2200
modinfo ipw2200 filename: /lib/modules/2.6.27.4- desktop-2mnb/kernel/drivers/net/wireless/ipw2200.ko.gz license: GPL author: Copyright(c) 2003-2006 Intel Corporation version: 1.2.2kmprq description: Intel(R) PRO/Wireless 2200/2915 Network Driver srcversion: 0019B280965EEAD222D68E9 alias: pci:v00008086d00004224sv*sd*bc*sc*i* alias: pci:v00008086d00004223sv*sd*bc*sc*i* alias: pci:v00008086d00004221sv*sd*bc*sc*i* alias: pci:v00008086d00004220sv*sd*bc*sc*i* alias: pci:v00008086d0000104Fsv*sd*bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002762bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002761bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002754bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002753bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002752bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002751bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002742bc*sc*i* alias: pci:v00008086d00001043sv0000103Csd00002741bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002741bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002732bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002731bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002722bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002721bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002712bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002711bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002702bc*sc*i* alias: pci:v00008086d00001043sv00008086sd00002701bc*sc*i* depends: ieee80211 vermagic: 2.6.27.4-desktop-2mnb SMP mod_unload 686 parm: disable:manually disable the radio (default 0 [radio on])(int) parm: associate:auto associate when scanning (default on) (int) parm: auto_create:auto create adhoc network (default on) (int) parm: led:enable led control on some systems (default 0 off) (int) parm: debug:debug output mask (int) parm: channel:channel to limit associate to (default 0 [ANY]) (int) parm: rtap_iface:create the rtap interface (1 - create, default0) (int) parm: qos_enable:enable all QoS functionalitis (int) parm: qos_burst_enable:enable QoS burst mode (int) parm: qos_no_ack_mask:mask Tx_Queue to no ack (int) parm: burst_duration_CCK:set CCK burst value (int) parm: burst_duration_OFDM:set OFDM burst value (int) parm: mode:network mode (0=BSS,1=IBSS,2=Monitor) (int) parm: bt_coexist:enable bluetooth coexistence (default off) (int) parm: hwcrypto:enable hardware crypto (default off) (int) parm: cmdlog:allocate a ring buffer for logging firmware commands (int) parm: roaming:enable roaming support (default on) (int) parm: antenna:select antenna 1=Main, 3=Aux, default 0 [both], 2=slow_diversity (choose the one with lower background noise) (int)
Does that shed any light?
I could get similar info from the EeePC, if it would help to compare.
Anne
On Fri, 2008-11-14 at 18:58 +0000, Anne Wilson wrote:
wpa_supplicant
What is the kernel level,
2.6.27.4-desktop-2mnb
and what is the output of modinfo of the module for your wireless card?
Remember that this is a different laptop. Wifi here is ipw2200
Oh, well not nearly as interesting then. I thought you meant that Mandriva on the problematic system was working perfectly.
Out of curiosity, how do you interact with wpa_supplicant?
As for the KDE working or not, I was mostly making guesses before we had more evidence to the fact that the kernel/firmware may be the issue, not the config software.
On Friday 14 November 2008 19:08:12 Jesse Keating wrote:
On Fri, 2008-11-14 at 18:58 +0000, Anne Wilson wrote:
wpa_supplicant
What is the kernel level,
2.6.27.4-desktop-2mnb
and what is the output of modinfo of the module for your wireless card?
Remember that this is a different laptop. Wifi here is ipw2200
Oh, well not nearly as interesting then. I thought you meant that Mandriva on the problematic system was working perfectly.
Out of curiosity, how do you interact with wpa_supplicant?
I don't. It was configured once, and it doesn't need anything more.
As for the KDE working or not, I was mostly making guesses before we had more evidence to the fact that the kernel/firmware may be the issue, not the config software.
Ah - a thought. I have Mandriva on a usb pen-drive. I'll try it and see if there is any success, I don't know whether the kernel will be recent enough though, as that is Mandriva 2008.1.
I'll let you know if I get anything useful.
Anne
On Friday 14 November 2008 19:35:41 Anne Wilson wrote:
Ah - a thought. I have Mandriva on a usb pen-drive. I'll try it and see if there is any success, I don't know whether the kernel will be recent enough though, as that is Mandriva 2008.1.
I'll let you know if I get anything useful.
Well, it was a thought. The hardware is just too different. I'd need to reinstall. Maybe I'll find time for that over the weekend, if it would really be valuable. Would it?
Anne
On Fri, 2008-11-14 at 19:49 +0000, Anne Wilson wrote:
Maybe I'll find time for that over the weekend, if it would really be valuable. Would it?
If it works there, yes, as we can compare kernel versions, whether or not they used different firmware, etc.. but if it doesn't work, not much value.
Since you said it's an older kernel, I'm not too optimistic that it would work.
On Friday 14 November 2008 20:02:01 Jesse Keating wrote:
On Fri, 2008-11-14 at 19:49 +0000, Anne Wilson wrote:
Maybe I'll find time for that over the weekend, if it would really be valuable. Would it?
If it works there, yes, as we can compare kernel versions, whether or not they used different firmware, etc.. but if it doesn't work, not much value.
Since you said it's an older kernel, I'm not too optimistic that it would work.
I've just borrowed a system to check. The latest kernels available for 2008.1 are 2.6.24.x, which is much too old, I think. Isn't 2.6.27 the beginning of the ath5K driver being in the kernel?
Anne
On Fri, 2008-11-14 at 20:22 +0000, Anne Wilson wrote:
Isn't 2.6.27 the beginning of the ath5K driver being in the kernel?
I honestly don't know that.
On Fri, Nov 14, 2008 at 08:22:09PM +0000, Anne Wilson wrote:
I've just borrowed a system to check. The latest kernels available for 2008.1 are 2.6.24.x, which is much too old, I think. Isn't 2.6.27 the beginning of the ath5K driver being in the kernel?
No. I am using ath5k on a laptop (currently with F8 on it) for some time. So this worked at least with 2.6.26.x kernels although I do not remember now when I switched from madwifi. 2.6.24.x may indeed be too old. The module ath5k.ko was there but not in the best shape.
In any case this works for me, currently with 2.6.26.6-49.fc8 for a kernel, without any issues and in WPA2 mode. Curiously enough NM in "Connection Information" claims "Driver: ath5k_pci", while there is nothing like that around, but whatever ...
Of course ath5k services a lot of different hardware and I may be just lucky with that particular card ("AR5212/AR5213", 168c:0013).
Michal
On Fri, Nov 14, 2008 at 08:22:09PM +0000, Anne Wilson wrote:
I've just borrowed a system to check. The latest kernels available for 2008.1 are 2.6.24.x, which is much too old, I think. Isn't 2.6.27 the beginning of the ath5K driver being in the kernel?
Not of the module itself, but the beginning of it working with the AR5007EG.
On Fri, 2008-11-14 at 19:35 +0000, Anne Wilson wrote:
I don't. It was configured once, and it doesn't need anything more.
Ok, just a side discussion here. What would happen if you went to a coffee shop and needed to use the wireless there, or to an office and needed to use the encrypted wireless there? How do you configure for that?
As for the KDE working or not, I was mostly making guesses before we had more evidence to the fact that the kernel/firmware may be the issue, not the config software.
Ah - a thought. I have Mandriva on a usb pen-drive. I'll try it and see if there is any success, I don't know whether the kernel will be recent enough though, as that is Mandriva 2008.1.
I'll let you know if I get anything useful.
Thanks! Should be interesting.
On Friday 14 November 2008 19:49:32 Jesse Keating wrote:
On Fri, 2008-11-14 at 19:35 +0000, Anne Wilson wrote:
I don't. It was configured once, and it doesn't need anything more.
Ok, just a side discussion here. What would happen if you went to a coffee shop and needed to use the wireless there, or to an office and needed to use the encrypted wireless there? How do you configure for that?
It's a long time since I took this laptop anywhere :-) However, I took it to akademy 2007 and used it with the university network. It simply uses the info in the configuration if the SSID matches, but asks for a key if it doesn't.
My memory isn't worth 2p these days :-) but I'm pretty sure that's what happened. I've mostly used the EeePC on open networks, but I have used it at least once on an encrypted one, and the same thing happened there.
Anne
On Fri, Nov 14, 2008 at 11:49:32AM -0800, Jesse Keating wrote:
On Fri, 2008-11-14 at 19:35 +0000, Anne Wilson wrote:
I don't. It was configured once, and it doesn't need anything more.
Ok, just a side discussion here. What would happen if you went to a coffee shop and needed to use the wireless there, or to an office and needed to use the encrypted wireless there? How do you configure for that?
A wpa_supplicant configuration file allows for many different networks but you have to edit it or you will be asked for a required information every time. Clearly NM, __when it happens to work__, is definitely more convenient although creating tools which would edit those config files "automagically" should be rather simple. It appears that few orders of magnitude simpler than getting NM into a shape.
I already mentioned https://bugzilla.redhat.com/show_bug.cgi?id=413281 where NM messed up its configuration data and refused to recognize that all of that is bogus. Only an archeological dig in ~/.gconf plus quite a bit of a guesswork allowed me to recover. In comparison editing wpa_supplicant configurations is obvious and even documented ('man wpa_supplicant.conf').
It is not a question that NM could be often useful; only that priorities seems to be backwards. NM is not something entirely new, where you can expect "teething problems", but has been around already for a while.
Michal
On Fri, Nov 14, 2008 at 07:35:41PM +0000, Anne Wilson wrote:
Ah - a thought. I have Mandriva on a usb pen-drive. I'll try it and see if there is any success, I don't know whether the kernel will be recent enough though, as that is Mandriva 2008.1.
I'll let you know if I get anything useful.
I think 2008 was using MadWifi and 2009 is using ath5k. (Mepis, however, still uses MadWifi)
All my KDE wireless troubles were only with that AR5007EG card. It will be interesting to see if it works perfectly for you on the Acer. (Although, as previously mentioned, it works for most people apparently.)
On Thu, 2008-11-13 at 12:09 +0000, Timothy Murphy wrote:
Jesse Keating wrote:
The gnome keyring is a secure storage of various passphrases that you may use during your session. It typically has one password to unlock the key, and then other passphrases can be fetched from the keyring for various applications. Quite often, the keyring has the same password as your login password, but this isn't required (nor should it be encouraged).
My experience (with KDE) is that NM sometimes gets into a state where it endlessly asks you for your keyring password. In general, NM seems to suffer from severe short-term memory failure, asking the same question over and over again.
AIUI, the wireless protocols make it very difficult to diagnose why a connection failed. All you can really do is (a) try again or (b) fail.
There seems to be an issue with the iwl4965 driver (and maybe others) that gives NM fits. You could try a direct connection with wpa_supplicant to see if that makes a difference. (I haven't tried this with my iwl4965 because it sits near a wire.)
On Thursday 13 November 2008 01:57:05 Antonio Olivares wrote:
Dear fellow testers,
I have a machine with wireless card that NetworkManager identifies but cannot connect. The Administrator at school tried to connect it, but gnome-keyring came out and asked for the password. I put in my own root password, but the connection failed :(. The network is encrypted and it has a key and he put the key, but gnome-keyring gets in the way and I am denied a connection. What can I do to make this machine connect with wireless?
In the other case, when a wire is present it connects without problems.
http://www.smolts.org/client/show/pub_52cf9c16-aa07-4697-8df6-7b47eb9855f4 (public)
The machine has a wireless nic supported by Atheros ath5k driver (Thanks to Mr. Linville and all other contributors to the project, the card is identified and it tries to connect)
The card is an Atheros Communications, Inc. AR5005G 802.11abg NIC
I do not know the password to the gnome-keyring. The network adminstrator can put the key in but that keyring pops up and destroys everything. On windoze the machine picks up without problems. I would like to have the same functionality on the Linux side if possible.
Thank you in advance for all your help/suggestions/advice.
This may be related to the problems I described in my lengthy thread "Problem setting up wired networking" (wired got sorted, then wireless became problematic). Mine also uses the ath5k driver, and I seem to have problems passing the keys as well, so I'll be following your thread with interest.
Anne
-
Anne Wilson -
Antonio Olivares -
Jerry Amundson -
Jesse Keating -
Matthew Saltzman -
Michal Jaegermann -
Scott Robbins -
Timothy Murphy -
Timothy Murphy