I would pull back to the "Enterprise" scenario here and note there are APs and smarter networks which will temporarily blacklist if not ban a client device after repeated failed association attempts. There also are networks (although somewhat rare) which change their passwords daily to ensure that only customers of a restaurant or similar establishment get wifi access. Is there a method to put this on a counter so we attempt to reassociate once with stored credentials and then prompt the user the second time? How does GNOME handle this? <div class="gmail_quote">On Mon, Jun 25, 2012 at 11:06 AM, Ajay Garg <<a href="mailto:ajay@activitycentral.com" target="_blank">ajay@activitycentral.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yep.. Sorry Peter, Anish. So, as far as the current patch is concerned, this patch should be tested WITHOUT thinking about the WPA-Enterprise Networks scenario. That should bring us back on the track (for this particular patch) :P Regards, Ajay<div class="HOEnZb"><div class="h5"> <div class="gmail_quote">On Mon, Jun 25, 2012 at 8:31 PM, Anish Mangal <<a href="mailto:anish@activitycentral.com" target="_blank">anish@activitycentral.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Not to take the discussion in a different direction, but IMO, would be great if Enterprise network support made it to upstream sugar. :-) <div><div> On Mon, Jun 25, 2012 at 8:22 PM, Ajay Garg <<a href="mailto:ajay@activitycentral.com" target="_blank">ajay@activitycentral.com</a>> wrote: > Peter, > > Is WPA-Enterprise Networks supported in Sugar 0.96, yet? (I don't think it > is). > As a result, the current patch has not been tested with WPA Enterprise > Networks. > > There is a patch for WPA-Enterprise Networks (fully integrated in dextrose3) > available at > <a href="http://patchwork.sugarlabs.org/patch/1096/" target="_blank">http://patchwork.sugarlabs.org/patch/1096/</a> > > with specs at > <a href="http://wiki.sugarlabs.org/go/Features/WPA-WPA2-Enterprise-Network-Connections" target="_blank">http://wiki.sugarlabs.org/go/Features/WPA-WPA2-Enterprise-Network-Connections</a> > > Would upstream be interested :P :P (I would be more than willing to port > it). > > > > Adding Anish in the loop. > > > Regards, > Ajay > > > > > On Mon, Jun 25, 2012 at 8:07 PM, Peter Robinson <<a href="mailto:pbrobinson@gmail.com" target="_blank">pbrobinson@gmail.com</a>> > wrote: >> >> On Sun, Jun 24, 2012 at 12:00 PM, Ajay Garg <<a href="mailto:ajay@activitycentral.com" target="_blank">ajay@activitycentral.com</a>> >> wrote: >> > >> > NM may request the secrets in the following cases :: >> > >> > a) >> > Wifi connection is lost. >> > >> > b) >> > After being lost, the wifi connection is again within the range. >> > >> > c) >> > When the credentials for the wifi network change. >> > >> > >> > In every case, secrets were being requested via the popup dialog. >> > >> > However, case c) is rare (and when it does happens, usually the >> > system-administrator, or the like, >> > has the responsibility for issuing the changes publically). >> > >> > Thus, due to case c) (which is rare), cases a) and b) were suffering >> > (these cases are generally >> > very plausible cases in everyday life). >> > >> > >> > So now, the intended solution is ::: >> > >> > >> > 1. >> > Always return the cached secrets (present in 'settings' themselves). >> > This would make the irritating dialog-box go away, for cases a) and b). >> > >> > >> > 2. >> > For case c), the user would :: >> > >> > (i) "Discard Network History". >> > (ii) Click on the wifi icon (in the neighborhood-view). >> > (iii) Enter the new (publically broadcasted) credentials. >> >> This biggest time for C is when it's WPA-Enterprise and the enterprise >> user authenication has a lifetime on the password. Our corp wifi is AD >> authenticated and the password expires every 60 days. >> >> Peter > > </div></div></blockquote></div> </div></div> _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div>