Re: Wireless card on New users computer

[Marc Stephan Nkouly]

Greetings
Just to confirm my wifi card is now working
I have search for the package "firmware-iwlwifi" using the browser and
found the page https://wiki.debian.org/iwlwifi from there I had just
followed the instructions. I also admit that I made use of the text editor
"nano" to edit the list source.
As much as am usually afraid of the CLI I start enjoying it.
Are they any resources anyone can share for me to learn more about it and
most of all harness its power?

Thanks

Marc Stephan Nkouly
Digital Consultant
bp: 5180 Nkwen
Bamenda
Cameroon

 Mobile:
 00 237 6 77 95 77 55
 00 237 6 90 89 51 52

"Technical people tend to fall into two categories: Specialists
and Generalists. The Specialist learns more and more about a
narrower and narrower field, until he eventually, in the limit,
knows everything about nothing. The Generalist learns less and
less about a wider and wider field until eventually, he knows
nothing about everything." - William Stucke - AfrISPA




On Fri, Nov 23, 2018 at 3:14 PM  wrote:

> On Fri, Nov 23, 2018 at 02:30:42PM +0100, Marc Stephan Nkouly wrote:
> > Sorry for not giving enough details initially.
>
> No worries.
>
> > My laptop is LENOVO IDEA PAD 300
> > INTEL PROCESSOR of 64 Bits with 4 G Ram & 500 HDD
> > Is true I had installed UBUNTU 18.04 But didn't appreciate it's sluginesh
> > Ànd now am running DEBIAN 9 with GNOME 3 Desktop environment.
> > Is true while doing the installation I saw a warning message that my
> > Wireless card require a non free driver with bthe name " iw l
> wifi-3160-17 "
>
> Thanks for the details.
>
> I see. This is actually the info needed here (actually the driver is
> probably
> called "iwlwifi-3160-17", see below).
>
> > But I didn't had the disc with it as the system asked me to insert it.
> > I have done my installation using NET INSTALL and got all the packages
> from
> > the Wired connection.
>
> Asking "apt-file" (this is a very useful command, which is found in a
> package with the same name):
>
>   tomas@trotzki:~$ apt-file search iwlwifi-3160
>   firmware-iwlwifi: /lib/firmware/iwlwifi-3160-12.ucode
>   firmware-iwlwifi: /lib/firmware/iwlwifi-3160-14.ucode
>   firmware-iwlwifi: /lib/firmware/iwlwifi-3160-16.ucode
>   firmware-iwlwifi: /lib/firmware/iwlwifi-3160-17.ucode
>   firmware-iwlwifi: /lib/firmware/iwlwifi-3160-9.ucode
>
> (Apt-file searches for packages containing a file with that name) reveals
> that iwlwifi-3160-17.ucode is contained in a package named
> "firmware-iwlwifi"
> (the suffix .ucode suggests that those are "microcode files", i.e. firmware
> to be loaded onto the processor embedded in your wifi hardware.
>
> So installing the package "firmware-iwlwifi" should get you going.
>
> Note that the package itself is in the non-free repository (hardware
> vendors
> sometimes distribute non-free software and don't document their hardware
> in a way that would allow us to write software for it, alas). So possibly
> you would have to enable the non-free repository. Don't hesitate to ask
> if you are unsure.
>
> > I also admit that am a beginners and don't feel comfortable enough to
> edit
> > files using the command line. Nevertheless am here because I want to
> learn.
> > Am also attaching what I had snap during the installation.
>
> Don't worry. We all have things to learn -- actually that is part of the
> fun.
>
> Cheers
> -- tomás
>

Re: Any directional antennas recommendations?

[Alexander V. Makartsev]

On 24.11.2018 3:41, Hubert Hauser wrote:
> Hello!
>
> I need to connect to a distant Wi-Fi network. I consider buying a
> parabolic antenna. I want to have 10 km range and long amplification.
> Will TP-Link TL-ANT2424B be a good aerial?
>
> --
>
> Best wishes,
> Hubert.
>
According to specifications of the TL-ANT2424B you should be getting
around 30Mbps. [1]
Of course, you have to install antennas on both sides, as Doug already
suggested, to make them "talk" in both directions and also make sure
there are minimal possible obstructions between them, especially
concrete or wooden buildings, trees, high voltage power lines, etc.
You have to mount them on a poles long enough to compensate for horizon
curvature and direct them at each other to get maximum possible signal
strength.
Also keep in mind that this setup will be prone to weather conditions
like rain, snow, wind and could temporally make signal strength worse.

[1]
https://www.tp-link.com/us/products/details/cat-5067_TL-ANT2424B.html#specifications

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Re: Any directional antennas recommendations?

[Eike Lantzsch]

On Saturday, November 24, 2018 4:28:01 PM -03 Alexander V. Makartsev wrote:
> On 24.11.2018 3:41, Hubert Hauser wrote:
> > Hello!
> > 
> > I need to connect to a distant Wi-Fi network. I consider buying a
> > parabolic antenna. I want to have 10 km range and long amplification.
> > Will TP-Link TL-ANT2424B be a good aerial?
> > 
> > --
> > 
> > Best wishes,
> > Hubert.
> 
> According to specifications of the TL-ANT2424B you should be getting
> around 30Mbps. [1]
> Of course, you have to install antennas on both sides, as Doug already
> suggested, to make them "talk" in both directions and also make sure
> there are minimal possible obstructions between them, especially
> concrete or wooden buildings, trees, high voltage power lines, etc.

And don't just think of line-of-sight but also take the Fresnel-Zone* into 
account because every dB counts. You might want to install WiMax, which is 
designed to cover distances of up to 50km instead of being bent on WiFi. Using 
high-gain directional antennas makes your installation illegal in most 
countries unless you are a licensed radio amateur. But even then you need to 
stay within the assigned frequenies for amateur radio and you are not allowed 
to encrypt.

[*] https://en.wikipedia.org/wiki/Fresnel_zone

> You have to mount them on a poles long enough to compensate for horizon
> curvature and direct them at each other to get maximum possible signal
> strength.
> Also keep in mind that this setup will be prone to weather conditions
> like rain, snow, wind and could temporally make signal strength worse.
> 
> [1]
> https://www.tp-link.com/us/products/details/cat-5067_TL-ANT2424B.html#specif
> ications

-- 
Eike Lantzsch ZP6CGE

Re: Any directional antennas recommendations?

[Roger Price]

On Fri, 23 Nov 2018, Hubert Hauser wrote:


I need to connect to a distant Wi-Fi network. I consider buying a
parabolic antenna. I want to have 10 km range and long amplification.
Will TP-Link TL-ANT2424B be a good aerial?


Given your 10km range, it might be interesting to calculate the Fresnel Zone 
radius to identify obstructions outside the line of sight. See 
https://en.wikipedia.org/wiki/Fresnel_zone


Roger

Re: Any directional antennas recommendations?

[Gene Heskett]

On Saturday 24 November 2018 06:28:01 Alexander V. Makartsev wrote:

> On 24.11.2018 3:41, Hubert Hauser wrote:
> > Hello!
> >
> > I need to connect to a distant Wi-Fi network. I consider buying a
> > parabolic antenna. I want to have 10 km range and long
> > amplification. Will TP-Link TL-ANT2424B be a good aerial?
> >
> > --
> >
> > Best wishes,
> > Hubert.
>
> According to specifications of the TL-ANT2424B you should be getting
> around 30Mbps. [1]
> Of course, you have to install antennas on both sides, as Doug already
> suggested, to make them "talk" in both directions and also make sure
> there are minimal possible obstructions between them, especially
> concrete or wooden buildings, trees, high voltage power lines, etc.
> You have to mount them on a poles long enough to compensate for
> horizon curvature and direct them at each other to get maximum
> possible signal strength.

We have a criteria for that, called the first fresnel zone clearance for 
determining the clearance needed to get past any obstacles in the path. 
That diameter varies with the distance and calculations must include the 
earths curvature. That criteria is that a path straight between the 
points, must be clear by a wave length increase of the path caused by 
the signal if it diverges from a straight line far enough to add 1 
wavelength to the path at that frequency as if the surface in the middle 
that it was glancing off of was a mirror. For really long hops, that 
clearance distance can be 100 feet or more. 

For a 90 mile hop at 7 GHz we had to go cut brush that wanted to be 
trees, on top of Pine Ridge (not the SD reservation town by the same 
name) between a microwave site on Battle Mtn SD, to the middle of the 
plateau of the Agate Beds National Monument in western NE. That was part 
of a 2 way path from Rapid City to the monument pulled off by cross 
polarization, tight filters and 1 watt transmitters. The southbound path 
turned east to KDUH-tv so we could switch the programming in Rapid City, 
SD.

> Also keep in mind that this setup will be prone to weather conditions
> like rain, snow, wind and could temporally make signal strength worse.
>
It's also subject to the sun rising and falling. About 30 minutes of 
cyclic fading for each transition. But they don't tell you that in 
school. :(

> [1]
> https://www.tp-link.com/us/products/details/cat-5067_TL-ANT2424B.html#
>specifications



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: VLC doesn't shutdown when closed

[Gary Dale]

On 2018-11-23 3:53 a.m., Curt wrote:

On 2018-11-22, Gary Dale  wrote:

On 2018-11-22 10:26 a.m., Curt wrote:

On 2018-11-22, Gary Dale  wrote:

I looked for a keep running option (and VLC does have a lot of options)
but couldn't find one.


If in 'Simple Preferences' under 'Playlists and instances' 'use only one
instance when started from file manager' isn't checked the phenomenon
has been known to occur (if you're starting VLC from a file
manager).

If not and on the other hand this appears to be a known bug. How you are
closing the app might be pertinent. 'Ctrl Q' after stopping the video?
Or some other way? Have you experimented in this regard?


Interesting - if I press the stop button on the player, vlc terminates
properly.


We live in an imperfect world, though this isn't exactly what you'd call
counter-intuitive, either.

Maybe the VLC people would argue this isn't a bug, as you might be
streaming to your Aunt Tilly in the other bedroom and only want to free
up screen real estate by closing the video's window on the source machine.


That would be equally served by the minimize button.

Moreover I will note that this is a new behaviour. I've been using VLC 
for a long time and this behaviour is not normal for it.


Finally, I will note that your example only makes sense if VLC is being 
used to stream a video. It doesn't make sense when the stream option 
isn't being used.

Re: Still unable to restart networking on Debian 9 text mode only

[Gary Dale]

On 2018-11-23 8:25 a.m., Luciano Andress Martini wrote:

Additional information - Again Debian 9.6 Fresh Install without
graphical interface:

cat /etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug enp0s3
iface enp0s3 inet static
 address 10.5.0.2/24
 gateway 10.5.0.1
 # dns-* options are implemented by the resolvconf package, if installed
 dns-nameservers 8.8.8.8
 dns-search neoconsig.local

Just changed 10.5.0.2 to 10.5.0.3

#ifdown enp0s3
#ifup enp0s3


Reco has already explained why this approach is incorrect.

My own two cents on the problem is that Interfaces is meant to define 
how the network is brought up, not to change a running network. If you 
want to change a running network, use ifconfig or ip to change the 
address. e.g. ifconfig enp-s3 10.5.0.3 should work since all you are 
changing is the ip address.

Re: VLC doesn't shutdown when closed

[Brad Rogers]

On Sat, 24 Nov 2018 12:11:42 -0500
Gary Dale  wrote:

Hello Gary,

>Moreover I will note that this is a new behaviour. I've been using VLC 
>for a long time and this behaviour is not normal for it.

It /might/ be just you, Gary:

Using VLC here, and closing without stopping video playback, clicking
the close gadget (top right of window) VLC shuts down, and leaves no
trace of having been run.  IOW, there's no task left showing in the
activity monitor -  in fact, it's entirely possible to watch the monitor
showing VLC shutting down cleanly.

What happens when/if you move the existing config file out of the way?

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
It's only bits of plastic, lines projected on the wall
Keep It Clean - The Vibrators


pgpgOg0vMYJS_.pgp
Description: OpenPGP digital signature

Worked example, was Re: Still unable to restart networking on Debian 9 text mode only

[David Wright]

On Sat 24 Nov 2018 at 12:25:20 (-0500), Gary Dale wrote:
> On 2018-11-23 8:25 a.m., Luciano Andress Martini wrote:
> > Additional information - Again Debian 9.6 Fresh Install without
> > graphical interface:
> > 
> > cat /etc/network/interfaces:
> > 
> > # This file describes the network interfaces available on your system
> > # and how to activate them. For more information, see interfaces(5).
> > 
> > source /etc/network/interfaces.d/*
> > 
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> > 
> > # The primary network interface
> > allow-hotplug enp0s3
> > iface enp0s3 inet static
> >  address 10.5.0.2/24
> >  gateway 10.5.0.1
> >  # dns-* options are implemented by the resolvconf package, if installed
> >  dns-nameservers 8.8.8.8
> >  dns-search neoconsig.local
> > 
> > Just changed 10.5.0.2 to 10.5.0.3
> > 
> > #ifdown enp0s3
> > #ifup enp0s3
> 
> Reco has already explained why this approach is incorrect.

The OP seems to prefer imagining a bug rather than taking much notice
of the replies.

> My own two cents on the problem is that Interfaces is meant to define
> how the network is brought up, not to change a running network.

Yes, but it also appears that interfaces also defines how the network
is brought down again, which is what the OP doesn't understand.

> If you
> want to change a running network, use ifconfig or ip to change the
> address. e.g. ifconfig enp-s3 10.5.0.3 should work since all you are
> changing is the ip address.

I can't see any advantage in this as you have to do all the grunt work
yourself instead of letting ifdown/ifup do it for you. For example:

Here's my normal /e/n/i:

$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug enp0s14
iface enp0s14 inet dhcp
$ 

I set up two static alternatives, one using the same address (13) as I
get from the router, and one wacky one (213) in the "intruder" range:

allow-hotplug enp0s14
iface enp0s14 inet static
 address 192.168.1.13
 netmask 255.255.255.0
 gateway 192.168.1.1
 dns-nameservers 192.168.1.1

and

allow-hotplug enp0s14
iface enp0s14 inet static
 address 192.168.1.213
 netmask 255.255.255.0
 gateway 192.168.1.1
 dns-nameservers 192.168.1.1

(the rest of each file is unchanged from the normal one).

Running a script like:

#!/bin/bash
ifdown enp0s14
cp /etc/network/interfaces-static-213 /etc/network/interfaces
ifup enp0s14

releases the lease, downs the avahi-daemon, changes the network
address, restarts the ssh server, reconfigures ntpd, and ups the
avahi-daemon. My ssh session also goes dead (as I was logged in
that way).

Logging in on 192.168.1.213 instead (and avoiding polluting my
known_hosts file) I can now run a similar script to the above,
that has the line
cp /etc/network/interfaces-static-13 /etc/network/interfaces
or
cp /etc/network/interfaces-normal-dhcp /etc/network/interfaces
in it, and my old ssh session comes alive again (the new session
going dead of course). The logs show all the other changes being
reversed back to normal, with a new lease etc.

So you can see the extra work (worth more than two cents) that
the higher level commands do for you automatically, thanks to
/etc/network/if-*.d/*

Cheers,
David.

Re: Worked example, was Re: Still unable to restart networking on Debian 9 text mode only

[Gary Dale]

On 2018-11-24 9:05 p.m., David Wright wrote:

On Sat 24 Nov 2018 at 12:25:20 (-0500), Gary Dale wrote:

On 2018-11-23 8:25 a.m., Luciano Andress Martini wrote:

Additional information - Again Debian 9.6 Fresh Install without
graphical interface:

cat /etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug enp0s3
iface enp0s3 inet static
  address 10.5.0.2/24
  gateway 10.5.0.1
  # dns-* options are implemented by the resolvconf package, if installed
  dns-nameservers 8.8.8.8
  dns-search neoconsig.local

Just changed 10.5.0.2 to 10.5.0.3

#ifdown enp0s3
#ifup enp0s3

Reco has already explained why this approach is incorrect.

The OP seems to prefer imagining a bug rather than taking much notice
of the replies.


My own two cents on the problem is that Interfaces is meant to define
how the network is brought up, not to change a running network.

Yes, but it also appears that interfaces also defines how the network
is brought down again, which is what the OP doesn't understand.


If you
want to change a running network, use ifconfig or ip to change the
address. e.g. ifconfig enp-s3 10.5.0.3 should work since all you are
changing is the ip address.

I can't see any advantage in this as you have to do all the grunt work
yourself instead of letting ifdown/ifup do it for you. For example:

Here's my normal /e/n/i:

$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug enp0s14
iface enp0s14 inet dhcp
$

I set up two static alternatives, one using the same address (13) as I
get from the router, and one wacky one (213) in the "intruder" range:

allow-hotplug enp0s14
iface enp0s14 inet static
  address 192.168.1.13
  netmask 255.255.255.0
  gateway 192.168.1.1
  dns-nameservers 192.168.1.1

and

allow-hotplug enp0s14
iface enp0s14 inet static
  address 192.168.1.213
  netmask 255.255.255.0
  gateway 192.168.1.1
  dns-nameservers 192.168.1.1

(the rest of each file is unchanged from the normal one).

Running a script like:

#!/bin/bash
ifdown enp0s14
cp /etc/network/interfaces-static-213 /etc/network/interfaces
ifup enp0s14

releases the lease, downs the avahi-daemon, changes the network
address, restarts the ssh server, reconfigures ntpd, and ups the
avahi-daemon. My ssh session also goes dead (as I was logged in
that way).

Logging in on 192.168.1.213 instead (and avoiding polluting my
known_hosts file) I can now run a similar script to the above,
that has the line
cp /etc/network/interfaces-static-13 /etc/network/interfaces
or
cp /etc/network/interfaces-normal-dhcp /etc/network/interfaces
in it, and my old ssh session comes alive again (the new session
going dead of course). The logs show all the other changes being
reversed back to normal, with a new lease etc.

So you can see the extra work (worth more than two cents) that
the higher level commands do for you automatically, thanks to
/etc/network/if-*.d/*

Cheers,
David.


That, of course, assumes that ifup and ifdown work on your system. They 
don't work on two of my systems that uses systemd-networkd to control 
the network. However ifconfig works on one and ip works on the other 
(although they are both running Stretch, one is a new server-type 
install while the other has been upgraded over the years from earlier 
versions).


The lower-level tools tend to be more flexible and are more agnostic 
regarding how your network is set up.


In the case of the OP, he needs to change his interfaces file no matter 
how he changes the network. However the order of commands isn't 
important when he uses ifconfig or ip to update the ip address - he can 
do it before or after editing interfaces. Moreover, it takes one fewer 
command. And it's worth learning how to use these tools if you are 
working with networks.

Re: VLC doesn't shutdown when closed

[Gary Dale]

On 2018-11-24 12:28 p.m., Brad Rogers wrote:

On Sat, 24 Nov 2018 12:11:42 -0500
Gary Dale  wrote:

Hello Gary,


Moreover I will note that this is a new behaviour. I've been using VLC
for a long time and this behaviour is not normal for it.

It /might/ be just you, Gary:

Using VLC here, and closing without stopping video playback, clicking
the close gadget (top right of window) VLC shuts down, and leaves no
trace of having been run.  IOW, there's no task left showing in the
activity monitor -  in fact, it's entirely possible to watch the monitor
showing VLC shutting down cleanly.

What happens when/if you move the existing config file out of the way?

When I do that, VLC behaves itself. However when I added the faster and 
slower buttons to the timeline panel, VLC stopped shutting down again. 
If I remove them again, vlc shuts down properly. When I put them back, 
it acts up again.

Re: Worked example, was Re: Still unable to restart networking on Debian 9 text mode only

[john doe]

On 11/25/2018 3:05 AM, David Wright wrote:
> On Sat 24 Nov 2018 at 12:25:20 (-0500), Gary Dale wrote:
>> On 2018-11-23 8:25 a.m., Luciano Andress Martini wrote:
>>> Additional information - Again Debian 9.6 Fresh Install without
>>> graphical interface:
>>>
>>> cat /etc/network/interfaces:
>>>
>>> # This file describes the network interfaces available on your system
>>> # and how to activate them. For more information, see interfaces(5).
>>>
>>> source /etc/network/interfaces.d/*
>>>
>>> # The loopback network interface
>>> auto lo
>>> iface lo inet loopback
>>>
>>> # The primary network interface
>>> allow-hotplug enp0s3
>>> iface enp0s3 inet static
>>>  address 10.5.0.2/24
>>>  gateway 10.5.0.1
>>>  # dns-* options are implemented by the resolvconf package, if installed
>>>  dns-nameservers 8.8.8.8
>>>  dns-search neoconsig.local
>>>
>>> Just changed 10.5.0.2 to 10.5.0.3
>>>
>>> #ifdown enp0s3
>>> #ifup enp0s3
>>
>> Reco has already explained why this approach is incorrect.
> 
> The OP seems to prefer imagining a bug rather than taking much notice
> of the replies.
> 
>> My own two cents on the problem is that Interfaces is meant to define
>> how the network is brought up, not to change a running network.
> 
> Yes, but it also appears that interfaces also defines how the network
> is brought down again, which is what the OP doesn't understand.
> 
>> If you
>> want to change a running network, use ifconfig or ip to change the
>> address. e.g. ifconfig enp-s3 10.5.0.3 should work since all you are
>> changing is the ip address.
> 
> I can't see any advantage in this as you have to do all the grunt work
> yourself instead of letting ifdown/ifup do it for you. For example:
> 
> Here's my normal /e/n/i:
> 
> $ cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> source /etc/network/interfaces.d/*
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> allow-hotplug enp0s14
> iface enp0s14 inet dhcp
> $ 
> 
> I set up two static alternatives, one using the same address (13) as I
> get from the router, and one wacky one (213) in the "intruder" range:
> 
> allow-hotplug enp0s14
> iface enp0s14 inet static
>  address 192.168.1.13
>  netmask 255.255.255.0
>  gateway 192.168.1.1
>  dns-nameservers 192.168.1.1
> 
> and
> 
> allow-hotplug enp0s14
> iface enp0s14 inet static
>  address 192.168.1.213
>  netmask 255.255.255.0
>  gateway 192.168.1.1
>  dns-nameservers 192.168.1.1
> 
> (the rest of each file is unchanged from the normal one).
> 
> Running a script like:
> 
> #!/bin/bash
> ifdown enp0s14
> cp /etc/network/interfaces-static-213 /etc/network/interfaces
> ifup enp0s14
> 
> releases the lease, downs the avahi-daemon, changes the network
> address, restarts the ssh server, reconfigures ntpd, and ups the
> avahi-daemon. My ssh session also goes dead (as I was logged in
> that way).
> 
> Logging in on 192.168.1.213 instead (and avoiding polluting my
> known_hosts file) I can now run a similar script to the above,
> that has the line
> cp /etc/network/interfaces-static-13 /etc/network/interfaces
> or
> cp /etc/network/interfaces-normal-dhcp /etc/network/interfaces
> in it, and my old ssh session comes alive again (the new session
> going dead of course). The logs show all the other changes being
> reversed back to normal, with a new lease etc.
> 

TL-DR.

Instead of using the cp command, one could use mapping stanza:

http://manpages.ubuntu.com/manpages/bionic/man5/interfaces.5.html#mappings

-- 
John Doe