Procházet zdrojové kódy

updating docs for 0.8

afeiszli před 4 roky
rodič
revize
a3118963fa

binární
docs/_build/doctrees/environment.pickle


binární
docs/_build/doctrees/troubleshoot.doctree


+ 4 - 0
docs/_build/html/_sources/troubleshoot.rst.txt

@@ -102,6 +102,10 @@ Netclient
 **I have a handshake with a peer but can't ping it, what gives?**
 **I have a handshake with a peer but can't ping it, what gives?**
   This is commonly due to incorrect MTU settings. Typically, it will be because MTU is too high. Try setting MTU lower on the node. This can be done via netconfig, or by editing the node in the UI. 
   This is commonly due to incorrect MTU settings. Typically, it will be because MTU is too high. Try setting MTU lower on the node. This can be done via netconfig, or by editing the node in the UI. 
 
 
+**I have a hard to reach machine behind a firewall or a corporate NAT, what can I do?**
+  In this situation you can use the Relay Server functionality introduced in Netmaker v0.8 to designate a node as a relay to your "stuck" machine. Simply click the button to make a node into a relay and tell it to relay traffic to this hard-to-reach peer. 
+
+
 CoreDNS
 CoreDNS
 --------
 --------
 **Is CoreDNS required to use Netmaker?**
 **Is CoreDNS required to use Netmaker?**

Rozdílová data souboru nebyla zobrazena, protože soubor je příliš velký
+ 0 - 0
docs/_build/html/searchindex.js


+ 2 - 0
docs/_build/html/troubleshoot.html

@@ -824,6 +824,8 @@ You can also see the current WireGuard configuration with <code class="docutils
 </dd>
 </dd>
 <dt><strong>I have a handshake with a peer but can’t ping it, what gives?</strong></dt><dd><p>This is commonly due to incorrect MTU settings. Typically, it will be because MTU is too high. Try setting MTU lower on the node. This can be done via netconfig, or by editing the node in the UI.</p>
 <dt><strong>I have a handshake with a peer but can’t ping it, what gives?</strong></dt><dd><p>This is commonly due to incorrect MTU settings. Typically, it will be because MTU is too high. Try setting MTU lower on the node. This can be done via netconfig, or by editing the node in the UI.</p>
 </dd>
 </dd>
+<dt><strong>I have a hard to reach machine behind a firewall or a corporate NAT, what can I do?</strong></dt><dd><p>In this situation you can use the Relay Server functionality introduced in Netmaker v0.8 to designate a node as a relay to your “stuck” machine. Simply click the button to make a node into a relay and tell it to relay traffic to this hard-to-reach peer.</p>
+</dd>
 </dl>
 </dl>
 
 
 
 

+ 4 - 0
docs/troubleshoot.rst

@@ -102,6 +102,10 @@ Netclient
 **I have a handshake with a peer but can't ping it, what gives?**
 **I have a handshake with a peer but can't ping it, what gives?**
   This is commonly due to incorrect MTU settings. Typically, it will be because MTU is too high. Try setting MTU lower on the node. This can be done via netconfig, or by editing the node in the UI. 
   This is commonly due to incorrect MTU settings. Typically, it will be because MTU is too high. Try setting MTU lower on the node. This can be done via netconfig, or by editing the node in the UI. 
 
 
+**I have a hard to reach machine behind a firewall or a corporate NAT, what can I do?**
+  In this situation you can use the Relay Server functionality introduced in Netmaker v0.8 to designate a node as a relay to your "stuck" machine. Simply click the button to make a node into a relay and tell it to relay traffic to this hard-to-reach peer. 
+
+
 CoreDNS
 CoreDNS
 --------
 --------
 **Is CoreDNS required to use Netmaker?**
 **Is CoreDNS required to use Netmaker?**

Některé soubory nejsou zobrazeny, neboť je v těchto rozdílových datech změněno mnoho souborů