NetworkManager Problems

[Paul Johnson]

I've been testing some more.  I was unable to log in, and started
re-tracing my steps. I turned off the "network" service, still no N-M
joy.  But I grew tired of typing in the key over and over, and I
installed the rpm gnome-keyring-manager.i386 2.14.0-1, and it would
not run because it could not connect to the keyring daemon.

Then I tried the MS Windows solution: reboot.

After using modprobe to load the ipw3945 module and loading the
userspace driver, then N-M did work.  After I typed in the WEP key,
then the gnome keyring manager popped up and asked for a password.
That's when I really knew I was in business!

Hypothesis 1:

what if N-M failed to connect with my WEP key because
gnome-keyring-manager was not installed?  N-M appeared to be doing
nothing, but maybe it was looking for the keyring manager?

Hypothesis 2:

Perhaps the NetworkManager RPM should have a pre-requisite of
gnome-keyring-manager.

pj


On 6/8/06, Paul Johnson <pauljohn32 at gmail.com> wrote:
> I wish you could keep the convo here so I can learn something from it.
>
>  I just tried N-M again with a WEP key.  I am able to use "/sbin/ifup
> home" and it uses the stored wep key in
> /etc/sysconfig/network-scripts/keys-home and it connects just fine.
> That is a 26 character symbol.  It looks like this
>
> # cat /etc/sysconfig/network-scripts/keys-home
> KEY=a12345b33333c54321d12345ef
>
> I BELIEVE that is a HEX key because in the system-config-network GUI,
> it is entered with 0x at the beginning. But there's no 0x at the
> beginning in the file, so what can I say? It works.
>
> Now If I turn that off manually and try with Network Manager, what am
> I supposed to do?
> I tell it I want WEP 64/128 bit HEX and fill in my number.  No
> connection results.
>
> I've tried typing it into N-M with the 0x at the beginning, but that
> makes the symbol use 28 characters and the connect button does not
> light up.
>
> I don't think either of the other choices for WEP would be correct
> because when I type in my 26 character wep key, the "connect" button
> does not light up when those other options are set.
>
> I don't know if I need "open network" or "shared key" but I tried both
> settings and nothing happens.
>
> pj
>
>
> On 6/8/06, Thom Paine <painethom at gmail.com> wrote:
> > I don't have WPA running on the AP yet, but I want to get there. I am
> > unable to have NM manage my wired and wireless connection, which is
> > the plan.
> >
> > It attempts to get connected, and I can click the NM icon and pick my
> > AP from the list and click connect, but it fails to connect.
> >
> > Is there some way I should delete all my network config stuff and
> > start over from scratch with just NM?
> >
> > Should I take this to the NM list?
> >
> > Thanks.
> >
> >
> > --
> > -=/>Thom
> >
> > --
> > fedora-list mailing list
> > fedora-list at redhat.com
> > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> >
>
>
> --
> Paul E. Johnson
> Professor, Political Science
> 1541 Lilac Lane, Room 504
> University of Kansas
>


-- 
Paul E. Johnson
Professor, Political Science
1541 Lilac Lane, Room 504
University of Kansas