Turris OS packages issueshttps://gitlab.nic.cz/turris/os/packages/-/issues2023-08-16T14:58:23+02:00https://gitlab.nic.cz/turris/os/packages/-/issues/183Update boost libraries2023-08-16T14:58:23+02:00TomasUpdate boost librariesFor newest domoticz (upstream) the recommended version of boost libraries is 1.66:
Its recommended that you use the latest Boost libraries - as of December 2017 that is version 1.66.
http://www.domoticz.com/wiki/Raspberry_Pi_-_Build_Dom...For newest domoticz (upstream) the recommended version of boost libraries is 1.66:
Its recommended that you use the latest Boost libraries - as of December 2017 that is version 1.66.
http://www.domoticz.com/wiki/Raspberry_Pi_-_Build_Domoticz_from_source#Build_.26_Install_Boost_Libraries
Definitely, it cannot be build with current 1.58. The error I got with my current domoticz Makefile hosted at https://github.com/trusnak/domoticz-turris is:
```
[ 1%] Generating stdafx.h.gch/.c++
/home/linker/turris-os/staging_dir/toolchain-powerpc_8540_gcc-4.8-linaro_uClibc-0.9.33.2/lib/gcc/powerpc-openwrt-linux-uclibcspe/4.8.3/../../../../powerpc-openwrt-linux-uclibcspe/lib/crt1.o: In function `_start':
/home/linker/turris-os/build_dir/toolchain-powerpc_8540_gcc-4.8-linaro_uClibc-0.9.33.2/uClibc-0.9.33.2/libc/sysdeps/linux/powerpc/crt1.S:93: undefined reference to `main'
/home/linker/turris-os/build_dir/toolchain-powerpc_8540_gcc-4.8-linaro_uClibc-0.9.33.2/uClibc-0.9.33.2/libc/sysdeps/linux/powerpc/crt1.S:94: undefined reference to `main'
collect2: error: ld returned 1 exit status
CMakeFiles/domoticz_gch.dir/build.make:60: recipe for target 'stdafx.h.gch/.c++' failed
make[5]: *** [stdafx.h.gch/.c++] Error 1
```
I'm not aware if any other packages depends on boost, but it was added as domoticz dependency in TurrisOS 2.5, so I think not.
Could you please update boost libraries?Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/185https-dns-proxy: update to upstream version2023-08-16T14:58:22+02:00Josef Schlehoferhttps-dns-proxy: update to upstream versionThe version in our repository is outdated and should be updated to the latest version, which is available since 23.4.2018.
Here is a link to upstream package: https://github.com/openwrt/packages/tree/master/net/https-dns-proxyThe version in our repository is outdated and should be updated to the latest version, which is available since 23.4.2018.
Here is a link to upstream package: https://github.com/openwrt/packages/tree/master/net/https-dns-proxyJan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/202Request to add package: ipmitool2023-08-16T14:58:21+02:00Josef SchlehoferRequest to add package: ipmitool**ipmitool is utility for controlling IPMI-enabled devices**
OpenWRT link: https://github.com/openwrt/packages/tree/master/admin/ipmitool
Github repository: https://github.com/ipmitool/ipmitool
Requested on our [forum](https://forum....**ipmitool is utility for controlling IPMI-enabled devices**
OpenWRT link: https://github.com/openwrt/packages/tree/master/admin/ipmitool
Github repository: https://github.com/ipmitool/ipmitool
Requested on our [forum](https://forum.turris.cz/t/question-how-to-have-ipmitool-on-turris-omnia/5687/6?u=pepe).https://gitlab.nic.cz/turris/os/packages/-/issues/218shadowsocks-libev: update to version 3.2.02023-08-16T14:58:20+02:00Josef Schlehofershadowsocks-libev: update to version 3.2.0Package name: **shadowsocks-libev**
Short description of the package: **lightweight implementation of shadowsocks protocol**
OpenWRT repository:
https://github.com/openwrt/packages/tree/master/net/shadowsocks-libev
Upstream repos...Package name: **shadowsocks-libev**
Short description of the package: **lightweight implementation of shadowsocks protocol**
OpenWRT repository:
https://github.com/openwrt/packages/tree/master/net/shadowsocks-libev
Upstream repository:
https://github.com/shadowsocks/shadowsocks-libev/
_Version information_
We have version: 2.2.3.
Upstream and OpenWRT have version: 3.2.0
Dependencies:
* [x] libcares
We have version: 1.11.0
Upstream and OpenWRT have version: 1.14.0 ( https://github.com/openwrt/packages/blob/master/libs/c-ares/Makefile )
* [x] libev
We have version: 4.22
Upstream and OpenWRT have version: 4.22 ( https://github.com/openwrt/packages/blob/master/libs/libev/Makefile )
* [x] libpcre (commit in dev branch: https://gitlab.labs.nic.cz/turris/turris-os-packages/commit/57fb7f173d90ea6b299599a00b705b06b923915f)
We have version: 8.41
Upstream and OpenWRT have version: 8.42 ( https://github.com/openwrt/packages/blob/master/libs/pcre/Makefile )
* [ ] libpthread
We have version: 1.1.15
Upstream and OpenWRT have version:
* [x] libsodium
We have version: 1.0.10
Upstream and OpenWRT have version: 1.0.16 ( https://github.com/openwrt/packages/tree/master/libs/libsodium )
* [x] libmbedtls (commit in dev branch: https://gitlab.labs.nic.cz/turris/openwrt/commit/70303e1c8cb9b4734bb02479fb952078ffc14ff2)https://gitlab.nic.cz/turris/os/packages/-/issues/228Enable SSL support in zabbix packages2023-08-16T14:58:00+02:00Petr GregorEnable SSL support in zabbix packagesHi,
since turris is a security conscious OS I would like to request SSL support in zabbix packages. Currently SSL support is not compiled in so it cannot be enabled. It seems openwrt package got the support recently: https://github.com/o...Hi,
since turris is a security conscious OS I would like to request SSL support in zabbix packages. Currently SSL support is not compiled in so it cannot be enabled. It seems openwrt package got the support recently: https://github.com/openwrt/packages/commit/dda7a55418acf14d0c3d5fd82ab1b0cc2946c05a
Thank youJan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/231ddns-script: reboot bug2023-08-16T14:57:58+02:00Jan Pavlinecddns-script: reboot bugddns-script is causing rebootddns-script is causing reboothttps://gitlab.nic.cz/turris/os/packages/-/issues/250Add server support for DNS-over-TLS2023-08-16T14:57:57+02:00Jan PavlinecAdd server support for DNS-over-TLSBy default, Android Pie devices automatically upgrade to DNS over TLS if a network's DNS server supports it.
We could support this feature in routers. The only issues is, that user should securte valid certificate, so Android device will...By default, Android Pie devices automatically upgrade to DNS over TLS if a network's DNS server supports it.
We could support this feature in routers. The only issues is, that user should securte valid certificate, so Android device will accept it.
https://dnsprivacy.org/wiki/display/DP/Using+Unbound+as+a+DNS+Privacy+server
and
https://dnsprivacy.org/wiki/display/DP/Using+Knot-resolver+as+a+DNS+Privacy+serverJan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/253[Github Issue] Package Request: Node-Red2023-08-16T14:57:55+02:00Jan Pavlinec[Github Issue] Package Request: Node-Red[Node-Red](https://nodered.org/) is a powerful [node.js](https://nodejs.org/en/about/) graphical flow-based programming and run-time environment for IOT applications [originally devloped by IBM and later released under Apache license](ht...[Node-Red](https://nodered.org/) is a powerful [node.js](https://nodejs.org/en/about/) graphical flow-based programming and run-time environment for IOT applications [originally devloped by IBM and later released under Apache license](https://en.wikipedia.org/wiki/Node-RED). Without programming skills you can click together e.g. the complete control flows for all IOT devices in your home. Currently it provides over 2,400 nodes to build flow diagrams (I/O-, database-, services-nodes like MQTT, Alexa, Google-IoT, IBM-Watson, ...). It also provides a function node for custom Javascript code.
[Introduction video](https://www.youtube.com/watch?time_continue=1&v=vYreeoCoQPI)
[Example Makefile](https://github.com/nxhack/openwrt-node-packages/tree/master/node-node-red)Turris OS 5.0https://gitlab.nic.cz/turris/os/packages/-/issues/278mwan3: after update to 3.11 not working2023-08-16T14:57:53+02:00Jan Pavlinecmwan3: after update to 3.11 not workingrelated forum topic https://forum.turris.cz/t/mwan3-after-update-not-working/8862related forum topic https://forum.turris.cz/t/mwan3-after-update-not-working/8862https://gitlab.nic.cz/turris/os/packages/-/issues/310lua vs. luajit libraries2023-08-16T14:57:52+02:00Vladimír Čunátvladimir.cunat@nic.czlua vs. luajit librariesAs it is now, no lua libraries are usable from kresd, except those that come with luajit or kresd itself.
Well it doesn't really need any ATM, because we don't do root trust anchor bootstrapping, http module or other less usual stuff. ...As it is now, no lua libraries are usable from kresd, except those that come with luajit or kresd itself.
Well it doesn't really need any ATM, because we don't do root trust anchor bootstrapping, http module or other less usual stuff. I guess cqueues would be considered useful by some, as we'll add auto-reloading feature for RPZ that depends on that.
I actually don't know how the `*.so` parts of lua libs are shareable between vanilla lua and luajit. That would need investigation. I've seen distros packaging for each implementation separately (5.1, 5.2, luajit), but I don't know if that's truly necessary.
Cross-link that brought me to this: https://forum.turris.cz/t/luajit-require-not-work-in-omnii/9289https://gitlab.nic.cz/turris/os/packages/-/issues/336wrong iw command output2023-08-16T14:57:48+02:00Štěpán Henekwrong iw command outputMight be caused by some kernel bug. `iw` uses netlink to obtain information from the kernel...
Problem occurs on Omnia and TurrisOS 4.0.
```bash
root@turris:~# iw phy0 info
Wiphy phy0
max # scan SSIDs: 16
max scan IEs length: 195 byte...Might be caused by some kernel bug. `iw` uses netlink to obtain information from the kernel...
Problem occurs on Omnia and TurrisOS 4.0.
```bash
root@turris:~# iw phy0 info
Wiphy phy0
max # scan SSIDs: 16
max scan IEs length: 195 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CMAC (00-0f-ac:6)
* CMAC-256 (00-0f-ac:13)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
Available Antennas: TX 0x7 RX 0x7
Configured Antennas: TX 0x7 RX 0x7
Supported interface modes:
* IBSS
* managed
* AP
* monitor
* mesh point
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x19ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-23
VHT Capabilities (0x338001b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (30.0 dBm)
* 2417 MHz [2] (30.0 dBm)
* 2422 MHz [3] (30.0 dBm)
* 2427 MHz [4] (30.0 dBm)
* 2432 MHz [5] (30.0 dBm)
* 2437 MHz [6] (30.0 dBm)
* 2442 MHz [7] (30.0 dBm)
* 2447 MHz [8] (30.0 dBm)
* 2452 MHz [9] (30.0 dBm)
* 2457 MHz [10] (30.0 dBm)
* 2462 MHz [11] (30.0 dBm)
* 2467 MHz [12] (disabled)
* 2472 MHz [13] (disabled)
* 2484 MHz [14] (disabled)
Band 2:
Capabilities: 0x19ef
RX LDPC
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-23
VHT Capabilities (0x338001b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: MCS 0-9
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5180 MHz [36] (23.0 dBm)
* 5200 MHz [40] (23.0 dBm)
* 5220 MHz [44] (23.0 dBm)
* 5240 MHz [48] (23.0 dBm)
* 5260 MHz [52] (23.0 dBm) (radar detection)
* 5280 MHz [56] (23.0 dBm) (radar detection)
* 5300 MHz [60] (23.0 dBm) (radar detection)
* 5320 MHz [64] (23.0 dBm) (radar detection)
* 5500 MHz [100] (23.0 dBm) (radar detection)
* 5520 MHz [104] (23.0 dBm) (radar detection)
* 5540 MHz [108] (23.0 dBm) (radar detection)
* 5560 MHz [112] (23.0 dBm) (radar detection)
* 5580 MHz [116] (23.0 dBm) (radar detection)
* 5600 MHz [120] (23.0 dBm) (radar detection)
* 5620 MHz [124] (23.0 dBm) (radar detection)
* 5640 MHz [128] (23.0 dBm) (radar detection)
* 5660 MHz [132] (23.0 dBm) (radar detection)
* 5680 MHz [136] (23.0 dBm) (radar detection)
* 5700 MHz [140] (23.0 dBm) (radar detection)
* 5720 MHz [144] (23.0 dBm) (radar detection)
* 5745 MHz [149] (30.0 dBm)
* 5765 MHz [153] (30.0 dBm)
* 5785 MHz [157] (30.0 dBm)
* 5805 MHz [161] (30.0 dBm)
* 5825 MHz [165] (30.0 dBm)
* 5845 MHz [169] (disabled)
* 5865 MHz [173] (disabled)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* testmode
* connect
* disconnect
* channel_switch
* set_qos_map
* set_multicast_to_unicast
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
* monitor
valid interface combinations:
* #{ managed, P2P-client } <= 16, #{ P2P-GO } <= 3, #{ AP } <= 7, #{ IBSS } <= 1,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports scan flush.
Device supports AP scan.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
Device supports static SMPS
Device supports configuring vdev MAC-addr on create.
Supported extended features:
* [ VHT_IBSS ]: VHT-IBSS
* [ RRM ]: RRM
* [ SET_SCAN_DWELL ]: scan dwell setting
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
```
Shows that `Band 1` has `VHT Capabilities` although it is 11g mode.
Output for a 11g only cards seems to be fine (without `VHT Capabilities`). It also works properly on TurrisOS 3.X.https://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/389UTC time zone absent from Foris2023-08-16T14:57:31+02:00Ghost UserUTC time zone absent from Foris{"kernel":"4.14.113","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"armada-385-turris-omnia","release":{"distribution":"TurrisOS","version":"4.0-beta1","revision":"0663455801","target":"mvebu/...{"kernel":"4.14.113","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"armada-385-turris-omnia","release":{"distribution":"TurrisOS","version":"4.0-beta1","revision":"0663455801","target":"mvebu/cortexa9","description":"TurrisOS 4.0-beta1 0663455801"}}
___
Whilst available through LuCI the UTC time zone is absent from the Foris
UTC is a fixed time zone that never observes Daylight Saving Time and is not queal to what Foris offers
```
option timezone 'GMT0BST,M3.5.0/1,M10.5.0'
option _country 'GB'
option zonename 'Europe/London'
```Štěpán HenekŠtěpán Henekhttps://gitlab.nic.cz/turris/os/packages/-/issues/425sentinel-minipot does not allow connection on IPv62023-08-16T14:57:29+02:00Vojtech Myslivecsentinel-minipot does not allow connection on IPv6`sentinel-minipot` init script handles iptables rules to forward `telnet` traffic to minipot service, but it use `iptables` for IPv4 only and so minipot is not accessible IPv6.`sentinel-minipot` init script handles iptables rules to forward `telnet` traffic to minipot service, but it use `iptables` for IPv4 only and so minipot is not accessible IPv6.https://gitlab.nic.cz/turris/os/packages/-/issues/438turris-webapps: problems with accessing router over IPv62023-08-16T14:57:28+02:00Karel Kociturris-webapps: problems with accessing router over IPv6There seems to be problem when router is being accessed trough ipv6 address instead of ipv4. Browser reports malformed URI.
This was reported in issue https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/436There seems to be problem when router is being accessed trough ipv6 address instead of ipv4. Browser reports malformed URI.
This was reported in issue https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/436Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/packages/-/issues/439Modify or add google forwarder2023-08-16T14:57:27+02:00Štěpán HenekModify or add google forwarderAs @ljelinek suggested it is possible to use dns over tls with google resolver. So please consider adding a `Google (TLS)` forwarder
Google should be accessed via DoT too. It is probably supported: https://en.wikipedia.org/wiki/Google_P...As @ljelinek suggested it is possible to use dns over tls with google resolver. So please consider adding a `Google (TLS)` forwarder
Google should be accessed via DoT too. It is probably supported: https://en.wikipedia.org/wiki/Google_Public_DNSTurris OS 5.1Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/449New package: lshw2023-08-16T14:57:26+02:00Karel KociNew package: lshwFor diagnostics purposes it would be good to have command `lshw` on router. It is nice program that in readable form dumps everything it can about hardware it is running on. This would be pretty nice.
https://www.ezix.org/project/wiki/H...For diagnostics purposes it would be good to have command `lshw` on router. It is nice program that in readable form dumps everything it can about hardware it is running on. This would be pretty nice.
https://www.ezix.org/project/wiki/HardwareLiSter
We should after that push this package to upstream.https://gitlab.nic.cz/turris/os/packages/-/issues/470[resolver-conf - feature suggestion] add support for unbound ipset2023-08-16T14:57:25+02:00Ghost User[resolver-conf - feature suggestion] add support for unbound ipset`ipset` support is added to `unbound` v1.9.3 https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/469 and thus it would be handy if the resolver script would also support it by parsing `ipset` entries and addting to `ipt` as per h...`ipset` support is added to `unbound` v1.9.3 https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/469 and thus it would be handy if the resolver script would also support it by parsing `ipset` entries and addting to `ipt` as per https://github.com/NLnetLabs/unbound/blob/release-1.9.3/doc/README.ipset.mdJan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/476[haveged] postinst CPU spike2023-08-16T14:57:23+02:00Ghost User[haveged] postinst CPU spike> {"kernel":"4.14.141","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"TurrisOS","version":"5.0-dev","revision":"0c35633","target":"mvebu/cortexa9...> {"kernel":"4.14.141","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"TurrisOS","version":"5.0-dev","revision":"0c35633","target":"mvebu/cortexa9","description":"TurrisOS 5.0-dev 0c35633"}}
___
> INFO:Running postinst of libhavege
> INFO:Running postinst of haveged
> haveged: listening socket at 0
observed on two installations, it does not get relieve after some time
![Annotation_2019-09-03_075806](/uploads/f2006f7b151753607b9c1f233e46030c/Annotation_2019-09-03_075806.png)
A reboot of the node remedies the matter.https://gitlab.nic.cz/turris/os/packages/-/issues/489resolver-conf: DNSSEC rootkey update2023-08-16T14:57:04+02:00Jan Pavlinecresolver-conf: DNSSEC rootkey updateThis is a meta issue.
It's possible that DNSSEC root key will be rotated more frequently (once per year). Right now we ships omnia/mox with enabled DNSSEC.
In case that someone will buy the version with an older firmware, auto-update f...This is a meta issue.
It's possible that DNSSEC root key will be rotated more frequently (once per year). Right now we ships omnia/mox with enabled DNSSEC.
In case that someone will buy the version with an older firmware, auto-update function will not be possible because DNSSEC validation will fail. We should discuss a possible solution here.
cc @jschlehofer @kkoci @mhrusecky