Administrator/NANOKVM-sipeed_wiki-MIRROR
1
0
Fork 0
mirror of https://github.com/sipeed/sipeed_wiki.git synced 2026-11-09 17:44:31 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs(nanokvm-go): remove remote network comparisons

Browse Source 
Drop the comparison sections from the Tailscale, Sipeed Remote Network,
NetBird, and ZeroTier guides. Keep the actionable switch instructions and
the Cloud/self-hosted limitation notes.
This commit is contained in:
liangziyue
2026-10-29 18:48:33 +08:00
committed by Guoguo
parent 13022a8c1a
commit d384105f1a
8 changed files with 9 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/hardware/en/kvm/NanoKVM_Go/network/netbird.md
View File

@@ -14,18 +14,6 @@ NanoKVM Go -- NetBird virtual network -- remote computer or phone
> The NetBird integration adds only NanoKVM Go itself to the virtual network. It does not bring other devices or subnets from the local network into the virtual network.
## Compared with other remote network options
NetBird belongs to the same category as [Tailscale](tailscale.html) and [Sipeed Remote Network](sipeed_remote_network.html): both ends are connected through a virtual network, with no public server required. The differences are the control server and the account system:
| Option | Control server | Account required | Client on the access device |
| --- | --- | --- | --- |
| NetBird | NetBird Cloud | NetBird account | NetBird |
| Tailscale | Tailscale | Tailscale account | Tailscale |
| Sipeed Remote Network | Sipeed | No | Tailscale |
[frp](frp.html) and [Cloudflare Tunnel](cloudflare_tunnel.html) are tunneling solutions that require a public server or a domain. [Static IP](static_ip.html) only fixes the LAN address and cannot provide external access. If you do not have a public server, start with a mesh option such as NetBird.
> The built-in NetBird integration currently connects to NetBird Cloud only (management server `api.netbird.io`). A self-hosted NetBird management server cannot be configured.
## Prerequisites

6
docs/hardware/en/kvm/NanoKVM_Go/network/sipeed_remote_network.md
View File

@@ -26,11 +26,9 @@ Before starting, make sure that:
> If the `Sipeed Remote Network` option is not available on the settings page, check for and install the latest NanoKVM Go system and application updates.
## Differences from Tailscale
## Switching connection methods
The two methods differ in the control server they use: `Sipeed Remote Network` is provided by Sipeed and does not require a Tailscale account, while [Tailscale](tailscale.html) is provided by Tailscale and requires you to register and sign in.
To switch from the method you are using to the other one, click `Exit` on the NanoKVM Go page and confirm. The device leaves its current network and returns to the `Choose a connection network` page, where you can select the other method.
To switch between Sipeed Remote Network and Tailscale, click `Exit` on the NanoKVM Go page and confirm. The device leaves its current network and returns to the `Choose a connection network` page, where you can select the other method.
![Exit the current network and return to the network selection page](../../../../assets/NanoKVM/go/network/nanokvm_go_sipeed_remote_network_exit_en.webp)

6
docs/hardware/en/kvm/NanoKVM_Go/network/tailscale.md
View File

@@ -26,13 +26,11 @@ Before starting, make sure that:
> If the Tailscale option is not available on the settings page, check for and install the latest NanoKVM Go system and application updates.
## Differences from the Sipeed Remote Network
NanoKVM Go supports two connection methods. `Sipeed Remote Network` uses a control server provided by Sipeed and does not require a Tailscale account; see [Sipeed Remote Network](sipeed_remote_network.html) for setup. Tailscale, the method described in this guide, uses a control server provided by Tailscale and requires you to register and sign in. Either way, the Tailscale client must be installed on the computer or phone used for remote access.
## Switching connection methods
![Choose a connection network on NanoKVM Go](../../../../assets/NanoKVM/go/network/nanokvm_go_tailscale_network_select_en.webp)
To switch from the method you are using to the other one, click `Exit` on the NanoKVM Go page and confirm. The device leaves its current network and returns to the `Choose a connection network` page, where you can select the other method.
To switch between Sipeed Remote Network and Tailscale, click `Exit` on the NanoKVM Go page and confirm. The device leaves its current network and returns to the `Choose a connection network` page, where you can select the other method.
![Exit the current network and return to the network selection page](../../../../assets/NanoKVM/go/network/nanokvm_go_sipeed_remote_network_exit_en.webp)

