user-docs issueshttps://gitlab.nic.cz/turris/user-docs/-/issues2024-03-27T13:02:58+01:00https://gitlab.nic.cz/turris/user-docs/-/issues/147Add how to report Unknown API error in reForis2024-03-27T13:02:58+01:00Josef SchlehoferAdd how to report Unknown API error in reForisWe need to have article, where we will explain which steps are required to have stack trace from foris-controller, so we can fix this like, where to find web developer console in browser, how to get the stack trace and so on.
On our for...We need to have article, where we will explain which steps are required to have stack trace from foris-controller, so we can fix this like, where to find web developer console in browser, how to get the stack trace and so on.
On our forum, I wrote it several times, so at least there is some idea.Aleksandr GumroianAleksandr Gumroianhttps://gitlab.nic.cz/turris/user-docs/-/issues/203/hw/omnia/revisions.md Add info about newer revisions2024-03-04T13:13:27+01:00Marek Novotny/hw/omnia/revisions.md Add info about newer revisionsThe documentation page about Turris Omnia board revisions is incomplete.The documentation page about Turris Omnia board revisions is incomplete.Marek NovotnyMarek Novotnyhttps://gitlab.nic.cz/turris/user-docs/-/issues/200SFP module unstable after TOS4 - VDSL Modem2024-01-09T13:20:39+01:00johnappletreeSFP module unstable after TOS4 - VDSL Modem[Copy paste from the forum:](https://forum.turris.cz/t/user-experience-allnet-all4781-vdsl2-sfp-switch-modul-mini-gbic-vdsl2/7062/105?u=johnappletree)
Whist the module performs on my IPS’s subscriber line generally stable after the swit...[Copy paste from the forum:](https://forum.turris.cz/t/user-experience-allnet-all4781-vdsl2-sfp-switch-modul-mini-gbic-vdsl2/7062/105?u=johnappletree)
Whist the module performs on my IPS’s subscriber line generally stable after the switch from TOS3.x to TOS4.x I noticed intermittent hiccups manifested in the logs
` sfp: module transmit fault indicated`
` sfp: module transmit fault recovered`
and sometimes also
` sfp: module persistently indicates fault, disabling`
Those messages are generated by SFP.C [1] (not available in TOS3.x with kernel 4.9.x) and are pertinent to the check routines implemented for state machine:
- checks signal status (asserted / dessarted) for RX_LOS and TX_FAULT
with
` sfp: module transmit fault indicated`
relating to the signal status of TX_FAULT (`tx-fault in hi IRQ`)
SFP.C tries to clear (recover) the fault fives times in total, pausing one second between each attempt and if successful (`tx-fault in lo IRQ`) prints
` sfp: module transmit fault recovered`
If the five attempts are however exhausted it prints
` sfp: module persistently indicates fault, disabling`
and as a result there is no WAN connectivity. Signal status detection is only attempted again if the interface is being restarted, else the link will remain a down state.
It is not clear why the module most of the times passes the check but other times intermittently fails. Potential reasons could be:
- Module hardware defect that was not exposed in TOS3.x (lacking the presence of SFP.C and related checks)
- Something chocking the I2C bus communication with the module and preventing a timely response (within 300 ms) on the TX_FAULT signal status from the module
- Some bug in the SFP.C code, though its developer is adamant that it is not the case but trusts that the module misbehaves instead
[1] https://github.com/torvalds/linux/blob/master/drivers/net/phy/sfp.chttps://gitlab.nic.cz/turris/user-docs/-/issues/191Explicitly discourage users from sharing diagnostics output publicly2023-01-17T18:10:12+01:00Simon BorekExplicitly discourage users from sharing diagnostics output publiclyIn [Formulating your problem section of Getting Help documentation page](https://docs.turris.cz/basics/support/#formulating-your-problem) there is stated: "If you have logs, include them. But be aware that those __might contain sensitiv...In [Formulating your problem section of Getting Help documentation page](https://docs.turris.cz/basics/support/#formulating-your-problem) there is stated: "If you have logs, include them. But be aware that those __might contain sensitive data__."
As logs are listed as one of the diagnostics modules, it is technically clear the warning applies to them as well, but in practice users shouldn't be required to come to that conclusion themselves.
It might be highly beneficial to add a similar warning addressing diagnostics directly while being placed in an actual warning frame instead of being included as a part of text.
Related: https://gitlab.nic.cz/turris/reforis/reforis-diagnostics/-/issues/9https://gitlab.nic.cz/turris/user-docs/-/issues/182MOX A USB port does not support hub - should be mentioned2022-10-24T12:28:19+02:00Stepan RechnerMOX A USB port does not support hub - should be mentionedAt the [Turris MOX A site](https://docs.turris.cz/hw/mox/modules/a/) in the documentation, it is mentioned among other specifications:
> - USB 3.0 port
But it is not mentioned, that a USB hub inserted in it would not work. Nevertheless...At the [Turris MOX A site](https://docs.turris.cz/hw/mox/modules/a/) in the documentation, it is mentioned among other specifications:
> - USB 3.0 port
But it is not mentioned, that a USB hub inserted in it would not work. Nevertheless, users may expect that. It should be probably mentioned there.
A side note: another description of Turris MOX A is at the website <https://www.turris.cz/cs/mox/moduly/>.
cc: @prohar @dmelinhttps://gitlab.nic.cz/turris/user-docs/-/issues/68Turris OS UCI configuration reference2022-06-06T14:20:03+02:00Karel KociTurris OS UCI configuration referenceThis should be reference table of all possible UCI configurations with use cases and intended purposes we added to OpenWrt. We could even document some of the OpenWrt stuff we touch in Foris and other components. We do not have to docume...This should be reference table of all possible UCI configurations with use cases and intended purposes we added to OpenWrt. We could even document some of the OpenWrt stuff we touch in Foris and other components. We do not have to document every single option in UCI but having table for our extensions makes sense. I am not sure if OpenWrt has some generic sheet about that (they have for example this https://openwrt.org/docs/guide-user/base-system/basic-networking - see tables in that wiki) but we can build on top of that.https://gitlab.nic.cz/turris/user-docs/-/issues/178Feature request: provide steps to boot from SSD without working system2022-05-10T13:23:10+02:00Josef SchlehoferFeature request: provide steps to boot from SSD without working systemHey there,
I noticed that I am not able to use steps given in **Preparation of SSD**, they assume that I have working system (with functional eMMC). That's wrong in my case. Most people will be looking into it when they worn-out their i...Hey there,
I noticed that I am not able to use steps given in **Preparation of SSD**, they assume that I have working system (with functional eMMC). That's wrong in my case. Most people will be looking into it when they worn-out their internal storage.
My u-boot version: ``U-Boot 2019.07 (Oct 05 2020 - 23:50:39 +0000), Build: jenkins-turris-os-packages-dragons-omnia-1753``.
When I selected 7 (``run rescueboot`` does not work], I am able to use steps given in our old documentation, these days, community one: https://wiki.turris.cz/doc/en/howto/omnia_booting_from_external_storagehttps://gitlab.nic.cz/turris/user-docs/-/issues/161Link(s) to versions in changelog recognized as incorrect2022-03-17T17:34:16+01:00Lukas JelinekLink(s) to versions in changelog recognized as incorrectThe remote link checker recognizes links to Turris OS versions in the changelog as incorrect. This is because these links are build in JavaScript and the file itself contains only a template for these links.
We should modify the checker...The remote link checker recognizes links to Turris OS versions in the changelog as incorrect. This is because these links are build in JavaScript and the file itself contains only a template for these links.
We should modify the checker and/or the changelog to drop this false positive warning.https://gitlab.nic.cz/turris/user-docs/-/issues/125Suggest a way/ways how to set up a router if a server with public domain is b...2021-12-21T16:50:26+01:00Stepan RechnerSuggest a way/ways how to set up a router if a server with public domain is behind itBy default, it is possible to connect to a domain located in the same LAN only by adding `*.lan`. It may be an easy way to set it smoother for a user (usable for example for some CTI users). To add this sort of how-to was suggested by @v...By default, it is possible to connect to a domain located in the same LAN only by adding `*.lan`. It may be an easy way to set it smoother for a user (usable for example for some CTI users). To add this sort of how-to was suggested by @vcunat and later on by a user even to set it up by default:
>>>
after searching for hours - I was not able to setup the firewall rules accordingly.
The most simple solution is
####
Adding static address records
Extend section config resolver 'kresd' of /etc/config/resolver by
list hostname_config '/etc/hosts'
#####
Why is this not enabled by default?
...
>>>
It looks like there can be basically two ways.
1. IP based: traffic routed to an external IP (NAT WAN) re-route to the LAN IP address of the server. (According to @vcunat probably the cleaner way)
2. DNS based: for the LAN devices to return the LAN IP address.https://gitlab.nic.cz/turris/user-docs/-/issues/148Describe way how it is possible to verify medkit signature2021-09-21T16:07:26+02:00Josef SchlehoferDescribe way how it is possible to verify medkit signatureIn documentation, we have described how we can verify checksum for medkit, but we need to provide way to geeks how they can verify medkit's signature by using ``signify`` tool.In documentation, we have described how we can verify checksum for medkit, but we need to provide way to geeks how they can verify medkit's signature by using ``signify`` tool.https://gitlab.nic.cz/turris/user-docs/-/issues/142Article about hardening Turris router2021-07-28T14:45:54+02:00Karel KociArticle about hardening Turris routerAlthough Turris routers are as secure as possible out of the box there might still be some considerations and options users could choose to investigate. This should point possibly to topics such as:
* Sentinel
* Jail and Seccomp if we t...Although Turris routers are as secure as possible out of the box there might still be some considerations and options users could choose to investigate. This should point possibly to topics such as:
* Sentinel
* Jail and Seccomp if we trust them enoughhttps://gitlab.nic.cz/turris/user-docs/-/issues/153Add Errata how you can update your router from 4.0-beta (factory)2021-07-28T14:45:41+02:00Josef SchlehoferAdd Errata how you can update your router from 4.0-beta (factory)It would be nice, if we can document in our documentation in FAQ or in Erratum that once users unbox their router and plug them to the Internet, then they should not check any package lists before they are updated to the latest version.
...It would be nice, if we can document in our documentation in FAQ or in Erratum that once users unbox their router and plug them to the Internet, then they should not check any package lists before they are updated to the latest version.
This will prevent threads on our forum like this:
- https://forum.turris.cz/t/aktualizace-mox-4-0-beta/15581/3
- https://forum.turris.cz/t/runtime-string-requests-string-utils-uri-download-failed-the-requested-url-returned-error-404-not-found/14465?u=pepe
Related to https://gitlab.nic.cz/turris/os/build/-/issues/192#note_176493https://gitlab.nic.cz/turris/user-docs/-/issues/156Document ethernet cage leds behaviour for all our boards2021-06-28T09:25:46+02:00Karel KociDocument ethernet cage leds behaviour for all our boardsThis should add a table with status indication LEDs explanation.
* On 1.x we have non-standard behavior so we should describe it for sure
* Omnia has no ethernet cage LEDs and it should be noted that front leds are used instead (blinkin...This should add a table with status indication LEDs explanation.
* On 1.x we have non-standard behavior so we should describe it for sure
* Omnia has no ethernet cage LEDs and it should be noted that front leds are used instead (blinking on activity and light on link up, there is no standard way to indicate speed)
* Mox behavior is being discussed in turris/os/build#272https://gitlab.nic.cz/turris/user-docs/-/issues/97Add software erratum2021-06-22T12:24:51+02:00Karel KociAdd software erratumWe should create article with long-standing software issues we know about we can't do anything about.
Feel free to add any known ones in here for now.
* DDNS scripts might delay update until we kill process
turris-os-packages#265We should create article with long-standing software issues we know about we can't do anything about.
Feel free to add any known ones in here for now.
* DDNS scripts might delay update until we kill process
turris-os-packages#265https://gitlab.nic.cz/turris/user-docs/-/issues/146Add section about updater download error to common-errors2021-06-22T12:23:12+02:00Jan PavlinecAdd section about updater download error to common-errorsThis could help lower the number of complaints from users (forum and/or support). We could also refer them to this page.
Related issues:
- https://gitlab.nic.cz/turris/updater/supervisor/-/issues/24
- https://gitlab.nic.cz/turris/update...This could help lower the number of complaints from users (forum and/or support). We could also refer them to this page.
Related issues:
- https://gitlab.nic.cz/turris/updater/supervisor/-/issues/24
- https://gitlab.nic.cz/turris/updater/supervisor/-/issues/15https://gitlab.nic.cz/turris/user-docs/-/issues/84Create page for vulnerability reporting2021-06-15T10:50:13+02:00Jan PavlinecCreate page for vulnerability reportingThis page should provide contact information and timelines for acknowledgment of receipt and status update timeline.
We can get inspiration from products with certification see https://www.csa.gov.sg/programmes/cybersecurity-labelling/p...This page should provide contact information and timelines for acknowledgment of receipt and status update timeline.
We can get inspiration from products with certification see https://www.csa.gov.sg/programmes/cybersecurity-labelling/product-list
example https://kylaconnect.com/vulnerability-disclosure-policy/
This should help meet the following mandatory requirements for Tier 1 defined by CSA Singapore's Cybersecurity Labeling Scheme
* 5.2-1:The manufacturer shall make a vulnerability disclosure policy publicly available. This policy shall include, at a minimum: contact information for the reporting of issues; and information on timelines for:
1)initial acknowledgment of receipt; and 2)status updates until the resolution of the reported issues.
Related to https://gitlab.nic.cz/turris/biz/singapore-certification/-/issues/1https://gitlab.nic.cz/turris/user-docs/-/issues/150Add information about checking RAID health2021-06-08T18:52:20+02:00Lukas JelinekAdd information about checking RAID healthOriginally from this support ticket: https://tracker.nic.cz/Ticket/Display.html?id=1334688
The documentation page about the reForis storage plugin should contain information how to check RAID disks health.Originally from this support ticket: https://tracker.nic.cz/Ticket/Display.html?id=1334688
The documentation page about the reForis storage plugin should contain information how to check RAID disks health.https://gitlab.nic.cz/turris/user-docs/-/issues/47Guide for statistics graphs2021-06-04T10:11:39+02:00Vojtech MyslivecGuide for statistics graphsThere is a possibility to enable statistics graphs in LuCI. These packages are preinstalled AFAIK and it is needed just to enable it and tune a configuration a bit.
It is really valuable information to monitor device load (like CPU, mem...There is a possibility to enable statistics graphs in LuCI. These packages are preinstalled AFAIK and it is needed just to enable it and tune a configuration a bit.
It is really valuable information to monitor device load (like CPU, memory and network bandwidth) and we should guide the users to get these information as soon as possible.https://gitlab.nic.cz/turris/user-docs/-/issues/134Document SSH connection2021-04-21T11:54:14+02:00Martin PrudekDocument SSH connectionSince we advertise our routers as open and we grant the user full root access to the device we should have a proper documentation page about SSH access. Similar page already exists on our [old wiki](https://wiki.turris.cz/doc/cs/howto/ss...Since we advertise our routers as open and we grant the user full root access to the device we should have a proper documentation page about SSH access. Similar page already exists on our [old wiki](https://wiki.turris.cz/doc/cs/howto/ssh?s[]=putty).https://gitlab.nic.cz/turris/user-docs/-/issues/96Erratum for Turris Shield2021-04-12T10:19:51+02:00Karel KociErratum for Turris ShieldThis should mention at minimum:
* LAN4 port issue
* IP assignment issue (that LAN IP address is removed if connected to 192.168.1.1/24 network on WAN side)This should mention at minimum:
* LAN4 port issue
* IP assignment issue (that LAN IP address is removed if connected to 192.168.1.1/24 network on WAN side)Michal HruseckyMichal Hrusecky