Re: wpa_supplicant with ipw3945

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Kevin,

Thanks for the explanation. I'm checking off this mail list--activity too much for me to handle. I will check in again when I run into the next snag. The mail list and the people listening provide an invaluable service to novices like me. Thanks.

Regards,

John Dey
On May 24, 2007, at 9:05 PM, Kevin J. Cummings wrote:

John Dey wrote:
Kevin,

I can't believe it--It worked like a charm. Out with wpa_supplicant and
in with NetworkManagerDispatcher and NetworkManager.  They had been
installed but were not running.  The new serverst asked me to enter a
key ring which, for now, I declined.  I really would like to know what
is going on. I thought I was entering a key but it looks like the code was interpreted as a passphrase. The key seems to show from the command
'iwconfig eth1'.  I will play around with it a little bit when I have
time but it is satisfying to make the connection. Thanks you very much
for your assistance.

The "key ring" is gnome-keyring.  It manages your network password
(similar to storing ssh passwords).  The keyring itself is protected by
a passphrase of your choosing.  After entering your passphrase, any
stored passwords (like your WPA key) are given to the NetworkManager
automatically for *that* ESSID which you saved the key for.  It
(gnome-keyring) will save as many different keys for as many different
Wi-Fi networks that you may use from time to time.

John

On May 24, 2007, at 5:16 PM, Kevin J. Cummings wrote:

John Dey wrote:
Hi,

I have a wireless working on fc6 i386 without encryption When I set the
linksys router to:

securtiy mode: wpa2 persenal
wpa algorithm: TKIP+AEP
Group key renewal: 3600

Then I set the key and other items in wpa_supplicant.conf and try to start wpa_supplicant with -D ipw3945 I get an error that ipw3945 is not
supported.

Don't run wpa_supplicant.  Instead, run NetworkManagerDispatcher and
NetworkManager from the NetworkManager RPM.  Each runs as a service.
You can find them in core. You might also want the NetworkManager-gnome
if you want it to run in your task bar.

I am not very familiar with encrypted wireless. Is there a good Howto?
 Any guidance will greatly appreciated.  Thanks.

Its not that much different than un-encrypted wireless.  It requires
more iwconfig commands to be entered in order to work. Are you familiar
with the iwconfig command?  It can show you the current state of your
wireless chip as the system sees it.

And if you are still having problems, look at your /var/log/messages
file for messages about your hardware.

John

--
Kevin J. Cummings
kjchome@xxxxxxx
cummings@xxxxxxxxxxxxxxxxxx
cummings@xxxxxxxxxxxxxxxxxxxxxxx
Registered Linux User #1232 (http://counter.li.org)

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list




--
Kevin J. Cummings
kjchome@xxxxxxx
cummings@xxxxxxxxxxxxxxxxxx
cummings@xxxxxxxxxxxxxxxxxxxxxxx
Registered Linux User #1232 (http://counter.li.org)

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux