Turris Build issueshttps://gitlab.nic.cz/turris/os/build/-/issues2023-11-09T19:30:16+01:00https://gitlab.nic.cz/turris/os/build/-/issues/420Add macOS support in compile_pkgs script2023-11-09T19:30:16+01:00Aleksandr GumroianAdd macOS support in compile_pkgs scriptI've received this as feedback. There are two issues that prevent people on Macs build packages:
- shebang, most probably we should use `#!/usr/bin/env bash`
- https://stackoverflow.com/questions/4247068/sed-command-with-i-option-failin...I've received this as feedback. There are two issues that prevent people on Macs build packages:
- shebang, most probably we should use `#!/usr/bin/env bash`
- https://stackoverflow.com/questions/4247068/sed-command-with-i-option-failing-on-mac-but-works-on-linux
It would be nice to fix it. :slight_smile:https://gitlab.nic.cz/turris/os/build/-/issues/409Provide SDK2024-03-12T13:56:35+01:00Patrick GrimmProvide SDKWhy don't provide the SDK? It is easier to develop and distribute third party opkg feeds.
```
diff --git a/configs/common/basic_settings b/configs/common/basic_settings
index 08c99f23..3be3d260 100644
--- a/configs/common/basic_settings...Why don't provide the SDK? It is easier to develop and distribute third party opkg feeds.
```
diff --git a/configs/common/basic_settings b/configs/common/basic_settings
index 08c99f23..3be3d260 100644
--- a/configs/common/basic_settings
+++ b/configs/common/basic_settings
@@ -7,6 +7,9 @@ CONFIG_BUILD_NLS=y
CONFIG_ALL_KMODS=y
CONFIG_ALL=y
+# Build openwrt SDK pre-compiled toolchain designed to cross compile packages
+CONFIG_SDK=y
+
# Package output options
CONFIG_SIGNED_PACKAGES=y
CONFIG_IPK_FILES_CHECKSUMS=y
```https://gitlab.nic.cz/turris/os/build/-/issues/348MOX: Enable earlyprintk for easier UART debugging2022-07-27T13:51:46+02:00Josef SchlehoferMOX: Enable earlyprintk for easier UART debuggingSimilar as for Turris Omnia (turris/os/build#347), we need similar stuff for Turris MOX:
```
CONFIG_CMDLINE="earlycon=ar3700_uart,0xd0012000 console=ttyMV0,115200"
CONFIG_CMDLINE_FROM_BOOTLOADER=y
CONFIG_SERIAL_EARLYCON=y
CONFIG_SERIAL_...Similar as for Turris Omnia (turris/os/build#347), we need similar stuff for Turris MOX:
```
CONFIG_CMDLINE="earlycon=ar3700_uart,0xd0012000 console=ttyMV0,115200"
CONFIG_CMDLINE_FROM_BOOTLOADER=y
CONFIG_SERIAL_EARLYCON=y
CONFIG_SERIAL_MVEBU_UART=y
CONFIG_SERIAL_MVEBU_CONSOLE=y
```Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/333UBNT SFP GPON support2023-08-16T10:55:31+02:00Karel KociUBNT SFP GPON supportBackport UBNT SFP GPON patches to ensure functionality.Backport UBNT SFP GPON patches to ensure functionality.Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/312PRPL Mesh packages feed2021-12-14T12:19:29+01:00Karel KociPRPL Mesh packages feedThink about inclusion of prplMesh packages (https://gitlab.com/prpl-foundation/prplos/feed-prpl).
* [ ] add feed
* [ ] test itThink about inclusion of prplMesh packages (https://gitlab.com/prpl-foundation/prplos/feed-prpl).
* [ ] add feed
* [ ] test ithttps://gitlab.nic.cz/turris/os/build/-/issues/293[Feature request]: Add watchcat plugin configuration directly to the reForris...2023-08-16T10:57:04+02:00Marek Ľach[Feature request]: Add watchcat plugin configuration directly to the reForris user interface itself, active by defaultBecause the WiFi sometimes disconnects in mid-day for me, and TurrisOS, by default, is not able to reboot/restart such a once lost connection immediately on its own, without the need for a lenghty manual intervention.
The `OpenWRT` pack...Because the WiFi sometimes disconnects in mid-day for me, and TurrisOS, by default, is not able to reboot/restart such a once lost connection immediately on its own, without the need for a lenghty manual intervention.
The `OpenWRT` package `watchcat` seems to be the sought after remedy in these situations, with which I was eventually able to configure an automated re-connect if ping's lost, so **TurrisOS** could _have watchcat included_, and active by default in its own *reForis* interface, to make it even more convenient, useful and user-friendly.
It’d be worth it implementing this plugin into the latest iteration of TurrisOS proper out-of-the-box in the future... for laymen like myself :-)https://gitlab.nic.cz/turris/os/build/-/issues/249Consider switching default WAN policy from REJECT to DROP2021-03-01T19:14:45+01:00Karel KociConsider switching default WAN policy from REJECT to DROPIt might be better to drop all connections on WAN side rather then rejecting them.
The default is right now set unconditionally from OpenWrt. This needs either dirty patch or some upstream effort to export this settings to KConfig.It might be better to drop all connections on WAN side rather then rejecting them.
The default is right now set unconditionally from OpenWrt. This needs either dirty patch or some upstream effort to export this settings to KConfig.https://gitlab.nic.cz/turris/os/build/-/issues/247Replace Nikola with FWLogs2021-09-21T12:25:14+02:00Karel KociReplace Nikola with FWLogsFWLogs is much better implementation. We should use that.
On Sentinel meeting we checked that FWLogs is fully compatible with Nikola on Sentinel server side so there should be no issue in doing the replace.FWLogs is much better implementation. We should use that.
On Sentinel meeting we checked that FWLogs is fully compatible with Nikola on Sentinel server side so there should be no issue in doing the replace.Turris OS 5.3.0https://gitlab.nic.cz/turris/os/build/-/issues/245suggestion: replace dnsmasq with odhcpd2022-03-24T07:53:35+01:00Rosen Penevsuggestion: replace dnsmasq with odhcpdIn TurrisOS, dnsmasq is used as a DHCP server and unbound as a DNS one.
odhcpd is used as a DHCPv6 server. It has the ability to run as a DHCPv4 server as well.
The whole point of using dnsmasq in OpenWrt is that it combines DHCP and D...In TurrisOS, dnsmasq is used as a DHCP server and unbound as a DNS one.
odhcpd is used as a DHCPv6 server. It has the ability to run as a DHCPv4 server as well.
The whole point of using dnsmasq in OpenWrt is that it combines DHCP and DNS. But since this is not the case in TurrisOS, it can be removed.https://gitlab.nic.cz/turris/os/build/-/issues/235Create special TurrisOS medkit for LXC2021-01-19T14:10:27+01:00Jan PavlinecCreate special TurrisOS medkit for LXCRunning TurrisOS in LXC is challenging because some utils try to access low-level function which is not accessible in LXC (cert-backup, atsha)
One possible solution is to create custom medkits for LXCRunning TurrisOS in LXC is challenging because some utils try to access low-level function which is not accessible in LXC (cert-backup, atsha)
One possible solution is to create custom medkits for LXChttps://gitlab.nic.cz/turris/os/build/-/issues/201Move lists to separate feed2021-09-21T12:25:59+02:00Karel KociMove lists to separate feedWe should move lists to separate feed. We build them separately but we do not have them separate in feeds description. Moving them to separate repository is not essential for separate hash but makes it cleaner as they are updated only wh...We should move lists to separate feed. We build them separately but we do not have them separate in feeds description. Moving them to separate repository is not essential for separate hash but makes it cleaner as they are updated only when it is required. It also opens doors for implementation of some sort of limit "use these lists only with build of specific commit and newer". This could fix common issue when packages take time to build but at the meantime lists are broken.Turris OS 5.3.0https://gitlab.nic.cz/turris/os/build/-/issues/184Lists: essential packages should not be pulled in only exclusively by Foris p...2021-01-04T09:05:41+01:00Karel KociLists: essential packages should not be pulled in only exclusively by Foris packagesThere are components such as diagnostics that are pulled in only as Foris dependency. We should locate such packages and include them in default installation.
The ideal solution would be to make all Foris plugins optional and pulled in ...There are components such as diagnostics that are pulled in only as Foris dependency. We should locate such packages and include them in default installation.
The ideal solution would be to make all Foris plugins optional and pulled in only if specific package they need is requested.
The reason is that some users are removing Foris (although not supported it makes sense to not break system because of it) and because of that also other essential packages.Turris OS 5.2.0https://gitlab.nic.cz/turris/os/build/-/issues/178Enable GCC_DEFAULT_SSP2024-03-01T14:34:28+01:00Jan PavlinecEnable GCC_DEFAULT_SSPWe should enabled GCC_DEFAULT_SSP by default on HBL
https://gitlab.nic.cz/turris/turris-build/-/commit/25d12eb1a8ceb5e1fcbfcc1473b9610f7e9d5314
This issue is a sort of reminder.We should enabled GCC_DEFAULT_SSP by default on HBL
https://gitlab.nic.cz/turris/turris-build/-/commit/25d12eb1a8ceb5e1fcbfcc1473b9610f7e9d5314
This issue is a sort of reminder.Turris OS 7.1.0https://gitlab.nic.cz/turris/os/build/-/issues/167Add options to hardening with option for common passwords inclusion2021-01-25T09:58:41+01:00Karel KociAdd options to hardening with option for common passwords inclusionWe have package with common passwords that should not be used for authentication. This is nice thing to include as option in hardening package list.We have package with common passwords that should not be used for authentication. This is nice thing to include as option in hardening package list.Turris OS 5.2.0https://gitlab.nic.cz/turris/os/build/-/issues/166collectd: Consider enabling signing/encryption support2020-08-01T18:57:35+02:00Elvenlord Elrondcollectd: Consider enabling signing/encryption supportcollectd's network plugin has the option to sign or encrypt the contents for data transfer to other collectd instances.
OpenWrt added this feature [here](https://github.com/openwrt/packages/commit/4ba4d8232d4431170faffadfa80fbb0ba76d20f...collectd's network plugin has the option to sign or encrypt the contents for data transfer to other collectd instances.
OpenWrt added this feature [here](https://github.com/openwrt/packages/commit/4ba4d8232d4431170faffadfa80fbb0ba76d20f1).
It is probably only a matter of adding `PACKAGE_COLLECTD_ENCRYPTED_NETWORK=y` to `configs/common/packages`?
Yes, this will introduce a new dependency on libgcrypt. On a small embedded platform this might be of concern. But for omnia and mox, it shouldn't be a big problem. And only people installing the network plugin will actually get that extra depeendencies. Which sounds acceptable to me.Turris OS 5.1https://gitlab.nic.cz/turris/os/build/-/issues/162patch luci (-mod-network) to show a warning about DNS settings2021-11-03T18:36:35+01:00Vladimír Čunátvladimir.cunat@nic.czpatch luci (-mod-network) to show a warning about DNS settingsThis is the short-term plan after discussion with Pepe. Some people can be understandably confused that DNS settings in luci's "DHCP and DNS" don't have any effect, so we could at least show a warning on that page... until some better s...This is the short-term plan after discussion with Pepe. Some people can be understandably confused that DNS settings in luci's "DHCP and DNS" don't have any effect, so we could at least show a warning on that page... until some better solution is available, e.g. https://github.com/openwrt/luci/issues/4125https://gitlab.nic.cz/turris/os/build/-/issues/161[meta] Better IPv6 detection2024-03-11T09:33:49+01:00Jan Pavlinec[meta] Better IPv6 detectionThis issue should be used for brainstorming ideas about IPv6 detection.
The main idea is, that there should be one mechanism that can tell if the user has IPv6 and this information should be shared with init scripts (via uci for example...This issue should be used for brainstorming ideas about IPv6 detection.
The main idea is, that there should be one mechanism that can tell if the user has IPv6 and this information should be shared with init scripts (via uci for example) instead of doing separate detection for every service.
Examples of with detection:
* knot-resolver ping test for disabling IPv6: [turris-os-packages:net/knot-resolver/files/kresd.init#L270](https://gitlab.nic.cz/turris/turris-os-packages/-/blob/v5.1.0/net/knot-resolver/files/kresd.init#L270)
* hotplug - https://gitlab.nic.cz/turris/turris-os-packages/-/merge_requests/381/diffs#diff-content-160a8a7b73e11a0e3502870d06ac486732a69d98
cc @jschlehofer @kkoci @mhruseckyTurris OS 7.1.0https://gitlab.nic.cz/turris/os/build/-/issues/153Add wifi card ids to iwinfo database2020-06-04T16:54:54+02:00Ghost UserAdd wifi card ids to iwinfo databaseiwinfo patches:
* http://lists.infradead.org/pipermail/openwrt-devel/2020-May/023479.html
* http://lists.infradead.org/pipermail/openwrt-devel/2020-May/023480.htmliwinfo patches:
* http://lists.infradead.org/pipermail/openwrt-devel/2020-May/023479.html
* http://lists.infradead.org/pipermail/openwrt-devel/2020-May/023480.htmlTurris OS 5.0.1https://gitlab.nic.cz/turris/os/build/-/issues/115Replace dependency and file insert patches for turris-webapps with dedicated ...2023-08-16T11:01:11+02:00Karel KociReplace dependency and file insert patches for turris-webapps with dedicated packages and conditional install requestsTurris updater now supports conditional install requests. We should use that instead of patching various packages for webapps. We have to create appropriate packages and then it is just:
```
Install("turris-webapps-FOO", { condition = "F...Turris updater now supports conditional install requests. We should use that instead of patching various packages for webapps. We have to create appropriate packages and then it is just:
```
Install("turris-webapps-FOO", { condition = "FOO" })
```Turris OS 5.2.0https://gitlab.nic.cz/turris/os/build/-/issues/94New package_list for reForis.2019-12-11T15:13:04+01:00Bogdan BodnarNew package_list for reForis.Turris OS 4.0.3