Autor: Edward Bartolo Data: A: tilt!, dng Assumpte: Re: [DNG] netman: support for wlan1, wlan2, ... and eth1, eth2,
.... and new systemd's naming scheme
or better wlan and eth are enough instead of long words.
On 01/10/2015, Edward Bartolo <edbarx@???> wrote: > This is a screenshot of the changes in the main window GUI to allow
> for network interfaces other than wlan0 and eth0. The displayed
> strings wlan0 and eth0 will be changed into wireless and ethernet
> respectively.
>
> http://s28.postimg.org/9bn1t4wz1/2015_10_01_180401_1600x900_scrot.png >
>
> Edward
>
>
> On 01/10/2015, Edward Bartolo <edbarx@???> wrote:
>> Hi Tilman,
>>
>> The backend will connect as I described.
>>
>> Yes, it will be an operation of the backend, but not new: connect and
>> disconnect will work the 'new' way.
>>
>> This operation will be triggered by passing the network device name
>> string to backend in addition to the usual parameters. To avoid
>> malicious users from passing crafted strings to popen or execl, the
>> same encoding algorithm that is used for essid encoding will be used.
>>
>> Edward
>>
>> On 01/10/2015, tilt! <tilt@???> wrote:
>>> Hi Edward,
>>>
>>> i assume you want the backend to do this?
>>>
>>> Will this be a new operation of the backend?
>>>
>>> If yes, what will trigger this operation?
>>>
>>> Kind regards,
>>> Tilman
>>>
>>> Am 01.10.2015 um 08:41 schrieb Edward Bartolo:
>>>> Hi All,
>>>>
>>>> This is the bewitched command that I need to do the above in a split
>>>> second with the least of coding:
>>>> sed 's/wlan0/new_device/g' /etc/network/wifi/interfaces_file >
>>>> /run/netman/tmp_int_file
>>>>
>>>> new_device is the replacement network device and tmp_int_file is the
>>>> new interfaces file that uses new_device
>>>>
>>>> To connect the backend would then use:
>>>> ifup -i /run/netman/tmp_int_file new_device
>>>>
>>>> Edward
>>>>
>>>>
>>>>
>>>> On 01/10/2015, Edward Bartolo <edbarx@???> wrote:
>>>>> Hi All,
>>>>>
>>>>> I devised a simple algorithm that can survive any new device naming
>>>>> scheme: systemd & co can think of any naming convention they dream of,
>>>>> the new algorithm will survive that. It also allows me to use the same
>>>>> configuration files as they are without modification. wlan0 and eth0
>>>>> will be simply placeholders for network device names. This means,
>>>>> coding can be greatly simplified.
>>>>>
>>>>> The algorithm:
>>>>> i) copy the essid/eth0 interfaces file to a temporary file system like
>>>>> /run/netman. During the copy procedure, replace wlan0/eth0 with the
>>>>> respective network device name.
>>>>> ii) run the connect/disconnect function using the newly created file
>>>>> in the temporary file system and using the new network device name
>>>>> iii) delete the newly created file in the temporary file system
>>>>>
>>>>> Simply, easy and extremely flexible.
>>>>>
>>>>> Tilt and fsmithred, you will soon be able to connect to whatever
>>>>> device you like.
>>>>>
>>>>>
>>>>> Edward
>>>>>
>>>>>
>>>>>
>>>>> On 01/10/2015, Hendrik Boom <hendrik@???> wrote:
>>>>>> On Wed, Sep 30, 2015 at 09:09:52PM +0200, Edward Bartolo wrote:
>>>>>>> Hi All,
>>>>>>>
>>>>>>> My next coding task is to implement support for other network
>>>>>>> devices
>>>>>>> besides eth0 and wlan0.
>>>>>>>
>>>>>>> Since supporting other network devices essentially is including the
>>>>>>> new device names in the essid interfaces file, I am thinking of
>>>>>>> whether it is possible to hook the system file reader function to
>>>>>>> replace part of the read file so that I wouldn't need to change
>>>>>>> anything in the files themselves. The reason is it shouldn't matter
>>>>>>> which wifi or wired connection one uses to connect a network.
>>>>>>
>>>>>> They may operate at different speeds.
>>>>>> They may connect to different networks.
>>>>>>
>>>>>> -- hendrik
>>>>>> _______________________________________________
>>>>>> Dng mailing list
>>>>>> Dng@???
>>>>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng >>>>>>
>>>>>
>>>
>>>
>>> --
>>> WWW: http://tk-sls.de >>>
>>
>
::
Re: [DNG] netman: support for wlan1…
%20copy%20the%20essid/eth0%20interfaces%20file%20to%20a%20temporary%20file%20system%20like%0A>%20>>>>>%20/run/netman.%20During%20the%20copy%20procedure,%20replace%20wlan0/eth0%20with%20the%0A>%20>>>>>%20respective%20network%20device%20name.%0A>%20>>>>>%20ii)%20run%20the%20connect/disconnect%20function%20using%20the%20newly%20created%20file%0A>%20>>>>>%20in%20the%20temporary%20file%20system%20and%20using%20the%20new%20network%20device%20name%0A>%20>>>>>%20iii)%20delete%20the%20newly%20created%20file%20in%20the%20temporary%20file%20system%0A>%20>>>>>%0A>%20>>>>>%20Simply,%20easy%20and%20extremely%20flexible.%0A>%20>>>>>%0A>%20>>>>>%20Tilt%20and%20fsmithred,%20you%20will%20soon%20be%20able%20to%20connect%20to%20whatever%0A>%20>>>>>%20device%20you%20like.%0A>%20>>>>>%0A>%20>>>>>%0A>%20>>>>>%20Edward%0A>%20>>>>>%0A>%20>>>>>%0A>%20>>>>>%0A>%20>>>>>%20On%2001/10/2015,%20Hendrik%20Boom%20<hendrik@???>%20wrote:%0A>%20>>>>>>%20On%20Wed,%20Sep%2030,%202015%20at%2009:09:52PM%20+0200,%20Edward%20Bartolo%20wrote:%0A>%20>>>>>>>%20Hi%20All,%0A>%20>>>>>>>%0A>%20>>>>>>>%20My%20next%20coding%20task%20is%20to%20implement%20support%20for%20other%20network%0A>%20>>>>>>>%20devices%0A>%20>>>>>>>%20besides%20eth0%20and%20wlan0.%0A>%20>>>>>>>%0A>%20>>>>>>>%20Since%20supporting%20other%20network%20devices%20essentially%20is%20including%20the%0A>%20>>>>>>>%20new%20device%20names%20in%20the%20essid%20interfaces%20file,%20I%20am%20thinking%20of%0A>%20>>>>>>>%20whether%20it%20is%20possible%20to%20hook%20the%20system%20file%20reader%20function%20to%0A>%20>>>>>>>%20replace%20part%20of%20the%20read%20file%20so%20that%20I%20wouldn't%20need%20to%20change%0A>%20>>>>>>>%20anything%20in%20the%20files%20themselves.%20The%20reason%20is%20it%20shouldn't%20matter%0A>%20>>>>>>>%20which%20wifi%20or%20wired%20connection%20one%20uses%20to%20connect%20a%20network.%0A>%20>>>>>>%0A>%20>>>>>>%20They%20may%20operate%20at%20different%20speeds.%0A>%20>>>>>>%20They%20may%20connect%20to%20different%20networks.%0A>%20>>>>>>%0A>%20>>>>>>%20--%20hendrik%0A>%20>>>>>>%20_______________________________________________%0A>%20>>>>>>%20Dng%20mailing%20list%0A>%20>>>>>>%20Dng@???%0A>%20>>>>>>%20https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng%0A>%20>>>>>>%0A>%20>>>>>%0A>%20>>>%0A>%20>>>%0A>%20>>>%20--%0A>%20>>>%20WWW:%20http://tk-sls.de%0A>%20>>>%0A>%20>>%0A>%20>%0A>%20%0A>%20 "Reply to this message")
