gluon/docs/_build/gettext/features/wired-mesh.pot
Felix Kaechele 3b2f780e0a docs: add sphinx-intl workflow for translations
Add a update-po and %.po rule to the Makefile.
We define "de" as a language to start with.

To add languages just append them to the update-po rule in the Makefile.

We do want to keep the _build/gettext folder as Weblate uses this to
enable new translations.

Signed-off-by: Felix Kaechele <felix@kaechele.ca>
2019-04-20 19:41:42 -04:00

119 lines
5.2 KiB
Plaintext

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-2019, Project Gluon
# This file is distributed under the same license as the Gluon package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Gluon 2018.2+\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-04-20 16:46-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../features/wired-mesh.rst:2
# c86683753a6e448585bcb7099eb18989
msgid "Wired mesh (Mesh-on-WAN/LAN)"
msgstr ""
#: ../../features/wired-mesh.rst:4
# bbd9b082c31b41d2b5878b69266695f7
msgid "In addition to meshing over WLAN and VPN, it is also possible to configure wired meshing over the LAN or WAN ports. This allows nodes to be connected directly or over wireless bridges."
msgstr ""
#: ../../features/wired-mesh.rst:8
# 9d0106b6051d4f3d934c3d57eb96adb7
msgid "Mesh-on-WAN can be enabled in addition to the mesh VPN, so multiple nodes in the same local network that is used as VPN uplink can also mesh directly. Enabling Mesh-on-WAN should be avoided if the local network is also bridged with a WLAN access point, as meshing over batman-adv causes large amounts of multicast traffic, which will take up a lot of airtime."
msgstr ""
#: ../../features/wired-mesh.rst:14
# 25a72c46823040139ce2d18a243ee223
msgid "Enabling Mesh-on-LAN replaces the normal \"client network\" function of the LAN ports, as client network ports may never be connected (so care must be taken to always enable Mesh-on-LAN before connecting two nodes' LAN ports)."
msgstr ""
#: ../../features/wired-mesh.rst:19
# c264ae5f41cb4580852f61c041d5e8fc
msgid "Wired mesh encapsulation"
msgstr ""
#: ../../features/wired-mesh.rst:21
# 60490854c8a247d4be4ff16acc3ea329
msgid "Since version 2018.1, Gluon supports encapsulating wired mesh traffic in `VXLAN <https://en.wikipedia.org/wiki/Virtual_Extensible_LAN>`_, a new standard with use cases similar to VLANs, but a much greater ID space of 24bit; in addition, VXLAN packets pass through VLAN-aware switches without any special configuration."
msgstr ""
#: ../../features/wired-mesh.rst:26
# 183a595c631848018f9cea6b90a4040c
msgid "Encapsulating mesh traffic has two advantages:"
msgstr ""
#: ../../features/wired-mesh.rst:28
# fb4c185b98234d0b8ee7d9184d0a3de4
msgid "By using a different VXLAN ID for each site and mesh domain, accidental wired mesh connections between nodes of different domains will be prevented. This has special importance when nodes migrate between domains automatically, as currently possible through different site-specific packages."
msgstr ""
#: ../../features/wired-mesh.rst:32
# 604b8f384bf943a1bc5a4aa216685a2e
msgid "While batman-adv traffic does not interact with non-mesh traffic in the same wired network in any way (so Gluon nodes can mesh over existing wired networks), this is not the case for layer 3 mesh protocols like Babel. Encapsulating the traffic allows to distinguish mesh traffic from unrelated packets."
msgstr ""
#: ../../features/wired-mesh.rst:37
# e2da919e4cbc4c708dcc14948c146277
msgid "As enabling VXLAN encapsulation will prevent wired mesh communication with old nodes that do not support VXLAN yet, VXLANs can be enabled per-domain using the site configuration setting *mesh.vxlan*. VXLAN is enabled by default in multidomain setups; in single-domain site configurations, the *mesh.vxlan* setting is mandatory. We recommend to enable VXLAN encapsulation in all new sites and domains."
msgstr ""
#: ../../features/wired-mesh.rst:43
# a3fcc44a58e1433c98297262ad0f69ed
msgid "Non-encapsulated (\"legacy\") wired meshing will be removed in a future Gluon release. We cannot give a concrete timeframe for the removal yet; a missing prerequisite is the implementation of a robust migration path for existing deployments."
msgstr ""
#: ../../features/wired-mesh.rst:48
# 1aae75cb77fa4b83a237e65edbef3c0a
msgid "Configuration"
msgstr ""
#: ../../features/wired-mesh.rst:50
# 6739448b9cf5461bb26fe725f0529197
msgid "Both Mesh-on-WAN and Mesh-on-LAN can be configured on the \"Network\" page of the *Advanced settings* (if the package ``gluon-web-network`` is installed)."
msgstr ""
#: ../../features/wired-mesh.rst:53
# 68a3c9a77d324b04ad1ef2a55a0d6b99
msgid "It is also possible to enable Mesh-on-WAN and Mesh-on-LAN by default by adding ``mesh_on_wan = true`` and ``mesh_on_lan = true`` to ``site.conf``."
msgstr ""
#: ../../features/wired-mesh.rst:57
# 34f784f21b634d6e9fe543316785afaa
msgid "Commandline"
msgstr ""
#: ../../features/wired-mesh.rst:59
# cf3051a72d0d43779cc40ce93cd03db4
msgid "Enable Mesh-on-WAN::"
msgstr ""
#: ../../features/wired-mesh.rst:64
# c7d46d86ffd3418aadb355ccbb00c040
msgid "Disable Mesh-on-WAN::"
msgstr ""
#: ../../features/wired-mesh.rst:69
# 57a3b5abe8304ebab59a0f9fcb34870f
msgid "Enable Mesh-on-LAN::"
msgstr ""
#: ../../features/wired-mesh.rst:77
# 05fe376ab2fd4bc3ad8cde6b101fe24a
msgid "Disable Mesh-on-LAN::"
msgstr ""
#: ../../features/wired-mesh.rst:85
# dc3157628b1443eca994542c4520270e
msgid "Please note that this configuration has changed in Gluon 2016.1. Using the old commands on 2016.1 and later will break the corresponding options in the *Advanced settings*."
msgstr ""