Jerry,<br><br>The one I set up for testing has no security.<br>The "real" one in the school has security.<br><br>Clearly, this method (either one -- GNOME or NetworkManager) works. The issue is the persistence. To ask teachers to do this with 100 students every time they want to access the internet makes either one unworkable.<br>
<br>Any help will be appreciated.<br><br>Thanks.<br>Gerald<br><br><div class="gmail_quote">On Thu, Mar 3, 2011 at 10:55 PM, Jerry Vonau <span dir="ltr"><<a href="mailto:jvonau@shaw.ca">jvonau@shaw.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Thu, 2011-03-03 at 14:47 +1100, James Cameron wrote:<br>
> On Wed, Mar 02, 2011 at 10:38:07PM -0500, Dr. Gerald Ardito wrote:<br>
> > Both methods work within a session.<br>
> > In GNOME, I can connect to the hidden network. And, if I change back<br>
> > to Sugar, the connection is intact.<br>
><br>
> Yes. NetworkManager still has knowledge of the hidden network<br>
> connection request in memory, having been told about it by the GNOME<br>
> nm-applet.<br>
><br>
> (Restarting NetworkManager at this point causes the connection to drop<br>
> and not be re-established.)<br>
><br>
<br>
</div>Well sort of, if you restart MN in a terminal in GNOME, the connection<br>
is re-established, switch over to sugar the AP icon has the ESSID<br>
populated. This works if "Available to all users" was ticked as NM sees<br>
this as a system connection under root's control. Now open terminal in<br>
SUGAR and restart NM, now the ESSID is set to "None". While un-ticked<br>
you will be prompted for the info, which is saved in connections.cfg.<br>
The difference might be that in GNOME you have gnome-keyring running<br>
while in SUGAR it's not. There is the question of who owns the<br>
connection while setup as an ifcfg file, root or olpc?<br>
<div class="im"><br>
<br>
> > When I reboot, however, while the Wireless Connections UI (iin either<br>
> > GNOME or Sugar using nm) shows the connection properly, it does not<br>
> > actually connect to the hidden ssid.<br>
><br>
> Yes, I agree. After reboot, NetworkManager is restarted, and therefore<br>
> no longer knows about the hidden network connection request.<br>
><br>
<br>
</div>Agreed, I'll look for how "Connect to Hidden Wireless network" runs its<br>
re-scan for the hidden network in the code.<br>
<div class="im"><br>
> The ONBOOT setting doesn't appear to work either.<br>
><br>
<br>
</div>On an un-hidden network it does, or at least loaded as the UI becomes<br>
usable.<br>
<br>
Gerald, does your AP have any security or is it just hidden?<br>
<font color="#888888"><br>
Jerry<br>
<br>
</font></blockquote></div><br>