Turris issueshttps://gitlab.nic.cz/groups/turris/-/issues2024-03-26T10:34:16+01:00https://gitlab.nic.cz/turris/user-docs/-/issues/208Rework LTE setup2024-03-26T10:34:16+01:00Filip HronRework LTE setup- Get specific on particular `LTE` hardware
- "we use this and this card"
- drop current OpenWRT setup help
- specific lUCI setup no longer needed
- describe limitation of each HW (geek)
- example: `mmcli` is not able to sim-lock o...- Get specific on particular `LTE` hardware
- "we use this and this card"
- drop current OpenWRT setup help
- specific lUCI setup no longer needed
- describe limitation of each HW (geek)
- example: `mmcli` is not able to sim-lock on `EC20` hardwarehttps://gitlab.nic.cz/turris/user-docs/-/issues/206hw/omnia/ssd-boot: Add guide for new revisions with press-on stand-offs2024-03-12T10:19:10+01:00Marek Novotnyhw/omnia/ssd-boot: Add guide for new revisions with press-on stand-offsA lot of users are confused by having press-on stand-offs in their Omnias. Would be great to mention it in the guide.A lot of users are confused by having press-on stand-offs in their Omnias. Would be great to mention it in the guide.Marek NovotnyMarek Novotnyhttps://gitlab.nic.cz/turris/foris-controller/foris-client/-/issues/9paho-mqqt breaking changes between versions2024-03-07T16:46:20+01:00Filip Hronpaho-mqqt breaking changes between versions_paho-mqtt_ library introduced some breaking changes in it's API, see: https://github.com/eclipse/paho.mqtt.python/blob/v2.0.0/docs/migrations.rst
This fails multiple CI jobs
for example [sample module](https://gitlab.nic.cz/turris/for..._paho-mqtt_ library introduced some breaking changes in it's API, see: https://github.com/eclipse/paho.mqtt.python/blob/v2.0.0/docs/migrations.rst
This fails multiple CI jobs
for example [sample module](https://gitlab.nic.cz/turris/foris-controller/foris-controller/-/jobs/1035150):
```console
self = <foris_controller_testtools.infrastructure.MqttInfrastructure object at 0x7fc36bb2be50>
def start_message_bus(self):
kwargs = {}
if not self.debug_output:
devnull = open(os.devnull, "wb")
kwargs["stderr"] = devnull
kwargs["stdout"] = devnull
mosquitto_path = os.environ.get("MOSQUITTO_PATH", "/usr/sbin/mosquitto")
self.mosquitto_instance = subprocess.Popen(
[mosquitto_path, "-v", "-p", str(MQTT_PORT)], **kwargs
)
# wait for mqtt port to be opened
> client = mqtt.Client()
E TypeError: __init__() missing 1 required positional argument: 'callback_api_version'
```Štěpán HenekŠtěpán Henekhttps://gitlab.nic.cz/turris/os/updater-lists/-/issues/8[TOS 7.0.0][HBK] Updater execution failed: inconsistent: Package luci-app-tra...2024-03-12T13:38:03+01:00Sviatoslav Sydorenko[TOS 7.0.0][HBK] Updater execution failed: inconsistent: Package luci-app-transmission requires package transmission-daemon that is not availableI've started getting this specific error notification in my email 11 hours ago (19 Feb 2024 , 06:00, Prague time) and got a number of repeated messages since:
```console
Updater execution failed:
INFO:Target Turris OS: 7.0.0
line not fou...I've started getting this specific error notification in my email 11 hours ago (19 Feb 2024 , 06:00, Prague time) and got a number of repeated messages since:
```console
Updater execution failed:
INFO:Target Turris OS: 7.0.0
line not found
ERROR:
inconsistent: Package luci-app-transmission requires package transmission-daemon that is not available.
line not found
line not found
line not found
line not found
line not found
line not found
```
The previous updater notification was about a successful update about 6-7 hours before that:
```
Update notifications
====================
Changes performed by updater at 2024-02-18T22:22:20+00:00
• Installed package kmod-ath10k-ct version 5.15.148+2022-05-13-f808496f-1-147bb589b91b90f72db07f3eb029bf76
• Installed package ath10k-firmware-qca988x-ct-full-htt version 2020-11-08-1
• Installed package omnia-mcu-firmware version 3.4-1
• Installed package omnia-mcutool version 0.2-1
• Installed package firmware-updater version 1.1-5
• Removed package ath10k-firmware-qca988x version 20230804-1
• Removed package kmod-ath10k version 5.15.148+5.15.148-1-1-147bb589b91b90f72db07f3eb029bf76
```
The upgrade to Turris OS 7.0.0 was performed a few days ago.
I'm guessing this is similar to #6.Turris OS 7.0https://gitlab.nic.cz/turris/os/build/-/issues/427PPtP VPN seems broken2024-03-04T14:05:24+01:00Michal HruseckyPPtP VPN seems brokenhttps://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/20https://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/20Turris OS 7.0https://gitlab.nic.cz/turris/user-docs/-/issues/204Add CZ11NIC33 to revisions2024-03-04T13:13:26+01:00Lukas JelinekAdd CZ11NIC33 to revisionsAdd information about CZ11NIC33 to revisions in the documentation.Add information about CZ11NIC33 to revisions in the documentation.https://gitlab.nic.cz/turris/foris-controller/foris-controller-lte-module/-/issues/2Fix License to GPL-3.0-or-later2024-02-09T09:27:38+01:00Filip HronFix License to GPL-3.0-or-laterfix license in [pyproject](pyproject.toml#L10)
/cc @rmuzikfix license in [pyproject](pyproject.toml#L10)
/cc @rmuzikFilip HronFilip Hronhttps://gitlab.nic.cz/turris/pyuci/-/issues/12Legacy package manager2024-02-01T09:32:30+01:00Filip HronLegacy package manager- Convert `setup.py` to `pyproject.toml`
- use `hatch`
```console
DEPRECATION: pyuci is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pi...- Convert `setup.py` to `pyproject.toml`
- use `hatch`
```console
DEPRECATION: pyuci is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
Running setup.py install for pyuci ... done
```https://gitlab.nic.cz/turris/pakon/-/issues/32In Pakon log is missing devices from guest wifi2024-03-12T14:09:57+01:00uzivatel457In Pakon log is missing devices from guest wifiI don't trust all home appliances (heat pump, thermometer, ...), so I have most of them on the wifi network for guests. Now I wanted to find out where they connect to, but Pakon doesn't monitor devices on the guest wifi network. Can this...I don't trust all home appliances (heat pump, thermometer, ...), so I have most of them on the wifi network for guests. Now I wanted to find out where they connect to, but Pakon doesn't monitor devices on the guest wifi network. Can this setting be changed?https://gitlab.nic.cz/turris/turris-netboot/-/issues/6Netboot doesn't work with new uboot >=2021 version2024-03-12T13:33:39+01:00Tomas ZakNetboot doesn't work with new uboot >=2021 versionDuring testing HBL/HBK branch I found out, that Turris MOX doesn't work with newer version of U-BOOT. Let me describe, what I found.
If I use the newest stable version of u-boot (2022) for MOX, initramfs is not loaded so all boot proces...During testing HBL/HBK branch I found out, that Turris MOX doesn't work with newer version of U-BOOT. Let me describe, what I found.
If I use the newest stable version of u-boot (2022) for MOX, initramfs is not loaded so all boot process ended in Kernel panic. There is mox.its file which defines addresses and parameters of kernel, initramfs and device tree. When I use the latest u-boot (2022) the part which defines initramfs is ignored.
I tried to change u-boot enviroment and set same parameters as older working u-boot version has (for example 2018, 2021), but without success.
If I use u-boot ver. 2021 (workaround 4), netboot is working, but with problems at the begging. There are 2 problems what I got everytime, when I paired Omnia/Turris1x with MOX for the first time.
1.) When paring Omnia/Turris1X for the first time with MOX, it stucks on Starting kernel... and after some time MOX reboots itself and then boot normally until it reaches the point 2.
2.) After pairing and during loading kernel it stucks for short time on:
```Bash
...
./boot/Image
```
And then again MOX reboots itself.
Last run (third) is working normally and Omnia/Turris1x pairs with MOX and MOX successfully boot to running system. After this point (routers are paired and MOX started into running system for the first time) everything is working as it should.
With older version of u-boot (2018) everything running smooth and without any troubles.
I used u-boot from this url:
https://gitlab.nic.cz/turris/mox-boot-builder/-/releasesMarek BehunMarek Behunhttps://gitlab.nic.cz/turris/reforis/reforis/-/issues/428Fix link to EULA2024-02-21T18:29:07+01:00Filip HronFix link to EULAEULA link is pointing to old location [https://www.turris.cz/omnia-updater-eula](https://www.turris.cz/omnia-updater-eula)
new proper link will be known from resolution of ticket: https://gitlab.nic.cz/turris/ansible/-/issues/321EULA link is pointing to old location [https://www.turris.cz/omnia-updater-eula](https://www.turris.cz/omnia-updater-eula)
new proper link will be known from resolution of ticket: https://gitlab.nic.cz/turris/ansible/-/issues/321https://gitlab.nic.cz/turris/os/build/-/issues/423mwan3 default config is not proper2023-11-29T15:12:10+01:00Filip Hronmwan3 default config is not proper# Example
- install LTE extension in reForis
- set it up
### mwan on
- plug in WAN
- ping a web
- unplug WAN
- ping a web
### mwan off
```console
/etc/init.d/mwan3 stop
```
- plug in WAN
- ping a web
- unplug WAN
- ping a web
LTE ...# Example
- install LTE extension in reForis
- set it up
### mwan on
- plug in WAN
- ping a web
- unplug WAN
- ping a web
### mwan off
```console
/etc/init.d/mwan3 stop
```
- plug in WAN
- ping a web
- unplug WAN
- ping a web
LTE works
## Solution
Modify `mwan3` configuration so it works.Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/foris-controller/foris-controller-sentinel-module/-/issues/17Mention how to install experimental DynFW client2023-10-11T13:43:09+02:00Lukas JelinekMention how to install experimental DynFW clientThe experimental DynFW client is installed as a separate package that cannot be currently installed beside the standard client. Only one of the clients must be enable to be installed. This information should be clearly presented in the i...The experimental DynFW client is installed as a separate package that cannot be currently installed beside the standard client. Only one of the clients must be enable to be installed. This information should be clearly presented in the information at **Package Management → Packages**.
(If the behavior will change the information it must be updated of course.)
_If this issue pertains to another project, please move it._https://gitlab.nic.cz/turris/os/packages/-/issues/931rescue-mode-omnia: reflash from the internet is broken2023-10-23T10:15:16+02:00Aleksandr Gumroianrescue-mode-omnia: reflash from the internet is brokenIf `mode 6` is selected during reflash on my Omnia a.k.a `Flashing from the Cloud :-)` the following occurs:
- The reflash is stuck on step 1 - downloading the latest Omnia medkit, the serial console log:
<details>
<summary>Click to ex...If `mode 6` is selected during reflash on my Omnia a.k.a `Flashing from the Cloud :-)` the following occurs:
- The reflash is stuck on step 1 - downloading the latest Omnia medkit, the serial console log:
<details>
<summary>Click to expand</summary>
```
1s left
0s left
Mode 6 selected!
Flashing from the Cloud :-)
[ 9.101834] mvneta f1034000.ethernet eth2: PHY [f1072004.mdio-mii:01] driver [Marvell 88E1510]
[ 9.110598] mvneta f1034000.ethernet eth2: configuring for phy/sgmii link mode
[ 9.118241] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
udhcpc: started, v1.31.1
Setting IP address 0.0.0.0 on eth2
udhcpc: sending discover
udhcpc: sending discover
[ 12.311611] mvneta f1034000.ethernet eth2: Link is Up - 1Gbps/Full - flow control rx/tx
[ 12.319646] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
udhcpc: sending discover
udhcpc: sending select for 192.168.0.24
udhcpc: lease of 192.168.0.24 obtained, lease time 604800
Setting IP address 192.168.0.24 on eth2
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.0.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.0.1
Got IPv4!
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 532
link/ether d8:58:d7:00:55:13 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 532
link/ether d8:58:d7:00:55:11 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 532
link/ether d8:58:d7:00:55:12 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.24/24 brd 192.168.0.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 2a02:8308:280:5d00:da58:d7ff:fe00:5512/64 scope global dynamic
valid_lft 3456000sec preferred_lft 2592000sec
inet6 fe80::da58:d7ff:fe00:5512/64 scope link
valid_lft forever preferred_lft forever
5: lan0@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether d8:58:d7:00:55:11 brd ff:ff:ff:ff:ff:ff
6: lan1@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether d8:58:d7:00:55:11 brd ff:ff:ff:ff:ff:ff
7: lan2@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether d8:58:d7:00:55:11 brd ff:ff:ff:ff:ff:ff
8: lan3@eth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether d8:58:d7:00:55:11 brd ff:ff:ff:ff:ff:ff
9: lan4@eth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether d8:58:d7:00:55:13 brd ff:ff:ff:ff:ff:ff
default via 192.168.0.1 dev eth2
192.168.0.0/24 dev eth2 scope link src 192.168.0.24
--2023-10-10 12:38:17-- https://repo.turris.cz/hbs/medkit/medkit-omnia-latest.tar.gz
```
</details>
- If you follow the [URL](https://repo.turris.cz/hbs/medkit/medkit-omnia-latest.tar.gz) from the log, you will get - `404 Not Found`
- https://repo.turris.cz/hbs/medkit/medkit-omnia-latest.tar.gz ❌
- https://repo.turris.cz/hbs/medkit/omnia-medkit-latest.tar.gz ✅
- The downloading of the image and the overall process of reflashing is stuck:
<details><summary>Click to expand</summary>
![telegram-cloud-photo-size-4-5848131056711089750-y](/uploads/72d7f6a843d0ece07f41b89b52afcd3f/telegram-cloud-photo-size-4-5848131056711089750-y.jpg)
</details>
There is obviously a problem somewhere in the [rescue script](https://gitlab.nic.cz/turris/os/packages/-/blob/master/hardware/rescue-image/files/helpers.sh#L112), but I could not find it.
Tested on Turris Omnia: Turris OS 6.3.2, HBS & Turris OS 6.4.2, HBS.https://gitlab.nic.cz/turris/os/packages/-/issues/929turris auth breaks lightppd2023-11-11T18:31:47+01:00Filip Hronturris auth breaks lightppd# outline
The "not-valid-json" error is probably caused by occasional breakdowns of turris auth
User refernce: https://forum.turris.cz/t/error-reforis-not-valid-json/19018/14?u=image
Target file: https://gitlab.nic.cz/turris/os/package...# outline
The "not-valid-json" error is probably caused by occasional breakdowns of turris auth
User refernce: https://forum.turris.cz/t/error-reforis-not-valid-json/19018/14?u=image
Target file: https://gitlab.nic.cz/turris/os/packages/-/blob/master/web/turris-auth/files/lighttpd.conf
# steps
- [ ] investigate logs when this occurs and find out why turris auth fails
- [ ] fix the problemMichal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/diagnostics/-/issues/43Translation license, mistakenly GPLv3 _-only_?2023-10-03T12:39:46+02:00Allan NordhøyTranslation license, mistakenly GPLv3 _-only_?https://hosted.weblate.org/projects/turris/turris-diagnostics/#information \
https://hosted.weblate.org/projects/turris/diagnostics-web/#information \
and \
https://hosted.weblate.org/projects/turris/diagnostics-snapshots-web/#informatio...https://hosted.weblate.org/projects/turris/turris-diagnostics/#information \
https://hosted.weblate.org/projects/turris/diagnostics-web/#information \
and \
https://hosted.weblate.org/projects/turris/diagnostics-snapshots-web/#information
got re-licensed to GPLv3-only, when everything else is GPLv3-or-later
https://hosted.weblate.org/projects/turris/#information
can be changed in \
https://hosted.weblate.org/settings/turris/turris-diagnostics \
https://hosted.weblate.org/settings/turris/diagnostics-web \
https://hosted.weblate.org/settings/turris/diagnostics-snapshots-webLukas JelinekLukas Jelinekhttps://gitlab.nic.cz/turris/user-docs/-/issues/195Turris Mox USB (from module A) not working any more (for mass storage) after ...2023-05-18T13:38:03+02:00Lukas JelinekTurris Mox USB (from module A) not working any more (for mass storage) after TOS 6.0 upgrade - add to FAQAdd an item to the FAQ according this: https://forum.turris.cz/t/turris-mox-usb-from-module-a-not-working-any-more-for-mass-storage-after-tos-6-0-upgrade/17918/95Add an item to the FAQ according this: https://forum.turris.cz/t/turris-mox-usb-from-module-a-not-working-any-more-for-mass-storage-after-tos-6-0-upgrade/17918/95https://gitlab.nic.cz/turris/os/build/-/issues/407Retake and finish support for max63xx for Turris 1.x routers2023-03-04T07:51:19+01:00Josef SchlehoferRetake and finish support for max63xx for Turris 1.x routersWould it be possible to retake/ping/finish this patch series https://www.spinics.net/lists/linux-watchdog/msg23299.html which was sent by Pali to have it included in the Linux kernel?
Reference: https://github.com/openwrt/openwrt/pull/1...Would it be possible to retake/ping/finish this patch series https://www.spinics.net/lists/linux-watchdog/msg23299.html which was sent by Pali to have it included in the Linux kernel?
Reference: https://github.com/openwrt/openwrt/pull/10617Marek BehunMarek Behunhttps://gitlab.nic.cz/turris/user-docs/-/issues/193Updated MOX product brochure2023-03-02T09:03:33+01:00Filip HronUpdated MOX product brochurefollows #192
Upload updated MOX Brochure to reflect new Wi-Fi 6 card and deprecated SDIO.follows #192
Upload updated MOX Brochure to reflect new Wi-Fi 6 card and deprecated SDIO.Filip HronFilip Hronhttps://gitlab.nic.cz/turris/mox-boot-builder/-/issues/4License information2023-08-16T10:46:52+02:00DerekLicense informationI'd like to package wtmi_app.bin for Nix. I would like to get the correct license applied to this firmware. Could you add a license information file to the repo, or give me something I could cite?I'd like to package wtmi_app.bin for Nix. I would like to get the correct license applied to this firmware. Could you add a license information file to the repo, or give me something I could cite?Marek BehunMarek Behun