Sugar and NetworkManager

[forster at ozonline.com.au]

Hi
Can I suggest a related issue and alteration to this strategy? Is it possible to easily forget a connection? Maybe this has been done in later builds. At a conference I had briefly connected to a strong paid connection. Everytime the free conference connection dropped out, and it did it a lot, I was automatically connected to the paid connection. If there was a solution, I couldn't find it, maybe add forget to connect/disconnect menu?
Tony

> Hi,
> 
> I'm trying to improve the autoconnection algorithm NetworkManager uses to
> select the best AP to connect to -in the XO with F11-.
> 
> I've succeeded in modifying the algorithm so that it connects to the known
> AP with best strength. The problem I'm having is that the XO's initial scans
> are poor in results and don't let NM autoconnection feature make a confident
> decision as to what AP to connect to. This is important for network planning
> issues in deployments.
> 
> What I wanted to do was to execute a few scans before NM tries to
> autoconnect to any AP. That's why I have a question about how wireless
> interfaces get started in Sugar.
> 
> I was under the impression that I could ask for the scans by editing the
> code where sugar starts the network interfaces. Sadly I'm not familiar with
> the code and don't know where to start.
> 
> That's why I'm asking if anyone could point me in some direction (what .py/s
> to look for, where the interfaces get started) in order to accomplish what I
> want to do.
> 
> I look forward to any tips anyone can provide.
> 
> Thanks much for the help.
> 
> Cheers,
> 
> -- 
> Ing. Franco Miceli
> CITS - Plan Ceibal - Investigaci�n & Desarrollo
> Av. Italia 6201 - Montevideo, Uruguay
> CP: 11500
> Tel: (598 2) 601 5773 int.: 2227
> Hi,<br><br>I'm trying to improve the autoconnection algorithm NetworkManager uses to select the best AP to connect to -in the XO with F11-.<br><br>I've succeeded in modifying the algorithm so that it connects to the known AP with best strength. The problem I'm having is that the XO's initial scans are poor in 
> results and don't let NM autoconnection feature make a confident 
> decision as to what AP to connect to. This is important for network planning issues in deployments.<br><br>What I wanted to do was to execute a few scans before NM tries to autoconnect to any AP. That's why I have a question about how wireless interfaces get started in Sugar. 
> <br><br>I
>  was under the impression that I could ask for the scans by editing the code where sugar starts the network 
> interfaces. Sadly I'm not familiar with the code and don't know where to
>  start.<br>
> <br>That's why I'm asking if anyone could point me in some direction 
> (what .py/s to look for, where the interfaces get started) in order to 
> accomplish what I want to do.<br><br>I look forward to any tips anyone can provide.<br>
> <br>Thanks much for the help.<br><br>Cheers,<br><br><font color="#888888">-- <br>Ing. Franco Miceli<br>CITS - Plan Ceibal - Investigaci�n & Desarrollo<br>Av. Italia 6201 - Montevideo, Uruguay<br>CP: 11500<br>Tel: (598 2) 601 5773 int.: 2227</font><br>
> <br>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel