Hi,
Once it connects, netman will not try to change connection unless it
fails. The backend first reads the available signal strengths, then it
reads what essids are installed, and finally, it tries to connect by
first trying the strongest wifi source if that is available in the
essid files. This
On Sun, Sep 13, 2015 at 05:20:25PM +0200, Edward Bartolo wrote:
> Hi all,
>
> By automatic connections I understood netman using the available
> essids for which it knows the password to connect. This means, it does
> not attempt to connect if no essid file is found under
> /etc/network/wifi.
>
On Sun, Sep 13, 2015 at 05:20:25PM +0200, Edward Bartolo wrote:
> [moved to the top, in hope that you'll re-read it ;-)]
> > -wpa_supplicant is a daemon designed to autoconnect to wireless
> > networks, supporting roaming and just about every type of wireless
> > network.
> >
> > -the wpa_supplica
On Sun, Sep 13, 2015 at 08:23:56PM +0200, Edward Bartolo wrote:
> Hi Hendrik Boom,
>
> You can achieve what you want by not using --auto-conn. This means,
> netman would not try to automatically search for an existing essid
> file matching the wifi sources available in the vicinity. In that
> case
Hi Hendrik Boom,
You can achieve what you want by not using --auto-conn. This means,
netman would not try to automatically search for an existing essid
file matching the wifi sources available in the vicinity. In that
case, connection to a wifi can be done on request by clicking a
button. This fea
Hi Hendrik Boom,
I will think about implementing your request as it makes sense and it
escaped my planning of netman. However, at this time I am very busy
which means, I will not be able to implement your wish immediately.
Nevertheless, I will make my utmost to do it as soon as I can.
Edward
On
On Sun, Sep 13, 2015 at 06:52:27PM +0200, Edward Bartolo wrote:
> That is easy to achieve from the GUI frontend. Just delete the
> connections you don't want.
>
> Edward
NONONO! I want to keep them around for when I do need them. I just
don't want it automatic.
Examples:
A company's interna
On Sun, Sep 13, 2015 at 05:20:25PM +0200, Edward Bartolo wrote:
> Hi all,
>
> By automatic connections I understood netman using the available
> essids for which it knows the password to connect. This means, it does
> not attempt to connect if no essid file is found under
> /etc/network/wifi.
>
>
Hi all,
By automatic connections I understood netman using the available
essids for which it knows the password to connect. This means, it does
not attempt to connect if no essid file is found under
/etc/network/wifi.
Edward
On 13/09/2015, ibid...@gmail.com wrote:
> On Sun, Sep 13, 2015 at 02
On Sun, Sep 13, 2015 at 02:35:43PM +0200, Edward Bartolo wrote:
> Hi all,
>
> As I am approaching the final stages of Pre-Alpha development, I would
> like to ask how netman should behave when 'automatic connections' are
> enabled.
> Needless to state the obvious, here, we are not doing Microsoft
Hi Edward,
On 09/13/2015 02:35 PM, Edward Bartolo wrote:
> At the moment, I am thinking about how netman should behave when
> automatic searching and connecting to wifi hotspots is enabled. I
> already have an idea how this can be achieved, but I want to use
> the least of processing time possibl
Hi all,
Making the above changes is only a matter of a few minutes in Lazarus.
In the mainform:
AlreadyAttemptedToAutoConnect: boolean;
Set the above to false when the form is created;
At the event handlers for all Connect buttons set
AlreadyAttemptedToAutoConnect to false;
In the timer's event
Hi all,
As I am approaching the final stages of Pre-Alpha development, I would
like to ask how netman should behave when 'automatic connections' are
enabled.
Needless to state the obvious, here, we are not doing Microsoft, but
rather, we want to keep netman as simple as it can be. Yes, there are
13 matches
Mail list logo
