Turris OS packages issueshttps://gitlab.nic.cz/turris/os/packages/-/issues2023-08-16T14:37:59+02:00https://gitlab.nic.cz/turris/os/packages/-/issues/374Mounting on /tmp/certstore failed: Invalid argument2023-08-16T14:37:59+02:00Josef SchlehoferMounting on /tmp/certstore failed: Invalid argumentReported on our [forum](https://forum.turris.cz/t/turris-os-4-0-beta1-is-released/10107/22?u=pepe).Reported on our [forum](https://forum.turris.cz/t/turris-os-4-0-beta1-is-released/10107/22?u=pepe).Turris OS 4.0https://gitlab.nic.cz/turris/os/packages/-/issues/373python3: requests does not install urllib3 dependency2019-05-06T00:04:18+02:00Vojtech Myslivecpython3: requests does not install urllib3 dependency`requests` python library depends on `urllib3`, however it is not installed automatically when I install `python3-requests` package.
This issue is a major one as `certgen` depends on `requests` and it is failing on missing `urrlib3`.
`...`requests` python library depends on `urllib3`, however it is not installed automatically when I install `python3-requests` package.
This issue is a major one as `certgen` depends on `requests` and it is failing on missing `urrlib3`.
```
root@turris: ~ # python3 /usr/libexec/sentinel_certgen.py --help
Traceback (most recent call last):
File "/usr/libexec/sentinel_certgen.py", line 35, in <module>
import requests
File "/usr/lib/python3.6/site-packages/requests/__init__.py", line 43, in <module>
import urllib3
ModuleNotFoundError: No module named 'urllib3'
[1] root@turris: ~ #
```
```
root@turris: ~ # opkg list-installed | grep requests
python-requests - 2.21.0-1
python3-requests - 2.21.0-3.6-1
root@turris: ~ # opkg list-installed | grep urllib
[1] root@turris: ~ #
```Turris OS 3.11.5https://gitlab.nic.cz/turris/os/packages/-/issues/372postinst of foris-controller-netmetr-module runs netmetr2019-05-21T15:33:47+02:00Vojtech Myslivecpostinst of foris-controller-netmetr-module runs netmetrnetmetr is run after installation of `foris-controller-netmetr-module` package which blocks and slows down an update process.netmetr is run after installation of `foris-controller-netmetr-module` package which blocks and slows down an update process.https://gitlab.nic.cz/turris/os/packages/-/issues/371deckard-gui: create deckart gui in foris2023-08-16T14:49:11+02:00Jan Pavlinecdeckard-gui: create deckart gui in foriscreate deckart GUI in foris.create deckart GUI in foris.Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/368emergingthreats: create new package for surricata2019-04-26T15:53:48+02:00Jan Pavlinecemergingthreats: create new package for surricataThis package should contain https://rules.emergingthreats.net/open/suricata/emerging.rules.tar.gz since it's used in ludus https://github.com/stratosphereips/Ludus/blob/master/install.py#L65
Related to issue https://gitlab.labs.nic.cz/t...This package should contain https://rules.emergingthreats.net/open/suricata/emerging.rules.tar.gz since it's used in ludus https://github.com/stratosphereips/Ludus/blob/master/install.py#L65
Related to issue https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/358Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/367haas-proxy: init script requires refactoring2023-08-16T14:38:01+02:00Karel Kocihaas-proxy: init script requires refactoringWe should refactor haas-proxy init script to be more sensible and to drop log files in favor of procd stderr logging.We should refactor haas-proxy init script to be more sensible and to drop log files in favor of procd stderr logging.Turris OS 5.1https://gitlab.nic.cz/turris/os/packages/-/issues/366unbound: fix dns-over-tls2019-06-14T15:35:57+02:00Jan Pavlinecunbound: fix dns-over-tlsfix dns-over-tlsfix dns-over-tlsTurris OS 3.11.5https://gitlab.nic.cz/turris/os/packages/-/issues/364keepalived: requires kmod-nf-ipvs2023-08-16T14:57:32+02:00Jan Pavlineckeepalived: requires kmod-nf-ipvsThis requirement prevents new keepalived from installing
Related forum topic https://forum.turris.cz/t/keepalived-depends-on-kmod-nf-ipvs-which-is-not-available/10036This requirement prevents new keepalived from installing
Related forum topic https://forum.turris.cz/t/keepalived-depends-on-kmod-nf-ipvs-which-is-not-available/10036https://gitlab.nic.cz/turris/os/packages/-/issues/361[note to dev] Unbound repositories moving to GitHub on 1 May 20192019-04-24T11:12:16+02:00Ghost User[note to dev] Unbound repositories moving to GitHub on 1 May 2019> We are excited to announce that on the 1st of May 2019, we will migrate
> the NSD and Unbound repositories to git and use GitHub for maintaining
> them. We are also going to use the GitHub infrastructure to manage tasks
> and community...> We are excited to announce that on the 1st of May 2019, we will migrate
> the NSD and Unbound repositories to git and use GitHub for maintaining
> them. We are also going to use the GitHub infrastructure to manage tasks
> and community contributions, collect user feedback and allow you to
> report software bugs.
>
> This means that on 1 May 2019, the following will happen for the NSD and
> Unbound projects:
>
> - Our SVN repositories will be made unavailable by replacing the
> contents of the SVN trunk with a single document pointing to GitHub
> - Bugzilla, our bug-tracking system, will be switched to read-only
> - We will accept contributions via a pull request on GitHub
> - Feature requests and bug reports should be submitted via GitHub issues
>
> This change is part of an ongoing effort to unify the experience for our
> community. Over the next weeks and months, all projects that NLnet Labs
> manages will be migrated. We are convinced that GitHub offers the best
> platform to cater to the needs of both our community and our developers.
>
> If you would like to get a head start, you can already start using
> GitHub for the NSD[0] and Unbound[1] projects today.
>
> Regards,
> Ralph
>
> [0] - https://github.com/nlnetlabs/nsd
> [1] - https://github.com/nlnetlabs/unboundhttps://gitlab.nic.cz/turris/os/packages/-/issues/360resolver-conf: Fix syntax error when run resolver init script2020-04-09T16:33:05+02:00Jan Pavlinecresolver-conf: Fix syntax error when run resolver init scriptresolver-conf: Fix syntax error when run resolver init script
```
root@turris# /etc/init.d/resolver restart
Called /etc/init.d/kresd stop
remove dhcp script
syntax error. Last token seen: +
Garbled time
Called /etc/init.d/kresd start
rem...resolver-conf: Fix syntax error when run resolver init script
```
root@turris# /etc/init.d/resolver restart
Called /etc/init.d/kresd stop
remove dhcp script
syntax error. Last token seen: +
Garbled time
Called /etc/init.d/kresd start
remove dhcp script
```Turris OS 5.0https://gitlab.nic.cz/turris/os/packages/-/issues/358ludus: create package2019-08-16T13:59:25+02:00Jan Pavlinecludus: create packagegithub repo https://github.com/stratosphereips/Ludus/
Configuration for ludus should probably look like this https://github.com/stratosphereips/Ludus/commit/acb6f1fd46acfa3ebdffea9bed919dc1e9c327b2github repo https://github.com/stratosphereips/Ludus/
Configuration for ludus should probably look like this https://github.com/stratosphereips/Ludus/commit/acb6f1fd46acfa3ebdffea9bed919dc1e9c327b2Turris OS 3.11.6Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/356notifier reports uci error2019-09-27T12:53:30+02:00Karel Kocinotifier reports uci errorSyslog on 4.0 is filled with reports from cron with:
```
/usr/bin/notifier: line 274: uci: not found
```Syslog on 4.0 is filled with reports from cron with:
```
/usr/bin/notifier: line 274: uci: not found
```Turris OS 4.0https://gitlab.nic.cz/turris/os/packages/-/issues/355lxc: network is not configured in default2019-09-27T12:53:19+02:00Karel Kocilxc: network is not configured in defaultWe should provide default LXC network configuration that would be connected to LAN. At the moment there is no default configuration and containers start without network.
As an example Alpine edge:
```root@turris:~# lxc-start -F -n alpin...We should provide default LXC network configuration that would be connected to LAN. At the moment there is no default configuration and containers start without network.
As an example Alpine edge:
```root@turris:~# lxc-start -F -n alpine
lxc-start: alpine: utils.c: safe_mount: 1707 No such file or directory - Failed to mount /usr/lib/lxc/rootfs/proc/tty onto /usr/lib/lxc/rootfs/proc/sys/net
OpenRC 0.41.2.f4b2a85138 is starting up Linux 4.14.111 (aarch64) [LXC]
* /proc is already mounted
* /run/openrc: creating directory
* /run/lock: creating directory
* /run/lock: correcting owner
* Caching service dependencies ... [ ok ]
* Migrating /var/lock to /run/lock ... [ ok ]
* Creating user login records ... [ ok ]
* Wiping /tmp directory ... [ ok ]
* Starting busybox syslog ... [ ok ]
* Starting busybox crond ... [ ok ]
* Starting networking ... * eth0 ...ip: ioctl 0x8913 failed: No such device
[ !! ]
* ERROR: networking failed to start
Welcome to Alpine Linux 3.8
Kernel 4.14.111 on an aarch64 (/dev/console)
alpine login: root
Welcome to Alpine!
The Alpine Wiki contains a large amount of how-to guides and general
information about administrating Alpine systems.
See <http://wiki.alpinelinux.org/>.
You can setup the system with the command: setup-alpine
You may change this message by editing /etc/motd.
alpine:~# ip l
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN qlen 1000
link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
alpine:~#
```Turris OS 4.0Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/packages/-/issues/354lxc: unable to run systemd container2019-12-10T16:03:58+01:00Karel Kocilxc: unable to run systemd containerSystemd based containers such as Debian are failing with following error:
```
lxc-start: debian: utils.c: safe_mount: 1707 No such file or directory - Failed to mount /usr/lib/lxc/rootfs/proc/tty onto /usr/lib/lxc/rootfs/proc/sys/net
...Systemd based containers such as Debian are failing with following error:
```
lxc-start: debian: utils.c: safe_mount: 1707 No such file or directory - Failed to mount /usr/lib/lxc/rootfs/proc/tty onto /usr/lib/lxc/rootfs/proc/sys/net
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
```
```
lxc-start: opensuse: utils.c: safe_mount: 1707 No such file or directory - Failed to mount /usr/lib/lxc/rootfs/proc/tty onto /usr/lib/lxc/rootfs/proc/sys/net
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
```
I suspect that we don;t have appropriate kernel configuration.Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/packages/-/issues/353haas-proxy: does not contain any scripts nor configuration2019-05-06T17:21:48+02:00Karel Kocihaas-proxy: does not contain any scripts nor configurationIt seems that there is something wrong with `haas-proxy` package in TOS 4.0. It contains only python module and nothing more.
```
root@turris:~# cat /usr/lib/opkg/info/haas-proxy.list
/usr/lib/python3.6/site-packages/haas_proxy-1.9-py3....It seems that there is something wrong with `haas-proxy` package in TOS 4.0. It contains only python module and nothing more.
```
root@turris:~# cat /usr/lib/opkg/info/haas-proxy.list
/usr/lib/python3.6/site-packages/haas_proxy-1.9-py3.6.egg-info/PKG-INFO
/usr/lib/python3.6/site-packages/haas_proxy-1.9-py3.6.egg-info/dependency_links.txt
/usr/lib/python3.6/site-packages/haas_proxy-1.9-py3.6.egg-info/requires.txt
/usr/lib/python3.6/site-packages/haas_proxy/proxy.py
/usr/lib/python3.6/site-packages/haas_proxy-1.9-py3.6.egg-info/SOURCES.txt
/usr/lib/python3.6/site-packages/haas_proxy/__init__.py
/usr/lib/python3.6/site-packages/haas_proxy/utils.py
/lib/upgrade/keep.d/haas-proxy
/usr/lib/python3.6/site-packages/haas_proxy/constants.py
/usr/lib/python3.6/site-packages/haas_proxy/twisted/plugins/haas_proxy_plugin.py
/usr/lib/python3.6/site-packages/haas_proxy-1.9-py3.6.egg-info/top_level.txt
/usr/lib/python3.6/site-packages/haas_proxy/log.py
/usr/lib/python3.6/site-packages/haas_proxy/__main__.py
/usr/lib/python3.6/site-packages/haas_proxy/balancer.py
```Turris OS 4.0https://gitlab.nic.cz/turris/os/packages/-/issues/352rescue-mode-omnia: set the bootable flag on created mmc partition2023-08-16T14:38:02+02:00Pierre Bourdonrescue-mode-omnia: set the bootable flag on created mmc partitionI have a dream: using a completely upstream u-boot on my Turris Omnia one day :-)
The standard u-boot distribution looks for the bootable flag on partitions to determine whether it should try to boot from there. Adding the bootable flag...I have a dream: using a completely upstream u-boot on my Turris Omnia one day :-)
The standard u-boot distribution looks for the bootable flag on partitions to determine whether it should try to boot from there. Adding the bootable flag when reflashing a medkit seems like a very low risk and easy change: just add an "a" before the "p" here: https://gitlab.labs.nic.cz/turris/turris-os-packages/blob/ef0c02b7f39c23c1ebffc6f04db1e7edd47cfb2e/cznic/rescue-mode-omnia/files/rescue.sh#L130
I would have sent a PR but can't figure out how to do that on your gitlab. Could someone take care of this? Any objections?https://gitlab.nic.cz/turris/os/packages/-/issues/350various vulnerabilities in hostapd2019-04-11T14:16:07+02:00Ghost Uservarious vulnerabilities in hostapdhttps://github.com/openwrt/openwrt/commit/262229e9248a5235844cdab6bb87fcb77b359b30
https://github.com/openwrt/openwrt/commit/57ab9e3add0f10795b7db5b1f3d1b2eb9b8f92c9
https://github.com/openwrt/openwrt/commit/8f17c019a19f1d0a50e649e...https://github.com/openwrt/openwrt/commit/262229e9248a5235844cdab6bb87fcb77b359b30
https://github.com/openwrt/openwrt/commit/57ab9e3add0f10795b7db5b1f3d1b2eb9b8f92c9
https://github.com/openwrt/openwrt/commit/8f17c019a19f1d0a50e649e81dab9d8f74ad7efbhttps://gitlab.nic.cz/turris/os/packages/-/issues/349resolver-conf: add option for multiple ipv4/ipv6 address2020-03-20T13:31:15+01:00Jan Pavlinecresolver-conf: add option for multiple ipv4/ipv6 addressSupport multiple ipv4/ipv6 address in dns_servers config filesSupport multiple ipv4/ipv6 address in dns_servers config filesTurris OS 3.11.6Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/346unbound version bump 1.9.12019-04-05T09:47:11+02:00Ghost Userunbound version bump 1.9.1Unbound 1.9.1 is available:
https://www.nlnetlabs.nl/downloads/unbound/unbound-1.9.1.tar.gz
sha256 c3c0bf9b86ccba4ca64f93dd4fe7351308ab54293f297a67de5a8914c1dc59c5
pgp https://www.nlnetlabs.nl/downloads/unbound/unbound-1.9.1.tar...Unbound 1.9.1 is available:
https://www.nlnetlabs.nl/downloads/unbound/unbound-1.9.1.tar.gz
sha256 c3c0bf9b86ccba4ca64f93dd4fe7351308ab54293f297a67de5a8914c1dc59c5
pgp https://www.nlnetlabs.nl/downloads/unbound/unbound-1.9.1.tar.gz.asc
> This release contains bug fixes for two issues in the out of order
> processing introduced in 1.9.0, one where the wrong answer was returned
> and a crash bug in file descriptor handling.
>
> There is also a fix for qname minimisation, that could have skipped a
> label-fetch-step when it should not have. This was caused by certain
> recursion situations and the subsequent qname minimisation continuation.
> Qname minimisation in Unbound is designed to sometimes add several
> labels at a time, instead of just adding one label at a time and
> performing lookups until the full qname is reached, because certain
> names are very long, especially in the IPv6 reverse space. Unbound
> performs short steps near the top, in root and TLDs, but then makes
> longer label add steps when the name is very long, near the left side of
> the qname. This is to keep the lookup latency short.
>
> A new type of local-zone is added, inform_redirect, this acts like both
> type inform and type redirect are both used. The answer is logged and
> the content of the answer is like type redirect.
>
> For 0x20 capsforid, a canonical sort is used to compare faulty replies.
> This removes some cases where the fallback could not figure out the
> reply is genuine in several retries.
>
> To make ratelimiting easier, the ratelimit logs print the query name
> that triggered the ratelimit message. Not all query names are
> supposedly the same, but the query name of the query that made the
> ratelimit exceed is printed, and this gives (a single name of) insight
> into the nature of the traffic employed. Also the IP-address of the
> sender of the query that triggered the upstream ratelimit is printed.
> If a recursion exceeds ratelimit, it does not print the IP-address of
> the query ultimately responsible for the recursive lookup.
>
> Unbound has ratelimiting for both the clients (the downstream side) and
> for traffic sent by unbound to the wider internet (the upstream side).
> The ip-ratelimit options limit traffic in packets per client IP. The
> ratelimit options limit traffic towards a domain name. The new logging
> prints extra information with the log messages for both of them, so that
> an inkling of information on some of that traffic is visible straight away.
>
>
> Features
> - Add local-zone type inform_redirect, which logs like type inform,
> and redirects like type redirect.
> - Perform canonical sort for 0x20 capsforid compare of replies,
> this sorts rrsets in the authority and additional section before
> comparison, so that out of order rrsets do not cause failure.
> - Print query name with ip_ratelimit exceeded log lines.
> Spaces instead of tabs in that log message.
> - Print query name and IP address when domain rate limit exceeded.
>
> Bug Fixes
> - Fix #4224: auth_xfr_notify.rpl test broken due to typo
> - Fix locking for libunbound context setup with broken port config.
> - Fix case in which query timeout can result in marking delegation
> as edns_lame_known.
> - Set ub_ctx_set_tls call signature in ltrace config file for
> libunbound in contrib/libunbound.so.conf.
> - improve documentation for tls-service-key and forward-first.
> - #10: fixed pkg-config operations, PKG_PROG_PKG_CONFIG moved out of
> conditional section, fixes systemd builds, from Enrico Scholz.
> - #9: For openssl 1.0.2 use the CRYPTO_THREADID locking callbacks,
> still supports the set_id_callback previous API. And for 1.1.0
> no locking callbacks are needed.
> - #8: Fix OpenSSL without ENGINE support compilation.
> - Wipe TLS session key data from memory on exit.
> - Fix that log-replies prints the correct name for local-alias
> names, for names that have a CNAME in local-data configuration.
> It logs the original query name, not the target of the CNAME.
> - Fix #4206: OpenSSL 1.0.2 hostname verification for FreeBSD 11.2.
> - Fix that qname minimisation does not skip a label when missing
> nameserver targets need to be fetched.
> - Fix #4225: clients seem to erroneously receive no answer with
> DNS-over-TLS and qname-minimisation.
> - Note default for module-config in man page.
> - Fix #13: Remove left-over requirements on OpenSSL >= 1.1.0 for
> cert name matching, from man page.
> - Fix capsforid canonical sort qsort callback.
> - Fix pythonmod include and sockaddr_un ifdefs for compile on
> Windows, and for libunbound.
> - Fix the error for unknown module in module-config is understandable,
> and explains it was not compiled in and where to see the list.
> - In example.conf explain where to put cachedb module in module-config.
> - In man page and example config explain that most modules have to
> be listed at the start of module-config.
> - Fix #4227: pair event del and add for libevent for tcp_req_info.
> - Fix #4229: Unbound man pages lack information, about access-control
> order and local zone tags, and elements in views.
> - Fix #14: contrib/unbound.init: Fix wrong comparison judgment
> before copying.
> - Fix for python module on Windows, fix fopen.
> - Remove memory leak on pythonmod python2 script file init.
> - Remove swig gcc8 python function cast warnings, they are ignored.
> - Print correct module that failed when module-config is wrong.https://gitlab.nic.cz/turris/os/packages/-/issues/344Migration from 3.x to 5.x2023-08-16T14:49:13+02:00Karel KociMigration from 3.x to 5.xThere were some configuration changes in OpenWRT in meantime and we should implement script that migrates those primary settings
* [x] Switch configuration is now done using DSA and switch sections are obsolete. We have to migrate them....There were some configuration changes in OpenWRT in meantime and we should implement script that migrates those primary settings
* [x] Switch configuration is now done using DSA and switch sections are obsolete. We have to migrate them.
* [ ] ~~Create new bridge interface for VLANs without CPU port assigned.~~ (won't be implemented unless wide deployment with such config is discovered)
* [x] Updater configuration and userlists to pkglists
* [x] Wifi paths migration (`option path 'soc/soc:pcie-controller/pci0000:00/0000:00:01.0/0000:01:00.0'` vs `option macaddr '04:f0:21:1c:b7:52'`)
* [x] Detect and select sfp
Known problems:
* [x] update takes a long time because ubus seems to be timing out. I is enough to kill `ubusd` when new version is installed.
* [x] base-files with `/etc/services_wanted` is updated later in update and because of that some services (syslog-ng, dnsmasq, ...) are not activated. turris/turris-build@154d9217)
* [x] some services like lighttpd and mysql are ordered before ubus update do they postinst scripts are hanging (on procd timeout) (solution: turris/updater/updater#137)
* [x] services are still not enabled even with fix from previous line (solution: turris/updater/updater#273)
* [x] after migration Foris reports LAN and guest as to not contain any interface. This is because it expects `ifname` as list not option.
* [x] region country is not set in Foris. This is because of missing `system[0]._country` option but do we care? (this is because it wasn't set in 3.x. If set then it is correctly carried over)
* [x] nextcloud does not work after update. Website is empty. (turris/turris-os-packages#431)
* [x] single interface in network should be `option` not `list` otherwise wan dhcp proto does not work (turris/turris-os-packages@a9ec3c8b)
* [x] knot resolver is unreachable for some reason (problem was in loopback not having interface)
* [ ] `/etc/config/fstab` field `uuid` now really uses `UUID` and not `subuuid` (SUBUUID drives are not mounted. We should replace SUBUUIDs with UUIDs) (~Unconfirmed)
* [x] User installed packages that are no longer available in 4.0+ should be removed/disabled somehow or we should not initialize update. (turris/turris-build!59, turris/turris-build!107)
* [x] updater is unable to found localrepo repositories (turris/turris-os-packages!168)
* [x] localrepo contains invalid packages (we should just flush localrepo and inform user about it)
* [x] localrepo fix to move it away does not work sometimes (turris/turris-os-packages!374)
* [x] LXC is not reportedly migrated (but script itself works as users suggesting them self to run it manually) (turris/turris-os-packages!369)
* [x] Turris 1.x currently can't be migrated because of dependency loop on `updater-ng` package (turris/turris-build!183, turris/turris-build!187)
* [ ] Scary message about removal of `turris-btrfs` is send to users of Turris 1.x because of rename of that package (~Low probably won't fix)
* [x] Migration breaks (with broken libraries) because of turris/turris-os-packages!417 if package depending on `knot-libs` is installed (resolved by turris/turris-build!196)
* [x] Some swconfig configuration might stay in place (we might be ignoring it) and it can cause problems with system without swconfig (commands failing) (resolved by turris/turris-os-packages!383)
* [x] Notify users about finished migration (probably on tos3to4 package removal) (turris/turris-os-packages!380)
* [x] Wireguard `DEVICE_CLAIM_FAILED` error after migration (turris/turris-os-packages#696 turris/turris-os-packages#697)
* [x] Alternatives are not updated after migration as well as on Turris 1.x new version of kernel is not as well (turris/updater/updater#309 turris/turris-os-packages#678)
* [x] After migration router has no LAN as switch config is removed and DSA is not yet deployed (we have to do reboot) (turris/os/build!421)
* [x] Updater settings migration fails for some reason and we are with old version (turris/os/build!421)
* [x] Package lists are not migrated as format changed and fix script is not installed during migration (turris/os/build!421)
* [ ] When approvals are enabled the migration won't trigger right after installation of `tos3to4` but with next run (~Low and probably won't fix)
Test:
* [x] basic network configuration (switch, bridges, ..)
* [x] guest wifi and network configuration
* [x] firewall rules
* [x] DNS configuration
* [ ] openvpn
* [x] pakon
* [x] storage plugin
* [x] lxc
* [ ] haas (honeypot as a service)
* [x] netmetr
* [x] nextcloud
* [x] localrepo
* [ ] dev detect (migration from pakon-dev-detect to dev-detect)
* [ ] mwan
Things to notify users about:
* Updater approvals are disabled for this migration to mitigate possibility that because of link dependencies the approve would be impossible to give. Notification about it is send to notification system once user installs `tos3to4` on Turris OS 3.x.
* Updater is reported as disabled during update.Turris OS 3.x migration