Am Thu, 24 Jan 2008 18:31:44 -0500 schrieb Dan Williams <dcbw redhat com>: > On Thu, 2008-01-24 at 14:31 -0500, Ryan Novosielski wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Ralf Rublack wrote: > > > Am Thu, 24 Jan 2008 11:54:27 -0500 > > > schrieb Ryan Novosielski <novosirj umdnj edu>: > > > > > > Ralf Rublack wrote: > > >>>> hi guys > > >>>> > > >>>> at first, why is a active connection restartet if I click in > > >>>> mn-applet on this network. is there any reason for this > > >>>> behavior? > > >>>> > > >>>> thx for any answer that can explain this > > >>>> greetings Ralf > > > I think it causes a scan. > > > > > >> was this the answer to first or second problem?? > > > > Sorry for not placing that better -- it was an answer for the > > disconnect-on-click. I suspect, though, that that is not supposed to > > happen and that there is something to do about it. If I'm right > > though, it would seem to explain at least the "why." > > Actually, it's intentional behavior though not with a strong reason. > What behavior would you expect to happen when you click on the item? > One reason is that the behavior is _consistent_, ie that it doesn't > magically change based on the phase of the moon. Hence, when you > click on a menu item you know it will connect to something. > > Dan > Your are right with your though of _consistent_. Also I wouldn't make this a big problem, it isn't for me. I only think, in manner of using an application in usability concerns, the nm-applet should send his click event to the nm, but this should check if the clicked connection is established and if this is true no reconnection cycle is started. One example in this manner: user is down/up somethink, he want to use some application in his notification area, somehow he hit the nm-applet an trigger the current coonnection, connection is restartet his down/up timed out or lost connection to ssh because he got new ip from dhcp. enough of this the mail to the list was actualy because my second problem with the WPA-EAP and the frequent appearence of the new key dialog even through that the identification data are still in gconf. Had this anythink to do with roaming from one BSSID to another. > > Jan 24 11:14:47 popalf NetworkManager: <debug> [1201169687.445058] > > nm_device_802_11_wireless_update_bssid(): Roamed from BSSID > > 00:15:FA:A1:F8:90 to 00:19:AA:51:43:60 on wireless network '802.1X' > > Jan 24 11:14:48 popalf NetworkManager: <info> Activation > > (ath0/wireless): disconnected during association, asking for new > > key. Jan 24 11:14:48 popalf NetworkManager: <info> Activation > > (ath0) New wireless user key requested for network '802.1X'. > > Jan 24 11:14:53 popalf NetworkManager: <debug> [1201169693.444811] > > nm_device_802_11_wireless_update_bssid(): Roamed from BSSID > > 00:15:FA:A1:F8:90 to 00:19:AA:51:43:60 on wireless network '802.1X' greetings -- Ralf Rublack University of Leipzig Student
Attachment:
signature.asc
Description: PGP signature