13
docs/hardware/en/kvm/NanoKVM_Go/network/zerotier.md
View File

@@ -14,21 +14,8 @@ NanoKVM Go -- ZeroTier virtual network -- remote computer or phone
> The ZeroTier integration does not automatically share NanoKVM Go's local network with other members. Access to other devices on that LAN depends on the Managed Routes configured in the ZeroTier network.
## Compared with other remote network options
ZeroTier belongs to the same category as [Tailscale](tailscale.html), [NetBird](netbird.html), and [Sipeed Remote Network](sipeed_remote_network.html): a virtual network that does not require a public server. The main differences are how a device joins the network and how it is authorized:
| Option | Network identifier | Device authorization | Client on the access device |
| --- | --- | --- | --- |
| ZeroTier | 16-digit hexadecimal Network ID | Authorize the Node ID in ZeroTier Central | ZeroTier |
| NetBird | NetBird account | Sign in to the same account | NetBird |
| Tailscale | Tailscale account / Tailnet | Sign in to the same account | Tailscale |
| Sipeed Remote Network | Sipeed pairing code | 6-digit claim code + 3-digit verification | Tailscale |
ZeroTier does not require signing in to an account on NanoKVM Go, but you must create a network in ZeroTier Central and authorize the NanoKVM Go Node ID there.
[frp](frp.html) and [Cloudflare Tunnel](cloudflare_tunnel.html) are tunneling solutions that require a public server or a domain. [Static IP](static_ip.html) only fixes the LAN address and cannot provide external access.
> The page does not provide a configuration entry for a self-hosted ZeroTier controller or a custom Planet. Use a network hosted on ZeroTier Central.
## Prerequisites

12
docs/hardware/zh/kvm/NanoKVM_Go/network/netbird.md
View File

@@ -12,18 +12,6 @@ NanoKVM Go ── NetBird 虚拟网络 ── 外网电脑或手机
> NanoKVM Go 的 NetBird 集成只把 NanoKVM Go 自己加入虚拟网络，不会把设备所在局域网的其他设备或网段带进来。
## 与其他远程网络方式的区别
NetBird 和 [Tailscale](tailscale.html)、[Sipeed 远程网络](sipeed_remote_network.html) 属于同一类方案：靠虚拟组网打通两端，不需要公网服务器。区别在控制服务器和账号体系：
| 方式 | 控制服务器 | 需要账号 | 访问端客户端 |
| --- | --- | --- | --- |
| NetBird | NetBird Cloud | NetBird 账号 | NetBird |
| Tailscale | Tailscale | Tailscale 账号 | Tailscale |
| Sipeed 远程网络 | Sipeed | 不需要 | Tailscale |
[frp](frp.html) 和 [Cloudflare Tunnel](cloudflare_tunnel.html) 属于内网穿透，需要公网服务器或域名；[静态 IP](static_ip.html) 只固定局域网地址，不能从外网访问。没有公网服务器时，优先考虑 NetBird 这类组网方案。
> 目前 NanoKVM Go 内置的 NetBird 固定连接 NetBird Cloud（管理服务器 `api.netbird.io`），暂不支持填写自建的 NetBird 管理服务器地址。
## 使用前准备

6
docs/hardware/zh/kvm/NanoKVM_Go/network/sipeed_remote_network.md
View File

@@ -26,11 +26,9 @@ Sipeed 远程网络由 Sipeed 提供控制服务器，设备之间点对点直
> 如果设置页面中没有 `Sipeed 远程网络` 选项，请先检查并更新 NanoKVM Go 的系统和应用版本。
## 与 Tailscale 的区别
## 切换连接方式
两种方式的区别在控制服务器：`Sipeed 远程网络` 由 Sipeed 提供，不需要注册 Tailscale 账号；[Tailscale](tailscale.html) 由 Tailscale 提供，需要注册并登录 Tailscale 账号。
已经启用过其中一种方式、想改用另一种时，在 NanoKVM Go 页面点击 `退出` 并确认，设备会移出当前网络并返回 `选择连接网络` 页面，重新选择即可。
已经启用过 Sipeed 远程网络或 Tailscale，想切换时，在 NanoKVM Go 页面点击 `退出` 并确认，设备会移出当前网络并返回 `选择连接网络` 页面，重新选择即可。
![退出当前网络并返回网络选择页面](../../../../assets/NanoKVM/go/network/nanokvm_go_sipeed_remote_network_exit.webp)

