Re: kde (again)?



Michael Blakeley wrote:

>> Date: Thu, 15 Dec 2005 07:32:48 -0500
>  > From: Neal Becker <ndbecker2 gmail com>
>> 
>> I've been following networkmanager devel enthusiastically for several
>> months. I haven't been able to use it, because I use kde, and I need
>> to set WEP keys. I've never seen any guide to how to make this work.
>> I understand that in the present status somehow gnome's key manager
>> needs to be started - but I don't know how to do this.
>> 
>> I think that networkmanager will miss out out >1/2 of the linux
>> audience unless there is some way for kde users to make this work.
>> Could someone kindly explain the procedure?
> 
> KDE users who don't need WEP are fine with nm-applet out-of-the-box, as
> you probably know (modulo the various nm-applet/NetworkManager freezes
> and crashes that I see every other day or so).
> 
> For WEP, you need to give nm-applet some way to get to a gnome-keyring.
> I posted this link previously, so you can probably find it in the
> list-archives, but here it is again:
> http://bugzilla.ubuntu.com/show_bug.cgi?id=17463 (perhaps the
> NetworkManager web site admin could copy it or link to it?).
> 
> The procedure requires you to create two files, which will be run when
> you start and stop kde (respectively). Both files must be readable and
> executable by startkde:
> 
[...]

> I don't know about open networks, but I'd expect them to function more
> smoothly. Why don't you try it, and post back to the list with your
> results?
> 
> -- Mike

Thanks Mike!

OK, it sortof works.  I have a WEP net at home.  It brought up gnome wallet,
asked for password.  Connected OK

When I woke up this morning, it was asking for the gnome wallet password
again, and was not connected.  Not sure why it was asking for a password
again, maybe timeout?

Then, I went to work, and connected to 100BaseT.  Fired up
NetworkManagerDispatcher and NetworkManager. (NetworkManager-0.5.1-1.FC4.4)

Strange thing is, I don't have an eth0.  Now I have:
/sbin/ifconfig
dev7098   Link encap:Ethernet  HWaddr 00:0F:B0:47:08:7A
          inet addr:10.32.112.206  Bcast:255.255.255.255  Mask:255.255.255.0
          inet6 addr: fe80::20f:b0ff:fe47:87a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:59941 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31550 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:38299508 (36.5 MiB)  TX bytes:3412795 (3.2 MiB)
          Interrupt:185 Base address:0x7000

Wonder where dev7098 came from?  I think this may cause some trouble.




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