Re: kde (again)?

2005-12-16 Thread Dan Williams
On Fri, 2005-12-16 at 08:39 -0500, Neal Becker wrote: > 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:b0

Re: kde (again)?

2005-12-16 Thread Neal Becker
Michael Blakeley wrote: >> Date: Thu, 15 Dec 2005 07:32:48 -0500 > > From: Neal Becker <[EMAIL PROTECTED]> >> >> 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 g

Re: kde (again)?

2005-12-15 Thread Michael Blakeley
Dan Williams wrote: On Thu, 2005-12-15 at 12:07 -0800, Michael Blakeley wrote: My AP never shows up from a 'sudo iwlist wlan0 scan' at all - that's kind of the point, as I understand it. If you don't know that it's there, you can't access it. But I'm sure you know more about wifi than I do. My

Re: kde (again)?

2005-12-15 Thread Dan Williams
On Thu, 2005-12-15 at 12:07 -0800, Michael Blakeley wrote: > My AP never shows up from a 'sudo iwlist wlan0 scan' at all - that's > kind of the point, as I understand it. If you don't know that it's > there, you can't access it. But I'm sure you know more about wifi than I do. > > My card is a bro

Re: kde (again)?

2005-12-15 Thread Jeremy Jongsma
Scanning worked fine for me on my broadcom card via ndiswrapper (using the bcmwl5 driver). Although it did lock up my machine every time I tried to switch networks after the initial connection, but that's another story. -j On Thu, 2005-12-15 at 12:07 -0800, Michael Blakeley wrote: > Dan Williams

Re: kde (again)?

2005-12-15 Thread Michael Blakeley
Dan Williams wrote: On Thu, 2005-12-15 at 09:28 -0800, Michael Blakeley wrote: It almost works :-). The only WEP network I use is "closed" - that is, it doesn't advertise its essid. So I have to set the essid manually, from the command line. When I do that, "my-closed-network" shows up in the

Re: kde (again)?

2005-12-15 Thread Dan Williams
On Thu, 2005-12-15 at 09:28 -0800, Michael Blakeley wrote: > It almost works :-). The only WEP network I use is "closed" - that is, > it doesn't advertise its essid. So I have to set the essid manually, > from the command line. When I do that, "my-closed-network" shows up in > the nm-applet menu

Re: kde (again)?

2005-12-15 Thread Michael Blakeley
Date: Thu, 15 Dec 2005 07:32:48 -0500 > From: Neal Becker <[EMAIL PROTECTED]> 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 underst

Re: kde (again)?

2005-12-15 Thread Timo Hoenig
Hi, On Thu, 2005-12-15 at 08:12 -0500, Dan Williams wrote: > Timo Hoenig said he was writing a KDE applet for NM on Nov 23 (see > thread about "NetworkManager with KDE"). I'd encourage him to stick it > in CVS even if it's not complete... Sorry for the delay. KNetworkManager is ready for the p

Re: kde (again)?

2005-12-15 Thread Neal Becker
On Thursday 15 December 2005 8:12 am, Dan Williams wrote: > On Thu, 2005-12-15 at 07:32 -0500, Neal Becker wrote: > > 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

Re: kde (again)?

2005-12-15 Thread Dan Williams
On Thu, 2005-12-15 at 07:32 -0500, Neal Becker wrote: > 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 p

kde (again)?

2005-12-15 Thread Neal Becker
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