Changes

2,764 bytes added , 13 May

no edit summary

Line 88: Line 88:

<tr>

−

<td>TUN (tunnel) {{!}} TAP (bridged); default: TUN (tunnel)</td>

+

<td>TUN (tunnel) {{!}} TAP (bridged); default: TUN (tunnel)</td>

<td>Virtual network device type.

<ul>

Line 95: Line 95:

</ul>

</td>

+

</tr>

+

<tr>

+

<td>Bridge</td>

+

<td>Bridge interface for TAP; default: br-lan</td>

+

<td>Assign a TAP interface to a bridge.</td>

</tr>

<tr>

Line 250: Line 255:

</tr>

<tr>

−

<td>TLS: Private key decryption password (optional)</td>

+

<td>TLS/Config File: Private key decryption password (optional)</td>

<td>string; default: none</td>

<td>A password used to decrypt the server's private key. Use only if server's .key file is encrypted with a password.</td>

Line 268: Line 273:

<li>Purple for Authentication: Static key</li>

<li>Blue for Authentication: Password</li>

+

<li>Brown for OpenVPN config from file</li>

</ul>

</li>

Line 744: Line 750:

<tr>

<td>Authentication method</td>

−

<td>Pre-shared key {{!}} X.509 {{!}} EAP {{!}} PKCS#12; default: Pre-shared key</td>

+

<td>Pre-shared key {{!}} X.509 {{!}} EAP {{!}} PKCS#12; default: Pre-shared key</td>

<td>Specify authentication method. Choose between Pre-shared key and X.509 certificates.</td>

</tr>

Line 2,091: Line 2,097:

WireGuard works by adding an interface which acts as a tunnel. To create one enter its name and click the Add button. This should add a new Wireguard instance and open a configuration window.

−

[[File:~~Networking_rutx_vpn_wireguard_v1~~.png|border|class=tlt-border]]

+

[[File:Networking_rutx_vpn_wireguard_v2.png|border|class=tlt-border]]

===General Instance Settings===

Line 2,099: Line 2,105:

Private keys and generate them, specify Port and IP addresses for communication.

−

[[File:~~Networking_rutx_vpn_wireguard_instance_general_v1~~.png|border|class=tlt-border]]

+

[[File:Networking_rutx_vpn_wireguard_instance_general_v3.png|border|class=tlt-border]]

Line 2,114: Line 2,120:

<tr>

<td>Private Key</td>

−

<td>string; default: ~~none~~</td>

+

<td>string; default: -</td>

<td>Private Key used in authentication.</td>

</tr>

Line 2,123: Line 2,129:

</tr>

<tr>

−

<td>Generate</td>

+

<td>Generate key pair</td>

<td>-(interactive button)</td>

<td>Click to generate Public Key and Private Key.</td>

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Listen Port</td>~~

−

~~<td>integer [0..65535]; default: none</td>~~

−

~~<td>Specify port to listen for incomming connections. It will be set to a random integer if left empty.</td>~~

</tr>

<tr>

Line 2,145: Line 2,146:

Advanced Settings section contains Metric and MTU configuration for this WireGuard interface.

−

[[File:~~Networking_rutos_vpn_wireguard_instance_advanced_v2~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_vpn_wireguard_instance_advanced_v3.png|border|class=tlt-border]]

Line 2,156: Line 2,157:

<td>Metric</td>

<td>positive integer; default: none</td>

−

<td>Specify metric for this tunnel interface. Lower number means higher priority.</td>

+

<td>Specify (Optional) metric for this tunnel interface. Lower number means higher priority.</td>

+

</tr>

+

<tr>

+

<td>Listen port</td>

+

<td>integer [1..65535]; default: 51820</td>

+

<td>Required. UDP port used for outgoing and incoming packets.</td>

</tr>

<tr>

−

<td>integer [~~1280~~..~~1420~~]; default: none</td>

+

<td>integer [68..9200]; default: none</td>

−

<td>Maximum Transmission Unit ~~for this~~ tunnel interface.</td>

+

<td>Maximum Transmission Unit of tunnel interface. Range [68 to 9200]. If not specified, the MTU is automatically determined by physical interface MTU value.</td>

</tr>

<tr>

<td>DNS servers</td>

−

<td>ip ~~| ips~~; default: none</td>

+

<td>ip; default: none</td>

<td>DNS server(s) for this Wireguard interface.</td>

</tr>

Line 2,174: Line 2,180:

----

−

The Peers section is used to create and configure all the peers for this interface.

+

The Peers section is used to create and configure all the peers for this interface. To create one enter its name and click the Add button.

−

To create one enter its name and click the Add button.

+

−

~~To configure it click the Edit [[File:Networking_rutx_manual_edit_button_v1.png]] button.~~

+

[[File:Networking_rutx_vpn_wireguard_instance_peer_v3.png|border|class=tlt-border]]

−

[[File:~~Networking_rutx_vpn_wireguard_instance_peer_v2~~.png|border|class=tlt-border]]

Line 2,185: Line 2,190:

In the General section of Peer instance you can configure basic information about the endpoint to allow communications.

−

[[File:~~Networking_rutos_vpn_wireguard_instance_peer_instance_general_v2~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_vpn_wireguard_instance_peer_instance_general_v3.png|border|class=tlt-border]]

Line 2,196: Line 2,201:

<td>Public Key</td>

<td>string; default: none</td>

−

<td>Endpoint~~'s Public Key~~.</td>

+

<td>Base64-encoded public key of peer.</td>

+

</tr>

+

<tr>

+

<td>Endpoint host</td>

+

