Also drop Requisite on connman.service as it's not really needed
(connman and network online services all have conditions on
!/dev/.kernel_ipconfig) and it causes a dependency failed message
as Requisites are evaluated before conditions.
Signed-off-by: Matthias Reichl <hias@horus.com>
Setup system hostname, /etc/resolv.conf and /etc/hosts in a service
that can be run independently of connman.
The volatile etc files are created in /run/libreelec instead of
/run/connman so they can be modified similarily to standard linux
installations with a writable /etc. Connman can then hook into
that and move resolv.conf management to /run/connman/resolv.conf when
it's started.
If kernel IP configuration is used the resolv info from the kernel
will be used to create resolv.conf. Users can also provide their
own resolv.conf file in /storage/.config/resolv.conf which takes
precedence over ther kernel info. If no resolv.conf info is present
a fallback with use the Google nameservers is created (as before).
Loopback network interface setup has been removed, this is already
set up by systemd.
Signed-off-by: Matthias Reichl <hias@horus.com>
[ZeroTier](https://zerotier.com/) is a VPN/SD-WAN that provides wide access to a virtual wide peer to peer ethernet network.
The daemon manages new interface networks under the `zt` prefix, and handle all the ip configuration under those interrfaces.
After [battling](https://github.com/zerotier/ZeroTierOne/issues/868) for a whole week figuring why the IPv6 addresses didn't show up on that interface under LibreElec, I found the issue was related to the configuration on `connman` regarding which interfaces it should manage.
This commit proposes a new network interface prefix to be included on the block list by default for new LibreElec installations, in order to avoid more people facing issues while trying to hook up their devices on the ZeroTier network.
