Make the mock slightly more modular in terms of defining and querying
different ubus modules mocks.

Filip Hron authored Jul 27, 2021 and Martin Matějek committed Aug 26, 2022

Use ubus object provided by OpenWrt to get dhcpv6 leases, instead of
parsing `odhcpd` files directly.

Use following ubus call:

`ubus call dhcp ipv6leases`

It should give us nicely structured JSON data, which is easier to work
with.

Needed for testing updater supervisor type annotations.

Changed in updater supervisor made validation of API call `updater->get_settings`
fail on `reboot` attribute in JSON reply.

Which in turn makes updates page in reForis unusable, because error is shown
instead of update summary. That way it is not possible to approve update request.

For relevant changes in updater-supervisor see:
turris/updater/supervisor@aecdf2c4

Closes: #241

Update turrishw dependency to v0.9.0, so we can tell which ethernet port
belongs to which Mox module again on TOS 6.0.

Ability for managing network interfaces was intentionally disabled for
Turris 1.x devices, until support for Turris 1.x will be implemented in
turrishw.

Unfortunately, even though turrishw supports Turris 1.x devices for
quite some time, update of interfaces assignment was still disabled in
foris-controller.

This commit removes that artificial limitation and it is now possible to
assign interfaces to WAN, LAN and Guest network even on Turris 1.x.

Closes: #236

Reuse existing sorting function to avoid code duplication.

Interfaces were returned in order defined in uci config, e.g.:

config device
	option name 'br-lan'
	list ports 'lan3'
	list ports 'lan0'
	list ports 'lan4'
	list ports 'lan2'
	list ports 'lan1'

Would return interfaces in order ['lan3', 'lan0', 'lan4', 'lan2', 'lan1']
instead of expected ['lan0', 'lan1', 'lan2', 'lan3', 'lan4'].

It is possible to get to this state by moving interfaces between
interfaces groups (wan, lan, guest), because newly added interface will
be appended to the list in uci config file.

This commit will sort interfaces again by their names, before finalizing
the json data.

Closes: #238

Remove leftover comment, because that test is already implemented.

Allow these operations on DHCPv4 static leases:
* create
* update
* delete

MAC/IP/Hostname collisions are not allowed and it should not be possible
to set such configuration through foris-controller.

It should be able to handle configuration edge cases with multiple MAC
addresses per IP address for DHCP host.

It can read such config, but it won't allow to store multiple MACs per
IP address for DHCP host.

Refactor schema to make message data for `update_settings` request and
reply mandatory.

Add support for new High-Efficiency Wireless (HEW) modes in 802.11ax.

Allow new htmodes:
* HE20
* HE40
* HE80
* HE160

HE80+80 is intentionally left out and will be addressed later.

Closes: #219

OpenWrt 21.02 wifi-device config options that indicate wireless device
band were slightly changed - `option hwmode` -> `option band`.

Read both new and old syntax, but save only new syntax (`option
band`).

* propagate serial also as a part of properties
* remove address from properties (should be exported via address)
* don't export loopback IPs through zeroconf

From OpenWrt 21.02 now on firewall zone name is limited by 11
characters.

See following commit:
https://git.openwrt.org/?p=project/firewall3.git;a=commit;h=8c2f9fad9ca644af911e0d4113a890c3c84aa738

This leads to situation where firewall rules for guest network failed to
load and traffic was not passing from guest network through wan.

Shorten zone name "guest_turris" -> "tr_guest".

Some wifi interfaces were mistakenly detected as "unassigned" in
reForis, even though there are properly configured and assigned to
lan/guest network.

Fix reading config syntax, so it will detect wifi interfaces correctly.

Search for "option ifname" instead of "option device",
see https://openwrt.org/docs/guide-user/network/wifi/basic#common_options1

Filip Hron authored Sep 06, 2021 and Martin Matějek committed Jan 06, 2022

We need to be able to read both older (OpenWrt <=19.07) and new
(OpenWrt 21.02) configuration syntax.

It is capable of reading both, but write only new syntax.

* some information which are used in advertizements
  can be obtained once and not generated every time
  (e.g. get_netboot_status() calls `mount` cmd)

From Foris/reForis side only following modes are allowed:
* WPA2
* WPA3
* WPA2/3 (default)
* custom

"custom" mode should be used when user wants to keep wifi encryption
settings intact, i.e. configuration was made by hand or in LuCI.

Temporary workaround for deprecated integration with setuptools since
version >=4.0

Foris is no longer present in TOS 5.3.0 and was superseded by reForis
Use reForis translations to determine available localization for reForis

This is mostly quick fix - i.e. just replace Foris with reForis - until
we figure out better long term solution, so foris-controller could
become even more loosely coupled with the current and future web UIs
shipped with Turris OS