Feature request: restarting NM from nm-applet

2007-03-12 Thread Radek Vokál
I have issues with nm-applet and probably dbus, which doesn't recognize 
my USB Cable modem. So every time I plug in the USB modem I have to 
restart NetworkManager by hand. Same with my wireless card which has the 
switch off/on button. So I would like to see a restart option (or rather 
rescan option) in nm-applet which will look for recently added/removed NICs.

Radek
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Feature request: restarting NM from nm-applet

2007-03-12 Thread Bastien Nocera
On Mon, 2007-03-12 at 16:27 +0100, Radek Vokál wrote:
 I have issues with nm-applet and probably dbus, which doesn't recognize 
 my USB Cable modem. So every time I plug in the USB modem I have to 
 restart NetworkManager by hand. Same with my wireless card which has the 
 switch off/on button. So I would like to see a restart option (or rather 
 rescan option) in nm-applet which will look for recently added/removed NICs.

You should fix HAL to show your newly plugged in devices properly
instead.

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


NM and ipw3945 once again

2007-03-12 Thread wopozka
Hi,
Not so long time ago there was a thread about networkmanager and 
ipw3945. I 
had similar problem and therefore I decide to write. 

I have router with wpa psk. When I us wpa_supplicant it connects 
and I can 
without any problem use network. When I use networkmanager (with 
knetworkmanager applet) it keeps asking for the passphrase all the 
time (only 
in few cases it managed to connect to the network). I searched for 
the reason 
and below is what I discovered. 

I was monitoring wpa_supplicant using wpa_cli. I have found, that 
when it 
connects to my network, it first get disconets, then get timeout 
from 
00:00:00:00:00:00 (whatever it is), and then it tries the second 
time with my 
network and this time it connects to the ap. The log from wpa_cli 
below:

2Trying to associate with 00:18:4d:b9:be:44 
(SSID='ilonka_i_piotrek' freq=0 
MHz)
2CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
2Authentication with 00:00:00:00:00:00 timed out.
2Trying to associate with 00:18:4d:b9:be:44 
(SSID='ilonka_i_piotrek' freq=0 
MHz)
2Associated with 00:18:4d:b9:be:44
2WPA: Key negotiation completed with 00:18:4d:b9:be:44 [PTK=TKIP 
GTK=TKIP]
2CTRL-EVENT-CONNECTED - Connection to 00:18:4d:b9:be:44 
completed (auth)

Above is when I connect using directly wpa_supplicant. But when I 
use 
networkmanager the situation looks similar, but the question for 
passphrase 
appear all the time. When I monitored what is going on with 
wpa_supplicant 
called by networkmanager using wpa_cli I got below log:

2Trying to associate with 00:18:4d:b9:be:44 
(SSID='ilonka_i_piotrek' freq=0 
MHz)
2CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

At this point the networkmanager thinks that there was some 
problem with 
password and asks for the password again. When I write it once 
again, the 
situation repeats. But when I do not write password and observe 
wpa_supplicant, it connects to the ap after some time, the same 
like in case 
of direct use of wpa_supplicant:

2Authentication with 00:00:00:00:00:00 timed out.
2Trying to associate with 00:18:4d:b9:be:44 
(SSID='ilonka_i_piotrek' freq=0 
MHz)
2Associated with 00:18:4d:b9:be:44
2WPA: Key negotiation completed with 00:18:4d:b9:be:44 [PTK=TKIP 
GTK=TKIP]
2CTRL-EVENT-CONNECTED - Connection to 00:18:4d:b9:be:44 
completed (auth)

Of course nm does not know anything about that because it keeps 
asking for the 
new pasphrase.

It seems, that in every case when wpa_supplicant connects to my ap 
it first 
time get CTRL-EVENT-DISCONECTED, and then finally repeats 
connection and 
connects. But nm does not know that and thinks that there was 
something wrong 
with passphrase. 

Is there any solution of this problem. Because of that I am not 
able to use 
nm. The system is fc6 with some rawhide updates. The packages 
versions below:

wpa_supplicant-0.4.9-1.fc7
NetworkManager-0.6.5-0.3.cvs20061025.fc7
kernel-2.6.19-1.2911.6.5.fc6
ipw3945-1.2.0-18.2.fc6.at
ipw3945-kmdl-2.6.19-1.2911.6.5.fc6-1.2.0-18.2.fc6.at
ieee80211-kmdl-2.6.19-1.2911.6.5.fc6-1.2.16-17.fc6.at
knetworkmanager-0.1-0.6.svn20061113.fc6

Best regards
Piotr.


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: network-manager-applet release

2007-03-12 Thread Elijah Newren
Hi,

As Vincent earlier requested,

On 2/28/07, Vincent Untz [EMAIL PROTECTED] wrote:
 Le mercredi 28 février 2007, à 20:19, Vincent Untz a écrit :
  Hi,
 
  To include nm-applet in the GNOME release, it'd be really great to have
  a tarball :-)
 
  Would it be possible to have one soon?

it'd be great to have a tarball release.  In fact, nm-applet can't be
included in the GNOME release without having a tarball release to
include.  I'm very tempted to just request that nm-applet be
re-proposed for inclusion in 2.20, but maybe if we get a tarball
quickly...

Thanks,
Elijah
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list