Merge pull request #334 from AdguardTeam/update-translations

Update translations

Author: SeverAnna

i18n/cs/docusaurus-plugin-content-docs/current/adguard-vpn-for-linux/installation.md

@@ -33,6 +33,10 @@ Stisknutím `y` odsouhlasíte propojení binárního souboru s `/usr/local/bin`
 Podpis můžete ověřit pomocí nástroje `gpg`, abyste prokázali, že se jedná o oficiální verzi AdGuard VPN. [Více na GitHubu](https://github.com/AdguardTeam/AdGuardVPNCLI?tab=readme-ov-file#verify-releases)
 :::
 
+:::note
+You can also install and run the AdGuard VPN for Linux Docker container on MikroTik routers with RouterOS. For more information and detailed instructions, refer to [our dedicated guide](/adguard-vpn-for-linux/setting-up-on-a-router/mikrotik/).
+:::
+
 ## Odinstalace AdGuard VPN pro Linux
 
 Chcete-li odinstalovat AdGuard VPN, zadejte:

i18n/cs/docusaurus-plugin-content-docs/current/adguard-vpn-for-linux/setting-up-on-a-router/mikrotik.md

@@ -0,0 +1,349 @@
+---
+title: How to install AdGuard VPN CLI on MikroTik RouterOS
+sidebar_position: 5
+---
+
+:::info System requirements
+
+- RouterOS 7.6+ with Container feature and start-on-boot support
+- SSH access to the router
+
+:::info
+
+This guide explains how to install and run the AdGuard VPN CLI Docker container on MikroTik routers running RouterOS.
+
+These settings have been tested on RouterOS 7.22. It is recommended to use the latest stable version of RouterOS for better compatibility.
+
+## RouterOS Configuration
+
+### 1. Connect to the router via SSH
+
+```bash
+ssh admin@192.168.1.1
+```
+
+:::note
+
+Replace the IP with your router's address
+
+:::
+
+### 2. Check if the container package is installed
+
+```bash
+/system/package/print
+```
+
+Find the `container` package in the list. If it's not there, install it:
+
+#### Installing container package
+
+1. Download the `.npk` file for your architecture and OS version from [the official website](https://mikrotik.com/download)
+
+2. Upload the `.npk` file to the router:
+
+    ```bash
+    scp container-7.X-platform.npk admin@192.168.1.1:
+    ```
+
+   Replace the IP with your router's address.
+
+3. Verify the file is uploaded:
+
+    ```bash
+    /file/print
+    ```
+
+   You should see the `container-X.XX.npk` file.
+
+4. Reboot the router:
+
+    ```bash
+    /system/reboot
+    ```
+
+   After reboot, the `.npk` file will disappear. This is expected, it means the package was succesfully installed.
+
+5. Verify:
+
+    ```bash
+    /system/package/print
+    ```
+
+   The `container` package should appear in the list.
+
+### 3) Enable Container mode
+
+Enable Container mode and follow the instructions the command gives you. You will need to confirm the device-mode change by performing a cold reboot (physically unplugging and replugging the power).
+
+```bash
+/system/device-mode/update container=yes
+```
+
+:::warning
+
+Do not close the terminal or interrupt the command before unplugging the power — this will cancel the operation.
+
+:::
+
+### 4. Verify that container mode is active
+
+```bash
+/system/device-mode/print
+```
+
+Should show `container: yes`
+
+### 5. Set up networking for the container
+
+#### How it works
+
+In this setup:
+
+- The container acts as a VPN gateway
+- RouterOS routes selected traffic through a separate routing table (`via_vpn`)
+- Traffic is forwarded to the container and then tunneled via AdGuard VPN
+
+Flow:
+
+LAN → RouterOS → Routing rule → Container → VPN → Internet
+
+:::warning
+
+This setup routes all LAN traffic through the VPN container.
+If misconfigured, it may disrupt network connectivity or cause loss of internet access.
+
+:::
+
+Create a veth interface:
+
+```bash
+/interface/veth/add name=veth1 address=172.17.0.2/24 gateway=172.17.0.1
+```
+
+Create a bridge:
+
+```bash
+/interface/bridge/add name=docker
+```
+
+Add veth to bridge:
+
+```bash
+/interface/bridge/port/add bridge=docker interface=veth1
+```
+
+Assign an IP address to the bridge:
+
+```bash
+/ip/address/add address=172.17.0.1/24 interface=docker
+```
+
+Configure NAT for container internet access:
+
+```bash
+/ip/firewall/nat/add chain=srcnat src-address=172.17.0.0/24 out-interface=ether1 action=masquerade
+```
+
+:::note
+
+Replace `ether1` with the name of your WAN interface (e.g. `ether3`, `ether5`). To find it:
+
+1. Run `/ip/route/print` and find the default route (`0.0.0.0/0`, routing-table=main) — note its gateway IP
+2. In the same output, find the connected route (`DAc`) that covers that gateway IP — the interface listed there is your WAN interface
+
+:::
+
+Create routing table for VPN
+
+```bash
+/routing/table/add name=via_vpn fib
+```
+
+Add a default route via the container
+
+```bash
+/ip/route/add dst-address=0.0.0.0/0 gateway=172.17.0.2@main routing-table=via_vpn distance=1 check-gateway=ping
+```
+
+Add a routing rule
+
+```bash
+/routing/rule/add src-address=192.168.88.0/24 action=lookup table=via_vpn
+```
+
+:::note
+
+Replace the IP with your LAN network address
+
+:::
+
+Set DNS servers for LAN clients to a public DNS
+
+```bash
+/ip/dhcp-server/network/set [find address="192.168.88.0/24"] dns-server=1.1.1.1,8.8.8.8
+```
+
+## Running the Container
+
+### Pull image directly from Docker Hub
+
+#### 1. Configure Container registry
+
+Set Docker Hub URL and temporary directory for image extraction
+
+```bash
+/container/config/set registry-url=https://registry-1.docker.io tmpdir=disk1/tmp
+```
+
+:::note
+
+Replace `disk1` with the name of the specific disk you want to work with, selecting it from the list shown in the `/disk/print` output.
+This also applies to the next command.
+
+:::
+
+#### 2. Add the container and pull the image
+
+```bash
+/container/add name=adguardvpn-cli remote-image=adguard/adguardvpn-cli:latest interface=veth1 root-dir=disk1/adguardvpn-cli start-on-boot=yes logging=yes
+```
+
+**Available tags:**
+
+- `adguard/adguardvpn-cli:latest` - latest stable version
+- `adguard/adguardvpn-cli:nightly` - latest nightly build
+- `adguard/adguardvpn-cli:beta` - latest beta version
+- `adguard/adguardvpn-cli:1.7.6-nightly` - specific version
+
+**Parameters:**
+
+- `name=adguardvpn-cli` - container name
+- `remote-image` - Docker Hub image name
+- `interface=veth1` - network interface for the container
+- `root-dir=disk1/adguardvpn-cli` - directory for container files
+- `start-on-boot=yes` - auto-start on router reboot
+- `logging=yes` - enable logging
+
+#### 3. Check download status
+
+```bash
+/container/print
+```
+
+The image will be automatically downloaded and extracted. Wait for the download to complete (status will change to `stopped`).
+
+#### 4. Start the container
+
+```bash
+/container/start adguardvpn-cli
+```
+
+Check the container status
+
+```bash
+/container/print
+```
+
+The container should have the `R` (RUNNING) flag in the first column.
+
+## Initial Setup and AdGuard VPN CLI Authorization
+
+On first launch, the container will not be able to connect to VPN as authentication is required.
+
+### 1. Open a shell inside the container
+
+```bash
+/container/shell adguardvpn-cli
+```
+
+### 2. Set up AdGuard VPN CLI
+
+1. Log in to your account
+
+   To use AdGuard VPN for Linux, you need an AdGuard account.
+
+   You can sign up or log in on our [website](https://auth.adguardaccount.com/login.html) or in the Terminal.
+
+   To sign up or log in, type:
+
+    ```bash
+    adguardvpn-cli login
+    ```
+
+   Note: If failed to link the binary to `/usr/local/bin`, use full file path to run all commands. For example, `/opt/adguardvpn_cli/adguardvpn-cli login`
+
+2. Connect to VPN
+
+   Select a VPN server location that best suits your needs.
+
+   In general, the closer the server is to you, the faster the connection.
+
+   To view available locations, type:
+
+    ```bash
+    adguardvpn-cli list-locations
+    ```
+
+   To connect to a specific location, type:
+
+    ```bash
+    adguardvpn-cli connect -l LOCATION_NAME
+    ```
+
+   Replace LOCATION_NAME with the city, country, or ISO code of the location you want to connect to.
+
+   For quick connect, type:
+
+    ```bash
+    adguardvpn-cli connect
+    ```
+
+   AdGuard VPN will choose the fastest location available and remember it for future quick connections.
+
+3. Adjust your settings
+
+   Get a list of all available AdGuard VPN commands and customize the VPN client to your needs.
+
+   To view all commands, type:
+
+    ```bash
+    adguardvpn-cli --help-all
+    ```
+
+   AdGuard VPN CLI will create a tun0 interface for VPN tunneling.
+
+### 3) Exit the shell
+
+```bash
+exit
+```
+
+### 4. Restart the container
+
+```bash
+/container/stop adguardvpn-cli
+/container/start adguardvpn-cli
+```
+
+After restart, the container will automatically connect to the VPN.
+
+## Check that the VPN is working
+
+### 1. Enter the container shell
+
+```bash
+/container/shell adguardvpn-cli
+```
+
+### 2. Check VPN status
+
+```bash
+adguardvpn-cli status
+```
+
+:::note
+
+For additional information on container configuration, networking, and alternative installation methods, see the [official MikroTik Container documentation](https://help.mikrotik.com/docs/spaces/ROS/pages/84901929/Container)
+
+:::

i18n/cs/docusaurus-plugin-content-docs/current/adguard-vpn-for-linux/setting-up-on-a-router/setting-up-on-a-router.md

@@ -5,6 +5,8 @@ sidebar_position: 1
 
 Přečtěte si, jak nastavit AdGuard VPN pro Linux na routeru.
 
+- [Instructions for MikroTik routers](/adguard-vpn-for-linux/setting-up-on-a-router/mikrotik.md)
+
 - [Pokyny pro routery Keenetic](/adguard-vpn-for-linux/setting-up-on-a-router/keenetic.md)
 
 - [Pokyny pro routery OpenWRT](/adguard-vpn-for-linux/setting-up-on-a-router/openwrt.md)

i18n/cs/docusaurus-plugin-content-docs/current/adguard-vpn-for-routers/installation/keenetic.md

@@ -3,6 +3,12 @@ title: Instalace na routerech Keenetic
 sidebar_position: 3
 ---
 
+:::note
+You can also install and run the AdGuard VPN for Linux on Keenetic routers. This method requires advanced technical knowledge but provides access to all AdGuard VPN features.
+
+For more information and detailed instructions, refer to [our dedicated guide](/adguard-vpn-for-linux/setting-up-on-a-router/keenetic/).
+:::
+
 AdGuard VPN můžete nakonfigurovat na routerech Keenetic od verze KeeneticOS 3.5. Postupujte podle následujících kroků:
 
 1. Nainstalujte systémovou komponentu klienta VPN IKEv2/IPsec. Přejděte do [webového rozhraní](https://help.keenetic.com/hc/en-us/articles/360001923020-Web-interface) výrobce → _Obecná nastavení systému_ → _Aktualizace KeeneticOS a možnosti komponent_ a klikněte na _Možnosti komponent_.

i18n/cs/docusaurus-plugin-content-docs/current/adguard-vpn-for-routers/installation/mikrotik.md

@@ -3,6 +3,12 @@ title: Instalace na routerech MikroTik
 sidebar_position: 2
 ---
 
+:::note
+You can also install and run the AdGuard VPN for Linux Docker container on MikroTik routers with RouterOS. This method requires advanced technical knowledge but provides access to all AdGuard VPN features.
+
+For more information and detailed instructions, refer to [our dedicated guide](/adguard-vpn-for-linux/setting-up-on-a-router/mikrotik/).
+:::
+
 Chcete-li nastavit AdGuard VPN na routeru MikroTik, postupujte podle těchto kroků:
 
 1. Otevřete terminál MikroTik. To můžete provést pomocí příkazového řádku nebo terminálu na svém počítači zadáním: `ssh admin@192.168.88.1`. Alternativně se k němu můžete dostat také prostřednictvím prohlížeče, a to tak, že navštívíte stránku `http://192.168.88.1` a kliknete na záložku Terminál v pravém horním rohu.