6
docs/hardware/zh/kvm/NanoKVM_Go/network/tailscale.md
View File

@@ -26,13 +26,11 @@ NanoKVM Go ── Tailscale 虚拟网络 ── 外网电脑或手机
> 如果设置页面中没有 Tailscale 选项，请先检查并更新 NanoKVM Go 的系统和应用版本。
## 与 Sipeed 远程网络的区别
NanoKVM Go 支持两种连接方式：`Sipeed 远程网络` 由 Sipeed 提供控制服务器，不需要注册 Tailscale 账号，配置方法见 [Sipeed 远程网络连接](sipeed_remote_network.html)；另一种是 Tailscale，由 Tailscale 提供控制服务器，需要注册并登录 Tailscale 账号，也就是本文介绍的这种方式。两种方式的访问端（电脑或手机）都需要安装 Tailscale 客户端。
## 切换连接方式
![在 NanoKVM Go 中选择连接网络的方式](../../../../assets/NanoKVM/go/network/nanokvm_go_tailscale_network_select.webp)
已经启用过其中一种方式、想改用另一种时，在 NanoKVM Go 页面点击 `退出` 并确认，设备会移出当前网络并返回 `选择连接网络` 页面，重新选择即可。
已经启用过 Sipeed 远程网络或 Tailscale，想切换时，在 NanoKVM Go 页面点击 `退出` 并确认，设备会移出当前网络并返回 `选择连接网络` 页面，重新选择即可。
![退出当前网络并返回网络选择页面](../../../../assets/NanoKVM/go/network/nanokvm_go_sipeed_remote_network_exit.webp)

15
docs/hardware/zh/kvm/NanoKVM_Go/network/zerotier.md
View File

@@ -14,20 +14,7 @@ NanoKVM Go ── ZeroTier 虚拟网络 ── 外网电脑或手机
> NanoKVM Go 的 ZeroTier 集成不会自动把设备所在局域网共享给其他成员；能否访问局域网中的其他设备，取决于 ZeroTier 网络是否配置了对应的 Managed Route。
## 与其他远程网络方式的区别
ZeroTier 和 [Tailscale](tailscale.html)、[NetBird](netbird.html)、[Sipeed 远程网络](sipeed_remote_network.html) 一样，属于虚拟组网方案，不需要公网服务器。区别主要在网络的加入和授权方式：
| 方式 | 网络标识 | 设备授权 | 访问端客户端 |
| --- | --- | --- | --- |
| ZeroTier | 16 位十六进制 Network ID | 在 ZeroTier Central 授权 Node ID | ZeroTier |
| NetBird | NetBird 账号 | 登录同一账号 | NetBird |
| Tailscale | Tailscale 账号 / Tailnet | 登录同一账号 | Tailscale |
| Sipeed 远程网络 | Sipeed 配对码 | 6 位认领码 + 3 位核对 | Tailscale |
ZeroTier 不需要在 NanoKVM Go 上登录账号，但需要先在 ZeroTier Central 创建网络，并在 Central 中授权 NanoKVM Go 的 Node ID。
[frp](frp.html) 和 [Cloudflare Tunnel](cloudflare_tunnel.html) 属于内网穿透，需要公网服务器或域名；[静态 IP](static_ip.html) 只固定局域网地址，不能从外网访问。
> ZeroTier 不需要在 NanoKVM Go 上登录账号，但需要先在 ZeroTier Central 创建网络，并在 Central 中授权 NanoKVM Go 的 Node ID。
> 页面不提供自建 ZeroTier 控制器或自定义 Planet 的配置入口，请使用 ZeroTier Central 上的网络。