Fixed Interfaces tab and staged updates.

Hotfix openvpn for client's side, wrong path of configuration file were
provided.
This fixing commit: 4f7e6ba7

Update to 9.6p1 due to bugfixes and security fixes (among other Terrapin
attack). More info: https://www.openssh.com/txt/release-9.6

Make sure that post install script actually tries to setup the
environment for the tools to work. '\n' is not expanded by default in
echo. And some version of echo does not support -e option. So let's
stick with printf.

Richard Muzik authored 1 year ago and Michal Hrusecky committed 1 year ago

Patch taken from OpenWrt:
- https://github.com/openwrt/packages/commit/808f67d6152fcac09dcda4d66e2bb285878fb3d4
- https://github.com/openwrt/packages/issues/21200

OpenVPN supports more hooks than just 'up' and 'down'. Especially
reacting to 'route-up' and 'route-pre-down' events could be important.
When routing table changes, it can make sense to adapt firewall, run
some tests or change even more routes. This change passes those events
to hotplug, so it is easy to react to them without changing
configuration files provided by VPN provider.

This has been sent to upstream, in the meantime, let's have it in house.

https://github.com/openwrt/packages/pull/21027

We prepared nice GSM configuration but it was still disabled by default,
so let's enable it.

Update to the latest kernel and drop two patches related to Omnia LEDs
as they were merged upstream.

This option of IPv6 Router Advertisements allows devices connected to
a IPv6-only network to discover IPv6 prefix of the NAT64 gateway.
Devices can use this information for instance to setup client translator
(CLAT) from IPv4 to IPv6 in 464XLAT (RFC 6877) scenario or to handle
IPv4 address literal on application level.

To enable PREF64 option, a new uci parameter ra_pref64 has to contain
the NAT64 prefix, including prefix length. Only lengths of 96, 64, 56,
48, 40 and 32 bits are supported. For example, to annonce the Well-Known
Prefix:

config dhcp 'lan'
        …
        option ra_pref64 '64:ff9b::/96'

SWCONFIG and AR8216_PHY are not needed with DSA. Legacy PTYs are also
not needed. Moreover AR8216_PHY causes a 16 second stall at boot time.

Backport qca8k regmap bulk read/write changes and fdb fixes and add a
kernel 5.15 specific workaround for Turris 1.x (which disables switch
internal PHY MDIO access over management ethernet, since it causes
conflicts with WAN PHY, resulting in unusable WAN).

This should fix the bug
  Micrel KSZ9031 Gigabit PHY mdio@ffe24520:07: phy_poll_reset failed: -110
on Turris 1.x with kernel 5.15.

This ports commit
  f4d949b40485 ("generic: 5.15: backport qca8k fixup for mgmt and mdio read/write")
from upstream OpenWRT. The commit backports 5 qca8k patches to
  target/linux/generic/backport-5.15

The patches are currently backported into
  target/linux/mpc85xx/patches-5.15
by our patch
  mpc85xx: add patches from OpenWrt to improve switch

So this basically renames and moves the patches into another directory.

Take the 8 backported Turris Omnia LED patches from
target/mvebu/patches-5.15 and move them to target/generic/backport-5.15
as they are in upstream OpenWRT.

Rename the patch to conform to the name generated by
  git format-patch

For details see the included patch serie or the github repo:
https://github.com/turris-cz/easycwmp

Last year we prepared U-Boot so that when the turris-omnia-mcu driver is
finally in kernel, U-Boot will, before loading kernel, fixup Omnia's
device-tree by injecting reset-gpios to PCIe nodes (for board revisions
32+).

Now that the device-tree contains the node with "cznic,turris-omnia-mcu"
compatible, U-Boot does exactly that. But the problem is that the
pci-mvebu driver with reset-gpios available fails to enumerate the
ath10k card WLE900VX.

Rename the compatible of the driver to "cznic,turris-omnia-ctrl" so that
U-Boot does not inject the reset-gpios for now.

On WAN side automatically request prefix delegation. On LAN side use
eui64 as static IPv6 identifier (::1 is an easy target) and assign also
fe80::1 to the interface as it is common IPv6 address for a default
gateway.

Marek Behun authored 1 year ago and Michal Hrusecky committed 1 year ago

Update Turris Omnia LED driver patches from upstream, and add pending
patches to support Turris Omnia MCU.

For details see the patch.

We need lighttpd-https-cert enabled in order to get lighttpd up and
running and we have updated default configuration of mwan3 to work with
automatically configured 4G/5G modems, so we shouldn't hesitate to
enable it as well.