Autore: Edward Bartolo Data: To: fsmithred CC: dng Oggetto: Re: [DNG] netman: support for wlan1, wlan2, ... and eth1, eth2,
.... and new systemd's naming scheme
> 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 >>
>
::
Re: [DNG] netman: support for wlan1…
