Merge branch 'main' into dependabot/npm_and_yarn/webpack-5.94.0

docs/faq-windows.md

@@ -37,6 +37,10 @@ If the purpose of your ZeroTier network is solely remoting into office workstati
 [Client Isolation Rules](./faq-rules.md#client-isolation) and [RDP Only Rules](./faq-rules.md#remote-desktop-only-rdp-only)
 :::
 
+### System Service Not Reachable by UI
+
+[System Service Not Reachable by UI](./windows-service-unreachable)
+
 ### Resolving `Port Error` {#port-error}
 
 If you're seeing `PORT ERROR` on Windows, it's likely that the driver did not get installed correctly for some reason.  To fix this, navigate to

docs/multithreading.md

@@ -0,0 +1,33 @@
+---
+title: Multithreading
+description: Enable ZeroTier to use multiple physical cores
+---
+
+As of version `1.14.1` ZeroTier is capable of utilizing more than one CPU core for traffic processing. This enables greater total throughput and more efficient use of machines handling large amounts of traffic.
+
+:::info BETA
+This is currently a beta feature and we welcome any feedback and/or test results. For now it is only available for Linux and is disabled by default. It will be ported to FreeBSD, macOS, and Windows in a future release.
+:::
+
+The feature requires manual activation using the `local.conf` file in the same home directory that stores your node’s identity files. If that file is not already present, create it.
+
+### Example usage
+
+```json title="Example local.conf"
+{
+   "settings":
+   {
+       "multicoreEnabled": true,
+       "concurrency": 2,
+       "cpuPinningEnabled": true
+   }
+}
+```
+
+*[See here](https://docs.zerotier.com/config) for more info on how to configure the client using `local.conf`*
+
+### Tip for success
+
+It is recommended that you choose a concurrency level that is reflective of the actual number of physical (not virtual) cores on your machine. For instance, if `nproc` reports `4`, set a concurrency level of `2`. Additionally, enabling [pinning](https://en.wikipedia.org/wiki/Processor_affinity) seems to improve performance in more cases than not.
+
+Multithreading is unlikely to improve performance over the Internet but will over a physical LAN in most cases.

docs/troubleshooting.md

@@ -136,3 +136,56 @@ The new node ID will have be re-authorized on any networks, and the node's manag
 
 - Delete peers.d too
 - Start the service
+
+## Troubleshooting Connection Issues
+
+It can be a little tricky to figure out why something isn't working. We'll try to improve this. Unfortunately you need to use the [CLI](cli) to troubleshoot.
+
+It's a peer to peer system, so we might need to check 2 or more nodes to deduce where the problem is.
+
+Go through these steps and see [corporate firewalls](corporate-firewalls) and [Router Tips](routertips) for more explanation.
+
+### Peers List
+
+Check this command on both peers
+
+`zerotier-cli peers`
+
+If one device has many "RELAY" connections, it's having a hard time connecting to things.
+
+If the connections to the PLANETs are RELAY, the node is having a very hard time. UDP traffic may be blocked.
+
+### Status
+
+`zerotier-cli info` it eventually says "RELAY" instead of "ONLINE" if UDP traffic is blocked.
+
+### Checking for Symmetric NAT
+
+`zerotier-cli info -j`
+
+Look at the "listeningOn" and "surfaceAddresses". If the surfaceAddress list large is constantly growing for each node you `ping`, this node may be behind Symmetric NAT. Other devices will have a hard time connecting with it.
+See [corporate firewalls](corporate-firewalls) for more info on Symmetric NAT.
+
+Ideally there is 1 surface address for each listening address/port.
+
+For a simplified example, if your computer only has 1 network interface and IP address, `listeningOn` will look like this:
+
+```json
+"listeningOn": [
+    "192.168.100.193/9993",
+    "192.168.100.193/55957",
+    "192.168.100.193/30431"
+    ]
+```
+
+then the `surfaceAddresses` should have only 3 entries
+
+```json
+"surfaceAddresses": [
+    "198.51.100.9/24/9993",
+    "198.51.100.9/30431",
+    "198.51.100.9/2785"
+   ],
+```
+
+Usually there is more going on in these entries and it can be hard to read. The output of `zerotier-cli dump` contains this information. If you send it to us, we can read it for you.

docs/windows-service-unreachable.md

@@ -26,3 +26,21 @@ ZeroTier should now be reachable by the UI client when you restart it.
 ## Why does this happen?
 
 Not entirely sure. IP helper service is a windows service that provides tunneling for IPv6 over IPv4. IP helper grabs 9993 before ZeroTier can. The issue persists through reboots. In the resource monitor, you can see which ports are bound to which services. IP helper is the culprit.
+
+Do you use Docker or WSL and ZeroTier? One of those might be reserving the port in IP Helper.
+
+Try this in a Admin Powershell
+
+```sh
+netsh interface portproxy show all
+```
+
+is 9993 in the results?
+
+Try to delete the entry
+
+```sh
+netsh interface portproxy delete help
+```
+
+Or try killing Docker or WSL and see if the problem goes away. [Let us know](https://discuss.zerotier.com/c/community-support/8) what you find out.

sidebars.js

@@ -170,7 +170,7 @@ module.exports = {
             description: 'ZeroTier on Windows',
             slug: '/windows',
           },
-          items: ['faq-windows', 'chocolatey', 'winget', 'windows-lan-game', 'windows-unknown-node-id']
+          items: ['faq-windows', 'chocolatey', 'winget', 'windows-lan-game', 'windows-unknown-node-id', 'windows-service-unreachable']
         },
         /* ANDROID */
         {
@@ -227,7 +227,7 @@ module.exports = {
             description: 'ZeroTier is designed to operate on resource constrained devices and under 16MB of memory.',
             slug: '/iot',
           },
-          items: ['lbm', 'compatibility', 'bridging', 'proxy', 'route-between-phys-and-virt'],
+          items: ['lbm', 'multithreading', 'compatibility', 'bridging', 'proxy', 'route-between-phys-and-virt'],
         },
         /* FreeBSD */
         {