gravitl/netmaker
1
1
Fork 0
mirror of https://github.com/gravitl/netmaker.git synced 2025-09-30 08:54:25 +08:00
Code Issues Projects Releases Packages Wiki Activity

updating docs for 0.8

Browse source
This commit is contained in:
afeiszli 2021-09-23 12:08:07 -04:00
parent 683d9e61e9
commit a3118963fa
6 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
docs/_build/doctrees/environment.pickle vendored
View file

Binary file not shown.

BIN
docs/_build/doctrees/troubleshoot.doctree vendored
View file

Binary file not shown.

4
docs/_build/html/_sources/troubleshoot.rst.txt vendored
View file

@ -102,6 +102,10 @@ Netclient
**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.
**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
--------
**Is CoreDNS required to use Netmaker?**

2
docs/_build/html/searchindex.js vendored
View file

File diff suppressed because one or more lines are too long

2
docs/_build/html/troubleshoot.html vendored
View file

@ -824,6 +824,8 @@ You can also see the current WireGuard configuration with <code class="docutils
</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>
</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>

4
docs/troubleshoot.rst
View file

@ -102,6 +102,10 @@ Netclient
**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.
**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
--------
**Is CoreDNS required to use Netmaker?**