Hi All,

The changes have been uploaded. The backend should now support other
devices besides wlan0 and eth0.

Edward

On 11/10/2015, Edward Bartolo <edbarx@???> wrote:
> Hi,
>
> I am coding the final function before I can upload the latest changes
> to the backend to support ethN and wlanN.
>
> Please, be aware that this time, there have been many changes compared
> to other uploads.
>
> Edward
>
> On 10/10/2015, Edward Bartolo <edbarx@???> wrote:
>> Hi,
>>
>> The frontend GUI presently does not match what the backend can do
>> which still is unable to support wlanN and ethN. Currently, I am
>> working on enabling the backend to handle wlanN and ethN. However, as
>> I expected, the code has become far more complicated than before, and
>> I am still debugging it.
>>
>> Currently, I am also engaged doing some 'gardening' to grow my
>> vegetables as I am having stomach and bowel pain due to
>> 'uncontrolled' pesticide use by vegetable sellers.
>>
>> Regarding the GUI being intuitive, I am afraid, I cannot satisfy
>> everyone. Huge commercial software companies also write software that
>> needs users to get accustomed to. A huge case in point was when
>> Microsoft replaced menus in Microsoft Office, but still, there are
>> office power users who claim, the new office design is more productive
>> and more intuitive.
>>
>> It is quite clear that what is obvious and intuitive to person A may
>> not be obvious to some other person B.
>>
>> However, I will make the changes you mentioned. The Network Interfaces
>> Files tab will be recaptioned to Saved Connections.
>>
>> Edward
>>
>> On 10/10/2015, fsmithred <fsmithred@???> wrote:
>>> It does compile and run on sid.
>>>
>>>
>>> Some thoughts on ease of use...
>>>
>>> If you try to connect without selecting a connection, there's an error
>>> message saying that you need to select a connection, but it's not
>>> obvious
>>> what to select. The physical interface list is showing, and that's not
>>> what you need to select. (Yeah, I tried connecting a few times with
>>> wlan0
>>> highlighted before I remembered what I was supposed to be doing.)
>>>
>>> A simple fix would be to change the label on the tab from "Network
>>> Interface Files" to something like "Connections" or "Saved connections".
>>> Likewise, if you auto-connect while the physical interface tab is
>>> showing,
>>> you don't know where you're connecting. The progress message at the
>>> bottom
>>> of the window that says "Connecting..." would be more helpful if it
>>> named
>>> the essid you were connecting to. (I think someone else mentioned this,
>>> so
>>> maybe you changed it already.) Or maybe put the interface files tab in
>>> front - that's the one most people will use, isn't it?
>>>
>>> -fsr
>>>
>>>
>>>
>>> On 10/07/2015 10:56 AM, Edward Bartolo wrote:
>>>>> One more thing. I tried it on sid, and got:
>>>>> "bash: /usr/bin/netman: cannot execute binary file: Exec format error"
>>>>> Does it need to be compiled on sid to run on sid?
>>>>
>>>> I presume yes.
>>>>
>>>> Edward
>>>>
>>>> On 07/10/2015, Edward Bartolo <edbarx@???> wrote:
>>>>> fsmithred, the backend still needs to be modified for those changes.
>>>>> Only the frontend has the changes. So, you have to wait for my next
>>>>> git push which will involve the backend mostly.
>>>>>
>>>>> Edward
>>>>>
>>>>> On 07/10/2015, fsmithred <fsmithred@???> wrote:
>>>>>> Yes, the link looks better.
>>>>>>
>>>>>> I'm testing the version you uploaded about 19 hours ago (aaof46...)
>>>>>> and running into some problems.
>>>>>>
>>>>>> The main window, upper left, says"Using: Wifi: wlan1, Wired: eth0"
>>>>>> but
>>>>>> I'm
>>>>>> actually using wlan0. The connection information window correctly
>>>>>> shows
>>>>>> wlan0 in use.
>>>>>>
>>>>>> If I try to change the default device, and I enter either wlan0 or
>>>>>> wlan1,
>>>>>> I get "Invalid device name. Valid characters are: a-z, A-Z, 0-9."
>>>>>>
>>>>>> Oh, I see I have to enter the wired device, too. With both fields
>>>>>> filled,
>>>>>> I get a different error.
>>>>>> "Unable to create file
>>>>>> "/home/user/.config/netman/netman.default.devices".
>>>>>>
>>>>>> If I create that file manually, then changing the default device
>>>>>> completes, and the file gets the right information. Did it a second
>>>>>> time
>>>>>> to change the device, and the file was updated correctly.
>>>>>>
>>>>>> One more thing. I tried it on sid, and got:
>>>>>> "bash: /usr/bin/netman: cannot execute binary file: Exec format
>>>>>> error"
>>>>>> Does it need to be compiled on sid to run on sid?
>>>>>>
>>>>>> Other than that, it seems to be working fine.
>>>>>>
>>>>>> -fsr
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 10/07/2015 07:57 AM, Edward Bartolo wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> This is the latest screenshot. I removed the ugly huge button and
>>>>>>> replaced it with a hyperlink. In the screenshot, the hyperlink has
>>>>>>> the
>>>>>>> mouse pointer above it although the pointer is not captured.
>>>>>>>
>>>>>>> http://postimg.org/image/4xzp8srht/
>>>>>>>
>>>>>>> Edward
>>>>>>>
>>>>>>> On 07/10/2015, Edward Bartolo <edbarx@???> wrote:
>>>>>>>>> If you're already getting a list of devices to display, couldn't
>>>>>>>>> you
>>>>>>>>> just
>>>>>>>>> verify that the chosen device matches one of those names? I don't
>>>>>>>>> know
>>>>>>>>> what it's like to test for illegal characters in the language
>>>>>>>>> you're
>>>>>>>>> using, but I can tell you it's a pain in the ass in bash.
>>>>>>>>
>>>>>>>> Yes, it is a good idea. List the available devices using ip link,
>>>>>>>> extract a list of available network interfaces, and verify that the
>>>>>>>> devices loaded from netman.default.devices is a valid device.
>>>>>>>>
>>>>>>>> Edward
>>>>>>>>
>>>>>>>> On 07/10/2015, fsmithred <fsmithred@???> wrote:
>>>>>>>>> One connection at a time should be enough for anyone. (Or they can
>>>>>>>>> edit
>>>>>>>>> their interfaces file.)
>>>>>>>>>
>>>>>>>>> If you're already getting a list of devices to display, couldn't
>>>>>>>>> you
>>>>>>>>> just
>>>>>>>>> verify that the chosen device matches one of those names? I don't
>>>>>>>>> know
>>>>>>>>> what it's like to test for illegal characters in the language
>>>>>>>>> you're
>>>>>>>>> using, but I can tell you it's a pain in the ass in bash.
>>>>>>>>>
>>>>>>>>> -fsr
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 10/06/2015 03:28 PM, Edward Bartolo wrote:
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> Now, the frontend can create a text file to declare a default
>>>>>>>>>> wifi
>>>>>>>>>> and
>>>>>>>>>> ethernet devices. Since this file is writable by ordinary
>>>>>>>>>> unprivileged
>>>>>>>>>> users, and because the file will be used by the backend to decide
>>>>>>>>>> which devices to use in cases where such a file exists, I am
>>>>>>>>>> thinking
>>>>>>>>>> about validating the device names before using popen or execl.
>>>>>>>>>> The
>>>>>>>>>> validation will check for illegal characters like shell
>>>>>>>>>> delimiters
>>>>>>>>>> which can be inserted by malicious users to run malicious
>>>>>>>>>> commands.
>>>>>>>>>> My
>>>>>>>>>> impression is that device names will be composed of letters from
>>>>>>>>>> the
>>>>>>>>>> English alphabet and digits with all other characters unallowed.
>>>>>>>>>>
>>>>>>>>>> With the backend directly accessing the text file, additional
>>>>>>>>>> parameters to define the network interface to use will be avoided
>>>>>>>>>> for
>>>>>>>>>> both Connect and Disconnect. This means, the backend command set
>>>>>>>>>> will
>>>>>>>>>> remain unaltered.
>>>>>>>>>>
>>>>>>>>>> Edward
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 06/10/2015, Edward Bartolo <edbarx@???> wrote:
>>>>>>>>>>>> Is it possible to run more than one instance of netman?
>>>>>>>>>>>
>>>>>>>>>>> No, only the previous versions allow more than one instance of
>>>>>>>>>>> netman
>>>>>>>>>>> to run. The current one I am working on (not yet pushed to git)
>>>>>>>>>>> prevents users from running more than one instance.
>>>>>>>>>>>
>>>>>>>>>>> Edward
>>>>>>>>>>>
>>>>>>>>>>> On 06/10/2015, Clarke Sideroad <clarke.sideroad@???>
>>>>>>>>>>> wrote:
>>>>>>>>>>>> On 10/06/2015 09:24 AM, Edward Bartolo wrote:
>>>>>>>>>>>>> In the case of more than one wifi and/or more than one
>>>>>>>>>>>>> ethernet
>>>>>>>>>>>>> connector, netman will either use decide by itself to use a
>>>>>>>>>>>>> device
>>>>>>>>>>>>> from the available list or choose a device from the defaults
>>>>>>>>>>>>> set
>>>>>>>>>>>>> by
>>>>>>>>>>>>> the user.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I think, netman should not support more than one active
>>>>>>>>>>>>> connection
>>>>>>>>>>>>> as
>>>>>>>>>>>>> is currently the case.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Please give feedback so that I start to work on the backend.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> There are cases when multiple connections and networks do come
>>>>>>>>>>>> in
>>>>>>>>>>>> handy,
>>>>>>>>>>>> but I think in those cases we are dealing with things that
>>>>>>>>>>>> might
>>>>>>>>>>>> be
>>>>>>>>>>>> better off started separately going back to the basics. AFAIK
>>>>>>>>>>>> Wicd
>>>>>>>>>>>> only
>>>>>>>>>>>> handles one connection at a time.
>>>>>>>>>>>>
>>>>>>>>>>>> Is it possible to run more than one instance of netman?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> Clarke
>>>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Dng mailing list
>>>>>> Dng@???
>>>>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>>>>>>
>>>>>
>>>
>>>
>>
>