<td>domain name {{!}} ip; default: none</td>

+

<td>Host of peer. Names are resolved prior to bringing up the interface.</td>

</tr>

<tr>

<td>Allowed IPs</td>

<td>ip; default: none</td>

−

<td>~~A single~~ IP ~~address or a list of them which are~~ allowed to ~~communicate with this~~ peer.</td>

+

<td>IP addresses and prefixes that this peer is allowed to use inside the tunnel. Usually the peer's tunnel IP addresses and the networks the peer routes through the tunnel.</td>

</tr>

<tr>

Line 2,211: Line 2,221:

<td>Route Allowed IPs</td>

<td>off {{!}} on; default: off</td>

−

<td>~~Enable to create~~ routes for ~~~~Allowed IPs~~~~ for this peer.</td>

+

<td>Create routes for Allowed IPs for this peer.</td>

</tr>

</table>

Line 2,222: Line 2,232:

settings such as its Description, Endpoint Host and Port, Preshared Key and other.

See more information below.

−

[[File:~~Networking_rutx_vpn_wireguard_instance_peer_instance_advanced_v1~~.png|border|class=tlt-border]]

+

[[File:Networking_rutx_vpn_wireguard_instance_peer_instance_advanced_v2.png|border|class=tlt-border]]

Line 2,231: Line 2,241:

</tr>

<tr>

−

<td>~~Description~~</td>

+

<td>Tunnel source</td>

−

<td>~~string~~; default: ~~none~~</td>

+

<td>Any {{!}} LAN {{!}} WAN {{!}} Mobile; default: Any</td>

−

<td>~~Description of~~ this ~~peer~~.</td>

+

<td>Interface to bind this instance to.</td>

</tr>

<tr>

Line 2,241: Line 2,251:

</tr>

<tr>

−

<td>~~Route Allowed IPs~~</td>

+

<td>Endpoint Port</td>

−

<td>~~off {{!}} on~~; default: ~~off~~</td>

+

<td>integer [1..65535]; default: none</td>

−

<td>~~Enable to create routes for Allowed IPs for this~~ peer.</td>

+

</tr>

<tr>

−

<td>~~Endpoint Host</td>~~

+

<td>Persistent Keep Alive</td>

−

~~<td>ip {{!}} url; default: none</td>~~

−

~~<td>IP or URL of Remote Endpoint.</td>~~

−

~~</tr>~~

−

~~<tr>~~

−

~~<td>Endpoint Port~~</td>

<td>integer [0..65535]; default: none</td>

−

<td>~~Specify port to connect to Remote Endpoint~~. ~~It will be set~~ to ~~51820 if left empty~~.</td>

+

<td>Seconds between keep alive messages. Default is 0 (disabled). Recommended value if this device is behind a NAT is 25. Range [0 to 65535].</td>

</tr>

<tr>

−

<td>~~Persistent Keep Alive~~</td>

+

<td>Routing table</td>

−

<td>~~integer [0..65535]~~; default: none</td>

+

<td>string; default: none</td>

−

<td>~~Specify time amount in seconds between Keep Alive messages. By default~~ this ~~option is 0 which means it is disabled~~. ~~Recommended value for a device behind NAT is 25~~.</td>

+

<td>Defines which routing table to use for this peer routes, not necessary to configure for most setups..</td>

</tr>

</table>

Line 2,409: Line 2,414:

<td>.key file; default: none</td>

<td>Generated RSA public key.</td>

+

</tr>

+

</table>

+

==Tailscale==

+

Tailscale is a straightforward peer-to-peer VPN service that utilizes the open-source WireGuard protocol.

+

Note: Tailscale is additional software that can be installed from the System → [[{{{name}}} Package Manager|Package Manager]] page.

+

[[File:Networking rutx vpn tailscale instance general v1.png|border|class=tlt-border]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Authentication method</td>

+

<td>Use login url | Use authentication key; default: Use login url</td>

+

<td>Selects method to authenticate your tailscale network.</td>

+

</tr>

+

<tr>

+

<td>Authentication key</td>

+

<td>string; default: none</td>

+

<td>Provide an auth key to automatically authenticate the node as your user account.</td>

+

</tr>

+

<tr>

+

<td>Enable</td>

+

<td>off | on; default: off</td>

+

<td>Turns tailscale service off or on.</td>

+

</tr>

+

<tr>

+

<td>Login server</td>

+

<td>full url; default: https://controlplane.tailscale.com</td>

+

<td>Provide the base URL of a control server. If you are using Headscale for your control server, use your Headscale instance’s URL.</td>

+

</tr>

+

<tr>

+

<td>Advertise routes</td>

+

<td>ipv4 or ipv6 with mask; default: none</td>

+

<td>Expose physical subnet routes to your entire Tailscale network.</td>

+

</tr>

+

<tr>

+

<td>Default route</td>

+

<td>on | off; default: off</td>

+

<td>Route traffic through another exit node.</td>

+

</tr>

+

<tr>

+

+

<td>ip; default: none</td>

+

<td>IP address of the exit node.</td>

+

</tr>

+

<tr>

+

<td>Accept routes</td>

+

<td>on | off; default: off</td>

+

<td>Accept subnet routes that other nodes advertise.</td>

+

</tr>

+

<tr>

+

+

<td>on | off; default: off</td>

+

<td>Offer to be an exit node for outbound internet traffic from the Tailscale network.</td>

</tr>

</table>

[[Category:{{{name}}} Services section]]

Lukas.Krasauskis

Administrators

43

edits

Changes

Template:Networking rutos manual vpn (view source)

Revision as of 11:20, 13 May 2024