Verified Commit 041a7330 authored by Lukas Jelinek's avatar Lukas Jelinek 📢
Browse files

treewide: Replace incorrect hyphens by en dashes

parent 696304ae
......@@ -20,7 +20,7 @@ package list from the _Updater_ tab. This will provide everything necessary
to boot up your MOX and a new tab in Foris user interface _Managed Devices →
Netboot_ to control them easily.
It will also set up everything needed to boot MOXes over the network - enables
It will also set up everything needed to boot MOXes over the network enables
_TFTP_ in _Dnsmasq_, downloads the latest image, generate keys and prepare
everything.
......@@ -92,7 +92,7 @@ config wifi default
# WiFi specific settings
# 02df_9141 is MOX SDIO WiFi
# 168c_003c is WLE900VX - 5GHz AC PCIe WiFi card in Turris MOX and Turris Omnia
# 168c_003c is WLE900VX 5GHz AC PCIe WiFi card in Turris MOX and Turris Omnia
config device 168c_003c
option channel 'auto5'
......@@ -104,7 +104,7 @@ config device 02df_9141
config device 0000000000000007
option network 'default'
# AP-WiFi specific overrides - format serial_WiFi
# AP-WiFi specific overrides format serial_WiFi
config device 0000000000000007_168c_003c
option channel '40'
option ssid '@@SSID@@-5'
......@@ -149,7 +149,7 @@ channel on the PCIe card. That is done via the following part:
config device 168c_003c
option channel 'auto5'
# 168c_003c is WLE900VX - 5GHz AC PCIe WiFi card in Turris MOX and Turris Omnia
# 168c_003c is WLE900VX 5GHz AC PCIe WiFi card in Turris MOX and Turris Omnia
config device 02df_9141
option channel 'auto24'
```
......@@ -158,7 +158,7 @@ But if you have just one WiFi card in Turris MOX and you want to run 5 GHz on it
you can override the defaults for that specific serial number in the following way
```
# AP-WiFi specific overrides - format serial_WiFi
# AP-WiFi specific overrides format serial_WiFi
config device 0000000000000007_168c_003c
option channel 'auto5'
```
......@@ -175,13 +175,13 @@ provides it with kernel and ramdisk.
That ramdisk boots up, generates ssh keys and uses the key provided via
kernel boot parameters to send that key over ssh to controlling router. It uses
highly restricted account that can do just that - send a little bit of
highly restricted account that can do just that send a little bit of
information about itself and try to get something back. Nothing more. Then it
waits for pairing to be completed by trying to use it's key to get access to
more advanced API.
On the controlling router, when accepting key you will authorize provided
ssh key to access more advanced functions - like download rootfs and
ssh key to access more advanced functions like download rootfs and
configuration. Pairing process will also generate more keys, one aes and one
certification authority to be used by Foris.
......
......@@ -39,7 +39,7 @@ all the past measurements on its [website](https://www.netmetr.cz/en/my.html). T
view your results you have to enter *Sync code* which is displayed in NetMetr
Foris tab.
All the data are - after proper anonymization - also shared on NetMetr
All the data are after proper anonymization also shared on NetMetr
[map](https://www.netmetr.cz/en/map.html) and as an
[open data](https://www.netmetr.cz/en/open-data.html).
......
......@@ -10,7 +10,7 @@ Starting with Turris OS 3.6, you can configure OpenVPN server easily through the
[OpenVPN](https://en.wikipedia.org/wiki/OpenVPN) is an open technology for
[virtual private networks](https://en.wikipedia.org/wiki/Virtual_private_network). It works on the client-server
principle - multiple clients connect to an OpenVPN server to get access to a regularly inaccessible network.
principle multiple clients connect to an OpenVPN server to get access to a regularly inaccessible network.
For example, you can access computers in your home or office LAN from your laptop connected to any Internet connection.
The access is [authenticated](https://en.wikipedia.org/wiki/Authentication) (only permitted clients can connect to
......@@ -71,15 +71,15 @@ you can temporarily lose connection to your router, you just need to refresh the
In most cases you don’t need to change any of the settings. There are these configuration parameters:
* _Listen on IPv6_ - Uncheck only if your IPv6 connection is broken.
* _Protocol_ - Change only if your ISP limits UDP transmission (this practice is defective by nature but some
* _Listen on IPv6_ Uncheck only if your IPv6 connection is broken.
* _Protocol_ Change only if your ISP limits UDP transmission (this practice is defective by nature but some
ISPs even do so).
* _OpenVPN network_ - The default address range is almost always suitable. In very rare cases, your LAN or your
* _OpenVPN network_ The default address range is almost always suitable. In very rare cases, your LAN or your
ISP can use these addresses. Then the network address and the netmask has to be changed to the address not used
in the network.
* _All traffic through vpn_ - Check only if you want all your traffic to the Internet to be routed over your VPN.
* _All traffic through vpn_ Check only if you want all your traffic to the Internet to be routed over your VPN.
For example, you need to connect to your servers which can be accessed only from the address of your router.
* _Use DNS from vpn_ - Check only if you need to use the DNS on your router. For example, your router is connected to
* _Use DNS from vpn_ Check only if you need to use the DNS on your router. For example, your router is connected to
a community network which has private servers and their domain names are not propagated to the public Internet.
!!! note
......
......@@ -2,7 +2,7 @@
board: mox, omnia, 1.x
competency: intermediate
---
# PaKon - Network monitoring (Parental Control)
# PaKon Network monitoring (Parental Control)
## What is Pakon?
......@@ -15,7 +15,7 @@ view and filter records.
## Details
PaKon utilizes **[Suricata](https://suricata-ids.org/) - network threat
PaKon utilizes **[Suricata](https://suricata-ids.org/) network threat
detection engine**. As part of Suricata, there is **Intrusion Detection System
(IDS)**, which is being used. Suricata does the hard work of analyzing raw
network traffic and **provides processed information** (about flows, DNS
......@@ -115,11 +115,11 @@ $ pakon-show -h
You can filter the data by _time_, by _MAC address_ and by _hostname_. You can
also display results aggregated by domain instead of displaying timeline data.
Some domains are hidden in output by default - for example, advertisements,
Some domains are hidden in output by default for example, advertisements,
tracking, CDNs, OCSPs, browser service domains, which makes the output hard to read. You can show all records using the option `–no-filter`. The lists of filtered domains is in `/usr/share/pakon-light/domains_ignore/`. If there is a new CDN or you want to group multiple hostnames from the same domain to one, and you would like to share it with others and include it in a new Turris OS release, you can contribute it in [pakon-light-lists](https://gitlab.nic.cz/turris/pakon-light-lists) repository.
## A few sidenotes
- In some cases, application level protocol is unknown - `?`.
- In some cases, application level protocol is unknown `?`.
It can happen in case of failed connection or unrecognized protocol. In those
cases, you can still get some idea about it from the destination port.
- Web pages commonly include content from multiple domains, which means that
......@@ -148,7 +148,7 @@ paired with.
Even if the DNS query was not performed (eg. when name/IP mapping is hardcoded
in the hosts file), Suricata is often able to determine the name from
application protocol - in case of HTTP and TLS. HTTP sends hostname as its
application protocol in case of HTTP and TLS. HTTP sends hostname as its
header. TLS is encrypted, but when the connection is opened (during TLS
handshake), client sends the name of server (TLS SNI) and server sends it's
certificate. These are both sent unencrypted, so Suricata can read it even
......@@ -156,7 +156,7 @@ though the data flow is later encrypted.
In case of other protocols, the detection relies just on DNS names. Also
**note that tunneling protocols (VPNs, SSH, proxies, Tor) can hide the activity
entirely** - you will only see the flow to the proxy/gateway and not the actual
entirely** you will only see the flow to the proxy/gateway and not the actual
traffic underneath. There is nothing that can be done about that.
### Is it possible to have client names instead of their MAC addresses?
......@@ -164,15 +164,15 @@ Yes, you need to do it in the advanced administration interface LuCI. From the
menu in _Network_ and choose _DHCP and DNS_. In the tab menu, you should see
_Static Leases_.
![Screenshot - LuCI DHCP & DNS tab menu](dhcp-dns-tab-menu.png)
![Screenshot LuCI DHCP & DNS tab menu](dhcp-dns-tab-menu.png)
You don't have to set a proper static lease to see names in PaKon - just fill
You don't have to set a proper static lease to see names in PaKon just fill
in the name and select MAC address. If you fill in also the IP address, you
create a static lease - meaning that the device will always get the same IP
create a static lease meaning that the device will always get the same IP
address. For more details about static leases click
[here](../luci/static-dhcp/static-dhcp.md).
![Screenshot - LuCI Static lease](static-lease.png)
![Screenshot LuCI Static lease](static-lease.png)
### Can I configure the list of monitor networks for PaKon?
Yes, you can change the list of monitor networks in configuration file
......@@ -187,7 +187,7 @@ monitor and then restart these two services by using the following commands:
### Can I clear collected data?
There is a way how to do it in the command-line interface.
You need to connect to your via SSH and run these following commands, which will
stop process pakon-monitor, remove two databases - temporary one and persistent
stop process pakon-monitor, remove two databases temporary one and persistent
and then it will create a temporary database from scratch.
```
/etc/init.d/pakon-monitor stop
......
......@@ -119,7 +119,7 @@ Turris OS 5 is based on top of [OpenWrt 19.07](https://openwrt.org/releases/19.0
with our feed and few patches. It supports [Turris MOX](../hw/mox/intro.md) and [Turris Omnia](../hw/omnia/omnia.md) and
there is an experimental support for [Turris 1.x](../hw/turris-1x/turris-1x.md) routers.
One important feature from Turris OS 3.x is still missing - possibility to
One important feature from Turris OS 3.x is still missing possibility to
configure honeypots and various aspects of security data collection from web ui.
This is going to be added to the minor versions of Turris OS 5.x.
......@@ -127,7 +127,7 @@ New features:
* Added support for secondary IP addresses for DNS servers
* Added possibility to add custom DNS forwarder
* Added support for DVB tuners - Astrometa DVB-T2 and Xbox One
* Added support for DVB tuners Astrometa DVB-T2 and Xbox One
* Redesigned Foris, which is being in development (opt-in)
* Optional WPA3 support
......
......@@ -48,7 +48,7 @@ address is collected by the software.
See the [setup page](setup.md#important-note-about-internet-service-providers)
for details.
### HaaS - Honeypot as a Service
### HaaS Honeypot as a Service
HaaS is a publicly available service which uses SSH Honeypot in order to catch
the pieces of information about the attacker's credentials, behavior and so on.
......@@ -99,4 +99,4 @@ could be seen on [HaaS project website](https://haas.nic.cz).
![HaaS Session](haas-session.png)
Sadly, there is currently no way to visualize what your own router collects from
Firewall monitoring and Minipots - a feature we are working hard on now.
Firewall monitoring and Minipots a feature we are working hard on now.
......@@ -3,7 +3,7 @@ board: shield, mox, omnia, 1.x
---
# Dynamic Firewall
The dynamic firewall (A.K.A. DynFW) is Turris IDS and IPS system - the tool for
The dynamic firewall (A.K.A. DynFW) is Turris IDS and IPS system the tool for
detecting network attackers and preventing them from attacking your device. It is
a part of Turris [data collection](../collect.md).
......@@ -54,7 +54,7 @@ types: `dynfw/list` and `dynfw/delta`. As a protocol,
[ZeroMQ](https://zeromq.org/) is used with
[PUB/SUB](http://zguide2.zeromq.org/page:all#Getting-the-Message-Out) pattern
and messages are standard ZeroMQ multipart message. The first frame is the
topic - aka message type - as simple string so PUB/SUB will work. Second frame
topic aka message type as simple string so PUB/SUB will work. Second frame
is message itself encoded using [message pack](https://msgpack.org/).
......
......@@ -28,7 +28,7 @@ When done, you can see at the _Overview_ page that data collection is disabled.
[HaaS](collect.md#haas-honeypot-as-a-service) is not operational by default
because it requires a few steps:
1. Register on our website - [HaaS.nic.cz](https://haas.nic.cz).
1. Register on our website [HaaS.nic.cz](https://haas.nic.cz).
2. There, in section _My Honeypot_ click on _Add new device_. After naming it,
you will get a **token**.
![HaaS Device](haas-device.png)
......
......@@ -29,7 +29,7 @@ uci set sentinel.main.agreed_with_eula_version=1 && uci commit
In both cases, few extra steps are needed to activate HaaS:
1. Register on our website - [HaaS.nic.cz](https://haas.nic.cz).
1. Register on our website [HaaS.nic.cz](https://haas.nic.cz).
2. There, in section _My Honeypot_ click on _Add new device_. After
naming it, you will get a **token**
![HaaS Device](haas-device.png)
......
......@@ -13,7 +13,7 @@ connection to the internet.
Because we want to make the first setup smooth, Ethernet port will be set
to LAN at the beginning of the first setup. **You shouldn't connect your MOX
directly to the internet**. Configure it somewhere in safe environment - like
directly to the internet**. Configure it somewhere in safe environment like
your local network or directly connected to your computer. Later on, you can
change the purpose of your only Ethernet port.
......
......@@ -21,7 +21,7 @@ without forwarding.
### DNS forwarding
DNS forwarding is enabled by default. It means all DNS queries are sent to your ISP's DNS forwarding servers (or other
DNS forwarders if set so - see bellow). This is the very recommended setting and should be left unchanged unless
DNS forwarders if set so see bellow). This is the very recommended setting and should be left unchanged unless
there is a very good reason to change it.
*What may be such reason? For example, DNSSEC on your ISP's DNS servers is broken and DoT (see bellow) port is blocked.*
......@@ -95,7 +95,7 @@ useful to wait for a while before running this test.
What particular results mean:
* _DNS_ - your router can successfully execute DNS queries and get responses
* _DNSSEC_ - your router can successfully execute DNSSEC queries and get correct (trustfully signed and intact)
* _DNS_ your router can successfully execute DNS queries and get responses
* _DNSSEC_ your router can successfully execute DNSSEC queries and get correct (trustfully signed and intact)
responses
......@@ -29,12 +29,12 @@ networks configured on your router.
Unless you want to use static addresses in the whole guest network (it's probably very rare) you need to have
the DHCP server enabled. This is the default option. The DHCP server has three parametres:
* _DHCP start_ - the first address inside the address space which may be leased (assigned) via DHCP. For example,
* _DHCP start_ the first address inside the address space which may be leased (assigned) via DHCP. For example,
if it is 100 and your network is 10.111.222.0 your DHCP leases addresses beginning 10.111.222.100. The default
value 100 usually need not to be changed.
* _DHCP max leases_ - the maximum addresses to be leased to computers. It effectively means if you have this
* _DHCP max leases_ the maximum addresses to be leased to computers. It effectively means if you have this
value set to 150 (the default) and the first leased address is 10.111.222.100, the last one is 10.111.222.249.
* _Lease time (hours)_ - this is how long an address is leased to a computer (the default is 1 hour and
* _Lease time (hours)_ this is how long an address is leased to a computer (the default is 1 hour and
is suitable for most cases). If this value is too high and the computers in the LAN "rotate" very often
(e.g. in an Internet café) the address space may be exhausted and new device will not get their addresses.
Too low values may lead to frequent address changes and some networking problems.
......
......@@ -42,12 +42,12 @@ field. The field _Network netmask_ should contain 255.255.255.0 as written above
Unless you want to use static addresses in the whole LAN you need to have the DHCP server enabled. This is the
default option. The DHCP server has three parameters:
* _DHCP start_ - the first address inside the address space which may be leased (assigned) via DHCP. For example,
* _DHCP start_ the first address inside the address space which may be leased (assigned) via DHCP. For example,
if it is 100 and your network is 192.168.2.0 your DHCP leases addresses beginning 192.168.2.100. The default
value 100 usually need not to be changed.
* _DHCP max leases_ - the maximum addresses to be leased to computers. It effectively means if you have this
* _DHCP max leases_ the maximum addresses to be leased to computers. It effectively means if you have this
value set to 150 (the default) and the first leased address is 192.168.2.100 the last one is 192.168.2.249.
* _Lease time (hours)_ - this is how long an address is leased to a computer (the default is 12 hours and
* _Lease time (hours)_ this is how long an address is leased to a computer (the default is 12 hours and
is suitable for most cases). If this value is too high and the computers in the LAN "rotate" very often
(e.g. in an Internet café) the address space may be exhausted and new device will not get their addresses.
Too low values may lead to frequent address changes and some networking problems.
......@@ -87,12 +87,12 @@ In some cases, useage of a specific hostname may be required. Write it into the
This mode is the default because your Turris should have a fixed address to be easily accessed (this can be
accomplished by some DHCP servers too but it is more complex).
* _IP address_ (mandatory) - it's something like 192.168.5.122.
* _Network mask_ (mandatory) - something like 255.255.255.0.
* _Gateway_ (mandatory) - something like 192.168.5.1.
* _DNS server 1 (IPv4)_ (optional) - may be left empty because there is a built-in DNS resolver capable to
* _IP address_ (mandatory) it's something like 192.168.5.122.
* _Network mask_ (mandatory) something like 255.255.255.0.
* _Gateway_ (mandatory) something like 192.168.5.1.
* _DNS server 1 (IPv4)_ (optional) may be left empty because there is a built-in DNS resolver capable to
work without it. But some ISPs require customers to use specific DNS servers. In such case fill in the first
of the addresses (or the only one) of your DNS servers/resolvers.
* _DNS server 2 (IPv4)_ (optional) - if you have more than one server/resolver use the second one here.
* _DNS server 2 (IPv4)_ (optional) if you have more than one server/resolver use the second one here.
![Static IP address](computer-static.png)
......@@ -67,7 +67,7 @@ drive takes a long time as data need to be moved out of it first and
!!! tip
No additional reboot is needed to extend/shrink your storage. Actually
quite opposite - everything happens at runtime, so avoid reboot till you
quite opposite everything happens at runtime, so avoid reboot till you
get notification that everything successfully finished.
......@@ -88,6 +88,6 @@ level will be set and data rearranged.
Valid options are the following:
* `raid1` - every piece of data is kept on two different drives (no matter how many drives you have), so if one drive fails, you can still get to your data
* `single` - there is only one copy of data - more space, but not redundancy
* `custom` - raid level is unchanged and only rebalance is done after adding/removing drive
* `raid1` every piece of data is kept on two different drives (no matter how many drives you have), so if one drive fails, you can still get to your data
* `single` there is only one copy of data more space, but not redundancy
* `custom` raid level is unchanged and only rebalance is done after adding/removing drive
......@@ -38,13 +38,13 @@ acquired via DHCP.
After switching to this mode, several text fields are displayed. Write in the values you have acquired from your ISP.
* _IP address_ (mandatory) - it's something like 192.168.5.122.
* _Network mask_ (mandatory) - something like 255.255.255.0.
* _Gateway_ (mandatory) - something like 192.168.5.1.
* _DNS server 1 (IPv4)_ (optional) - may be left empty because there is a built-in DNS resolver capable to
* _IP address_ (mandatory) it's something like 192.168.5.122.
* _Network mask_ (mandatory) something like 255.255.255.0.
* _Gateway_ (mandatory) something like 192.168.5.1.
* _DNS server 1 (IPv4)_ (optional) may be left empty because there is a built-in DNS resolver capable to
work without it. But some ISPs require customers to use specific DNS servers. If your ISP provided you
such DNS server adress(es) write it in here (for more addresses, use the first one).
* _DNS server 2 (IPv4)_ (optional) - if your ISP provided you more than one DNS server address write in the
* _DNS server 2 (IPv4)_ (optional) if your ISP provided you more than one DNS server address write in the
second one.
![IPv4 static configuration](ipv4-static.png)
......@@ -87,12 +87,12 @@ into the _Custom DUID_ field.
This mode of native IPv6 is similar to its equivalent in the IPv4 world. Write in the values you have acquired from
your ISP.
* _IPv6 address_ (mandatory) - it's something like 2001:db8:be13:37da::1/64 (this address includes the prefix
* _IPv6 address_ (mandatory) it's something like 2001:db8:be13:37da::1/64 (this address includes the prefix
length).
* _IPv6 gateway_ (mandatory) - something like 2001:db8:be13:37da:ffff::1.
* _IPv6 prefix_ (mandatory) - something like 2001:db8:be13:37da::/64.
* _DNS server 1 (IPv6)_ (optional) - see above (but an IPv6 address is used here).
* _DNS server 2 (IPv6)_ (optional) - see above.
* _IPv6 gateway_ (mandatory) something like 2001:db8:be13:37da:ffff::1.
* _IPv6 prefix_ (mandatory) something like 2001:db8:be13:37da::/64.
* _DNS server 1 (IPv6)_ (optional) see above (but an IPv6 address is used here).
* _DNS server 2 (IPv6)_ (optional) see above.
![IPv6 static configuration](ipv6-static.png)
......@@ -118,15 +118,15 @@ may have to set it manually into the _Public IPv4_ field.
on specially configured IPv4 links. 6in4 doesn't require a static public IPv4 address on your side but you need to have
a tunnel broker which provides you the values to write into the text fields.
* _Provider IPv4_ - the tunnel broker's IPv4 address to be used as the endpoint.
* _Routed IPv6 prefix_ - the IPv6 prefix to be routed to your network.
* _MTU_ - the maximum transmission unit; often may be left the default value (1480)
* _Dynamic IPv4 handling_ - check in if you have a dynamic public IPv4 address (this information should be
* _Provider IPv4_ the tunnel broker's IPv4 address to be used as the endpoint.
* _Routed IPv6 prefix_ the IPv6 prefix to be routed to your network.
* _MTU_ the maximum transmission unit; often may be left the default value (1480)
* _Dynamic IPv4 handling_ check in if you have a dynamic public IPv4 address (this information should be
obtained from your ISP) or if your tunnel broker requires to use your credentials (see bellow) instead of
your static IPv4 address.
* _Tunnel ID_ - obtain it from your tunnel broker
* _Username_ - obtain it from your tunnel broker
* _Key_ - obtain it from your tunnel broker
* _Tunnel ID_ obtain it from your tunnel broker
* _Username_ obtain it from your tunnel broker
* _Key_ obtain it from your tunnel broker
![IPv6 6in4 configuration](ipv6-6in4.png)
......@@ -152,10 +152,10 @@ useful to wait for a while before running this test.
What particular results mean:
* _IPv4 connectivity_ - your router has a working IPv4 address and can access machines inside the current network.
* _IPv4 connectivity_ your router has a working IPv4 address and can access machines inside the current network.
* _IPv4 gateway connectivity_ - your router has a working gateway IPv4 address and can access IPv4 machines on the
Internet.
* _IPv6 connectivity_ - your router has a working IPv6 address and can access machines inside the current network.
* _IPv6 connectivity_ your router has a working IPv6 address and can access machines inside the current network.
* _IPv6 gateway connectivity_ - your router has a working gateway IPv6 address and can access IPv6 machines on the
Internet.
......
......@@ -18,10 +18,10 @@ of the page. Then click the _Add_ button under that list.
Fill the new row with:
* _Hostname_ - any name you want to identify the device.
* _MAC-Address_ - Hardware identification number. It can be select from the list of list MAC addresses of connected
* _Hostname_ any name you want to identify the device.
* _MAC-Address_ Hardware identification number. It can be select from the list of list MAC addresses of connected
devices or filled manually by selecting the *\-\-custom\-\-* option.
* _IPv4-Address_ - An IP address to be permanently assigned to a device identified by MAC address. It can be select
* _IPv4-Address_ An IP address to be permanently assigned to a device identified by MAC address. It can be select
from the list of last used IP addresses or filled manually by selecting the *\-\-custom\-\-* option.
![Screenshot 1](screenshot-3.png)
......
......@@ -199,6 +199,6 @@ useful to wait for a while before running this test.
What particular results mean:
* _DNS_ - your router can successfully execute DNS queries and get responses,
* _DNSSEC_ - your router can successfully execute DNSSEC queries and get
* _DNS_ your router can successfully execute DNS queries and get responses,
* _DNSSEC_ your router can successfully execute DNSSEC queries and get
correct (trustfully signed and intact) responses.
......@@ -83,7 +83,7 @@ drive takes a long time as data need to be moved out of it first and
!!! tip
No additional reboot is needed to extend/shrink your storage. Actually
quite opposite - everything happens at runtime, so avoid reboot till you get a
quite opposite everything happens at runtime, so avoid reboot till you get a
notification that everything is successfully finished.
......@@ -96,10 +96,10 @@ CLI.
Valid options are the following:
* `raid1` - every piece of data is kept on two different drives (no matter how
* `raid1` every piece of data is kept on two different drives (no matter how
many drives you have), so if one drive fails, you can still get to your data
* `single` - there is only one copy of data - more space, but not redundancy
* `custom` - the RAID level is unchanged and only rebalance is done after
* `single` there is only one copy of data more space, but not redundancy
* `custom` the RAID level is unchanged and only rebalance is done after
adding/removing the drive
### Web interface
......
......@@ -18,7 +18,7 @@ faster.
sensitive data**.
If you are contacting official Turris support, always include the S/N of your
router - you can see this either on the bottom of your router, _About_ tab in
router you can see this either on the bottom of your router, _About_ tab in
_reForis_ or as the output of command `crypto-wrapper serial-number`.
## Getting logs
......@@ -80,13 +80,13 @@ command line tool).
$ scp root@192.168.1.1:/tmp/diag.gz <your destination>
```
- using SFTP client (like Filezilla)
using SFTP client (like Filezilla)
In a SFTP client, create new connection with credentials similar to SSH connection:
- **Host**: _your router IP address/hostname. By default_ `192.168.1.1`
- **username**: `root`
- **port**: `22`
**Host**: _your router IP address/hostname. By default_ `192.168.1.1`
**username**: `root`
**port**: `22`
!!! info
We prefer to have these complete diagnostics, but if you are experienced user
......
......@@ -10,7 +10,7 @@ them carefully.
## General rules
- Write readable and well-structured code.
- Simple is better than complex, explicit is better than implicit etc. - see
- Simple is better than complex, explicit is better than implicit etc. see
[The Zen of Python](https://www.python.org/dev/peps/pep-0020/).
- Use accurate names for classes, variables, constants,
functions/methods, modules etc. For example, `read_file` is better than
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment