:: Re: [DNG] netman GIT project
Page principale
Supprimer ce message
Répondre à ce message
Auteur: Edward Bartolo
Date:  
À: dng
Sujet: Re: [DNG] netman GIT project
I am thinking about adding yet another operation to backend.c to
attempt automatic connection with a wifi.

The algorithm can work as follows:
a) read all filenames from /etc/network/wifi
b) scan for wifi essids and strengths
c) sort wifi essids according to strength, starting from the strongest
d) iterate wifi as follows:
     i) if wifi essid is configured attempt connection
    ii) if wifi essid is not configured skip it
e) if all wifi essids are exhausted, prompt the user or change colour
of the GUI from default to some other colour to draw the user's
attention without being a nuisance.


Should I modify the existing functions that already work, to be able
to use them in the above algorithm, or write a new function which does
not use any services from the previous functions? Including all
functionality in new function adds more code but avoids potential
breakage of already tested functions.

>
> On 29/08/2015, Go Linux <golinux@???> wrote:
>>
>> Congrats on getting git to play nice! :)
>>
>> --------------------------------------------
>> On Fri, 8/28/15, Edward Bartolo <edbarx@???> wrote:
>>
>> Subject: Re: [DNG] netman GIT project
>> To: "Steve Litt" <slitt@???>
>> Cc: "dng" <dng@???>
>> Date: Friday, August 28, 2015, 2:35 PM
>>
>> But now, it looks like I succeeded with this commit:
>>
>> -----------------------------------------------
>> commit 799957ad4007aa8e272d18508e59f33903b7c44d
>> Author: edbarx <edbarx@???>
>> Date: Fri Aug 28 19:43:42 2015 +0100
>>
>>     GUI frontend: now supports wireless and wired connections. Code
>> added to protect the defaults in /etc/network/interfaces.

>>
>>     Backend C code: add another function connect_wired() and another
>> operation to backend code number 9. This is to connect a wired
>> connection. Both the frontend and the backend now refuse to disconnect
>> multiple connections. netman is now designed to handle one connection
>> at a time. Code has been added to minimize situations where multiple
>> instances of the backend are running.
>> ----------------------------------------------------------------

>>
>