Files
wireguard_webadmin/locale/de/LC_MESSAGES/django.mo
T

253 lines
56 KiB
Modelica
Raw Normal View History

2026-01-13 20:01:07 -03:00
Þ•¾ WüX%½Y%¢(Sº+m.ƒ|1ª7€«<,?]I@3§BFÛB/"D+RD'~D¦D
­D»DËDÒDãDçDøDE!E0E?EHE
_E
jExE‰|E
FF/FBF`F vF ‚F£F+©F¯ÕF2…G6¸G6ïG&H1DHvH{H‹H�H–H³HÐH
ÖHäHìH!üHI 2I?IPI;gI&£IÊIÑIàI%ÿI%J-J =JGJOJdJ tJ€J!œJ¾JÞJ$öJ%K$AK4fK2›K2ÎK"L$$LILZL iLuL�L!£LÅLÊL,ÜL M M1M4@MCuMJ¹MFNKNRN gNsN �N ™N"¥NÈN×N!èN
OO,O3OD<O �OŽO¦O²·OjPoP �P
‹P™P
ŸP
­P»PÒP+áP
QQ1Q
9Q DQNQ^Q:vQ±QÂQ
áQìQRDRW^RQR_SKhS´SÍSÝSúST+T:T;IT …T
‘TœT0±T
âTWíTEUÅUÚU%úU V>VMV`V"rV •V$V#ÛV ÿV WW&%W LXXX]XfX lX
yXA„X/ÆXöXþX/Y3>Y3rYW¦YcþYbZ eZUrZÈZ ÑZÝZ îZøZ [@[U[e[Fy[À[ß[î[,þ[
+\$6\&[\‚\  \Á\ Ê\ Ô\à\ñ\ù\# ]-]>]
G] R]^]g] m]
y]„]”]©]Â]ß]ó]^"^ <^I^[^`^h^n^r^%‰^¯^Ì^Bæ^$)_-N_|_’_
¢_ ­_·_¿_
Ã_ Ñ_Þ_ç_0ý_#.`,R``„`'—`,¿` ì`ø`5a Ma Za8ga' a'Èa'ðabHb gbsbIˆb#Òb/öb"&c^Ic2¨c4Ûc1d$Bdgd8ld3¥d Ùdæd&ød$eDe Ve`ehe weƒeœe«e5½eóe+üe (f4f=f
LfWf_fffvf‘f5¨fÞf;íf)g1g@gQgjg‰g�g¡·gYhkh {hˆhšh
´h Âh&Îhõh
úhiHiai ji6vi
­i¸i ¿i ÉiÕiòi
øij+#jOjmj~j“j§j®j ³jÀj=Öj„k‚™kDl»al&m@Dn)…n¼¯n:lo9§o%áo?peGp*­p®Øpx‡qr
s!s3s9s~VsÕsÞs<âs
t -t7t>tOt
dtrt‚tœtt%Ñt
÷t uu+u&GunuŠu“u
™u¤u·uËu Óu
Ýu¦ëu’v›v±vÆvÏvàvñvx w„w—w©w½wÎw;ãw=x]xlx{x›x»x(Ñxúxy&5y…\yây
æy
ôyzze2z˜zB¸zñû{Fí~u4‚:ª„Aå‡ï'�ì”R—�W˜Bõš�8›2ºœ6íœ.$�S�\�o��†� ›�§�Â�&Ú�žž4žIžiž
|žŠž‰�žŸ*ŸJŸ dŸ…Ÿ ŸŸ'¬ŸÔŸ>ÝŸ§ 8Ä Ký EI¡#�¡;³¡ï¡÷¡¢
¢ ¢(5¢
^¢i¢~¢†¢˜¢·¢
Í¢Û¢ñ¢H
£/V£†£�£%££%É£ï£÷£
¤¤¤7¤I¤$X¤$}¤"¢¤Ť'ã¤) ¥'5¥=]¥;›¥B×¥)¦*D¦o¦‚¦ ’¦ž¦»¦*Ц û¦§1§G§g§x§:ާQɧT¨Up¨ƨϨ
æ¨ô¨ ©©!#© E© O©[© {©‡©�© —©U£© ù©ª"ªØ<ª
« «;«O«c«l««”«§«?À«¬¬ /¬9¬ J¬T¬g¬H„¬ͬ2â¬
­%#­$I­Dn­v³­i*®‚”®b¯(z¯£¯/º¯%ê¯ °1°E°cY° ½°ɰа5á° ±]$±‘‚±!²#6²7Z²/’²²Ó²é²&³()³0R³.ƒ³²³ ³̳>å³$µ6µ;µDµ Jµ WµZdµB¿µ  @ :a@œ¶_ݶn=· ¬·¶·YË·%¸ -¸:¸
L¸Z¸ o¸Ty¸θá¸V¹1W¹‰¹š¹Aµ¹÷¹/º28º&kº-’ºÀºȺغîº
» »"»B» [»h»
{»‰»’»›»
«»¶»Ë»"æ»$ ¼.¼G¼`¼q¼‘¼¤¼¸¼ ½¼ǼϼÓ¼,ì¼$½>½R^½3±½:å½ ¾
:¾ E¾R¾
b¾ p¾z¾�¾Ÿ¾¨¾>½¾1ü¾2.¿a¿f¿2{¿6®¿å¿ô¿NÀbÀqÀD€À(ÅÀ*îÀ0ÁJÁIPÁšÁ©ÁM¾Á5 Â>BÂ/�Âc±Â?ÃCUÃ<™Ã7ÖÃÄFÄ;ZÄ–Ä¥Ä,¼Ä.éÄÅ /Å ;ÅEÅ
VÅdÅ�Å’Å8±Å
êÅ0õÅ &Æ 2Æ<Æ
QÆ \Æ
fÆtÆ!„ƦÆDÂÆÇBÇbÇkÇ~Ç’Ç#¯ÇÓÇ#ïÇÈÈÜÈõÈÉÉ-ÉLÉ^É1mÉ ŸÉ©É¹ÉWÊÉ
"Ê0Ê<@Ê}Ê�Ê
—Ê ¢Ê ¯ÊÐÊ×Ê$æÊ6 Ë&BËiË}˗˰˷Ë
¼ËÊËSäË’8̈ËÌQTͰ¦Í$WÎF|Ï;ÃÏÏÿÏHÏÐ:Ñ1SÑM…Ñ‹ÓÑ7_Ò¦—Òš>ÓòÙÓ ÌÔ.ÖÔÕ" Õ�.Õ ¼ÕÈÕUÌÕ"Ö5Ö
DÖRÖlÖˆÖ�Ö!¹Ö"ÛÖ$þÖ%#×
I×W×%j×)�×1º×-ì× Ø'Ø0Ø@Ø XØyØ �Ø�ؘ�Ø6Ù?ÙUÙtÙ}Ù�٥م¸Ù>ÚRÚfÚÚ’Ú?®ÚCîÚ2ÛEÛ!TÛ#vÛšÛ/µÛ#åÛ) Ü"3Ü�VÜôÜùÜ
ÝÝ).ÝsXÝ"ÌÝi÷¹�À´­2c/ô „Ø=)H S¤$&¾4}e\±u·‚jB?›:h ¬d •µ7æ+®fC¯ÐÁˆ#FÚ½9…œ![§N¬‡�Õxºë Lƒ'Vm›�´Y¹»! ‰˜†>Žö_W"ã%ç¼5>}rh‘ÝV3Ô4Ä^¨Þ©Å<\¿žk“�ƒ±P «yaÜý2Ò~Q+ևɨ@~:×Zí¯D»þ/s¤U<‹|цÛn$½(‘žê#£¥øŒè=t”rñD«zǦ—`™Ì®á lIoÓ8°yúJOŒE¼Hà¡’£–Kv—¸Gª]a’&)R6;¢{I*vLgbŸ"n6ªµ-€‰­qTòs•A�Q‹ù(RGfiÂMâkÀ„
˜{“üM¢Šoeû�C�-Í
`_.lW%…Owwb�ÈÊu ŸäzXAß,pT¦ÿî³ 1�S1gœm|xÆ,²§Šdð©J5p0j0³U]3^�õéKïF¾Ï*EBˆ”9–Î
‚óš¸qÙŽ.·ìN[@°¥7²™c¡Z8t?X'ºåšË;YP

<h5>Advanced VPN Firewall Configuration</h5>
<p>
This interface serves as a comprehensive tool for managing firewall rules, enabling users to implement advanced traffic policies between VPN peers and networks. It simplifies establishing firewall rules, packet filtering, and NAT configurations, allowing for precise control over network security. Users can define source and destination IP addresses, ports, protocols, and actions to tailor traffic flow, ensuring a secure and efficient networking environment.
</p>
<h5>Destination Selection</h5>
<p>
You have the option to apply this rule to a specific IP address or network and/or to multiple peers as the destination.<br><br>
Enabling the "Include peer networks" option will automatically include all Allowed IPs associated with each selected peer as the destination.<br><br>
Please note that selecting multiple peers with included networks on both the source and destination ends may result in a rapid increase in the number of firewall rules generated, depending on your configuration.<br><br>
The "Not Destination" option negates the selected destination IP, network, or peer(s).
</p>
<h5>Protocol and Port</h5>
<p>
Only the most commonly used protocols are listed here. If you require a specific protocol, please open an issue on GitHub.<br><br>
Selecting TCP+UDP will result in the duplication of generated rules.<br><br>
Ports can be specified as single numbers (e.g., 8080) or as ranges (e.g., 8001:8999).
</p>
<h5>Source Selection</h5>
<p>
You have the option to apply this rule to a specific IP address or network and/or to multiple peers.<br><br>
Enabling the "Include peer networks" option will automatically include all Allowed IPs associated with each selected peer.<br><br>
Please note that selecting multiple peers with included networks on both the source and destination ends may result in a rapid increase in the number of firewall rules generated, depending on your configuration.<br><br>
The "Not Source" option negates the selected source IP, network, or peer(s).
</p>
<h5>Default Ports</h5>
<p>The default <code>docker-compose.yml</code> file specifies the <b>TCP</b> port range <b>8080-8089</b>. If you wish to change the port forwarding to a different range, you must manually edit the <code>docker-compose.yml</code> file and rerun the Docker Compose step outlined in the <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">deployment instructions</a>.</p>
2025-12-29 18:30:39 -03:00
<h5>Destination Type: Peer</h5>
<p>Port redirection will prioritize the first Peer IP address assigned a priority of Zero.</p>
<h5>Destination Type: IP Address</h5>
<p>Port forwarding rules will redirect to the specified IP address. Remember to allocate the IP address or network to a Peer.</p>
<h5>Adding a Forward Rule</h5>
<p>Automatically generates a forwarding rule to accommodate stricter firewall settings.</p>
<h5>Masquerade Source</h5>
<p>This serves as a temporary solution when a peer does not use the VPN as its default gateway. It's important to note that this configuration is not recommended, as it alters the source address of all connections to match the IP address of the WireGuard instance.</p>
<h4>User Levels</h4>
<h5>Debugging Analyst</h5>
<p>Access to basic system information and logs for troubleshooting. No access to modify settings or view sensitive data such as peer keys.</p>
<h5>View Only</h5>
<p>Full view access, including peer keys and configuration files. Cannot modify any settings or configurations.</p>
<h5>Peer Manager</h5>
<p>Permissions to add, edit, and remove peers and IP addresses. Does not include access to modify WireGuard instance configurations or higher-level settings.</p>
2025-12-29 18:30:39 -03:00
<h5>Wireguard Manager</h5>
<p>Authority to add, edit, and remove configurations of WireGuard instances.</p>
<h5>Administrator</h5>
<p>Full access across the system. Can view and modify all settings, configurations and manage users. </p>
<br>
<h4>Peer Groups</h4>
<p>Select which peer groups this user can access. If no peer groups are selected, the user will have access to all peers.</p>
<h4>Console</h4>
<p>Enable or disable web console access for this user.</p>
<h4>Enhanced Filter</h4>
<p>This option filters the API status response to include only peers that the user has access to. Depending on the size of your environment, enabling this option may impact performance. To mitigate this, consider increasing the "Web Refresh Interval" to reduce the number of requests.</p>
2026-01-13 20:01:07 -03:00
<h5>Cluster Mode</h5>
<p>Configure how the cluster operates and synchronizes configurations between nodes.</p>
<h5>Sync Intervals</h5>
<p>Configure how frequently statistics and cache data are synchronized between cluster nodes.</p>
2026-01-13 20:01:07 -03:00
<h5>Restart Mode</h5>
<p>Choose whether WireGuard services should be automatically restarted when configurations change, or if manual intervention is required.</p>
<h5>Worker Display</h5>
<p>Select how workers should be identified in the interface - by name, server address, location, or a combination.</p>
<h5>Peers</h5>
<p>Select which peers can be managed by users with this peer group.</p>
<h5>WireGuard Instances</h5>
<p>All peers in this WireGuard instance can be managed by users with this peer group, including adding or removing peers.</p>
<h5>Worker Configuration</h5>
<p>Configure a cluster worker node that will synchronize with this primary instance.</p>
<h5>Name</h5>
<p>A unique name to identify this worker.</p>
<h5>IP Address</h5>
<p>The IP address of the worker node. Leave empty if IP lock is disabled.</p>
<h5>IP Lock</h5>
<p>When enabled, the worker can only connect from the specified IP address.</p>
<h5>Location Information</h5>
<p>Optional location details for this worker (country, city, hostname).</p>
(Share this password via a separate secure channel)<h2>Welcome to Your VPN Setup</h2>
<p>Begin by downloading the WireGuard app for your device using one of the links below.</p>
<p>Once installed, you can either <strong>scan the QR code</strong> or <strong>download the configuration file</strong> to quickly import your settings and start using your secure VPN connection.</p>A peer can have only one IP with priority zero.A peer group with that name already exists.A worker with that name already exists.ACCEPTAccess DeniedAccess PasswordActionAction Required!AddAdd Client routeAdd Filter ListAdd Forward Rule (allow)Add IP AddressAdd Peer GroupAdd UserAdd WireGuard InstanceAdd WorkerAdministratorAllAll DNS queries will be forwarded to the primary resolver. If the primary resolver is not available, the secondary resolver will be used.Allow ForwardAllow Instance to InstanceAllow Peer to PeerAllow traffic from VPN to WANAllowed IP or NetworkAllowed IPsAllowedIPs at Peer section of wgApplyAre you sure you want to create a new peer?At least one address does not appear in the wg show command output, which may indicate that another peer is using an overlapping IP or that the configuration file is outdated.At this stage, only core features are implemented:Automatic Rule: Firewall Settings Instance to InstanceAutomatic Rule: Firewall Settings Peer to Peer trafficAutomatic Rule: Port forward.Automatic rule: Allow established/related trafficBackChange LanguageCityClearClient Routing ConfigurationClipboard API not supported.CloseClose QR CodeClusterCluster EnabledCluster Feature – Testing PhaseCluster InformationCluster ModeCluster SettingsCluster is not enabledCluster mode requires WireGuard status cache to be enabled.Cluster settings updated successfully.ConfigConfig VersionConfiguration sync in progressConfiguration synchronization serviceConsoleConsole EnabledCopy TextCountryCreate Firewall RuleCreate InstanceCreate PeerCreate Port forwarding RuleCreate a new Peer for instance wgCreate a new WireGuard InstanceDNS Filter List DetailsDNS Filter List deleted successfullyDNS Filter List disabled successfullyDNS Filter List enabled successfullyDNS Filter List not deleted | Filter List is enabledDNS Filter List not deleted | Invalid confirmationDNS Filter List not enabled | No valid hosts foundDNS Filter List saved successfullyDNS Filter List updated successfullyDNS Filter ListsDNS ForwardersDNS VersionDNS container test scriptDNS rules mirroringDNS settings applied successfullyDROPDebugging AnalystDefault DNS Filter List created successfullyDefault Forward PolicyDefault PasswordDefault PolicyDefault password must be at least 6 characters long.Default password must be provided when random password is disabled.Default password must not be contained in any message template. Found at: Default password must not be provided when random password is enabled.DeleteDelete ConfigurationDelete PeerDelete WireGuard InstanceDescriptionDestinationDestination Hostname or IP AddressDestination IPDestination PeerDestination Peer Include NetworksDestination PortDestination TypeDigitsDisabledDisabling WireGuard on the master server is currently not supported.Display NameDisplay automatic rulesDownload ButtonsDownload the WireGuard app for your device using one of the links below. After installation, you can scan the QR code or download the configuration file to import on your device.EditEdit Peer Group: Edit UserEdit Worker: EmailEmail EnabledEmail MessageEmail Message TemplateEmail SettingsEmail Settings|Settings saved successfully.Email SubjectEmail or phone numberEnabledEncryptionEndpointsEnhanced FilterEnhanced Filter EnabledEnhanced filter is enabled. This command is not available.Enter Allowed IPEnter Email or WhatsApp NumberEnter NameError closing invite:Error creating invite.Error creating peer|No available IP address found for peer creation.Error deleting Firewall rule|Confirmation did not match. Firewall rule was not deleted.Error deleting IP address|Invalid confirmation message. Type "delete" to confirm.Error deleting Port Forward rule|Confirmation did not match. Port Forward rule wa
You're invited to join our secure WireGuard VPN network. Please click the link below to access your personalized VPN configuration:
{invite_url}
Note: This invitation link will expire in {expire_minutes} minutes. If you need a new link after expiration, please request another invite.Hide extrasHostHostnameHostsI UnderstandIP AddressIP Address cannot be used without selecting a WireGuard instance.IP Address is required when IP Lock is enabled.IP LockIP Lock EnabledIP address added|IP address added successfully.IP address deleted|IP address deleted successfully.IP address updated|IP address updated successfully.IP lock is enabled, but the worker is attempting to access from a different IP address.If you find any issues with the translation or would like to request a new language, please open anInIn InterfaceIn the current version, peer state information is not collected by the master server.InstanceInstance IDInstance TrafficInterfaceInternal IP AddressInvalidInvalid Destination. Either Peer or IP Address must be informed.Invalid commandInvalid config fileInvalid confirmation|Please confirm deletion of WireGuard instance: wgInvalid hostname or IP AddressInvalid targetInvite SettingsInvite Settings|Settings saved successfully.Invite URLInvite URL must end with '/invite/'.Invite URL must start with 'https://'.Invite data is not available.Invite text copied to clipboard.LanguageLast SeenLast UpdateLatest HandshakeLettersLetters, DigitsLetters, Digits, Special CharactersList Peer GroupsList URLList UsersListen PortLocationLoginLogin againMASQUERADEMain ip addressManage Firewall RuleManage Firewall SettingsManage IP address or NetworkManage Port ForwardManage client routeMasquerade SourceMasquerade traffic from VPN to WANMemory usageMessage templatesNameNetmaskNeverNewNew WireGuard InstanceNext priority features (coming soon):No WireGuard Instances FoundNo active VPN invitationsNo interfaces found|No WireGuard interfaces were found to process.No invite data available to refresh.No traffic history, please wait a few minutesNo workers configuredNot DestinationNot SourceNot StateNot setOutOut InterfacePacket StatePasswordPassword ConfirmationPassword confirmation is required for new users.Password is required for new users.Password must be at least 8 characters long.PeerPeer ConfigurationPeer Group deleted|Peer Group deleted: Peer Group not deleted|Invalid confirmation.Peer GroupsPeer IP Addresses and networksPeer List Refresh Interval must be at least 5 secondsPeer ManagerPeer TrafficPeer and IP Address cannot be selected at the same time.Peer created|Peer created successfully.Peer deleted|Peer deleted successfully.Peer updated|Peer updated successfully.PeersPending Changes|There are pending DNS changes that have not been appliedPermissionsPersistent KeepalivePlease contact your system administrator if you believe this is an error.Please enter a valid email address.Please enter a valid phone number for WhatsApp.Please provide a valid IP address.Please report worker_config_version, worker_dns_version and worker_version in the API request.Please type 'delete' to remove this firewall rule.Please type \"delete\" to remove peer configuration.Please type \"delete\" to remove this IP address.Please type the username to proceed.PortPort %s is already in use by another WireGuard instance.Port 8000 (tcp) is reserved for wireguard-webadmin.Port ForwardPort Forward ListPort Forward rule deleted successfullyPort Forward rule saved successfullyPort is required.Post DownPost UpPre-Shared KeyPrimary DNSPrimary Enable WireGuardPrimary ServerPrimary WireGuardPrimary node mirroring (WireGuard and firewall rules)PriorityPriority must be greater than or equal to 1Private KeyProtocolPublic AddressPublic KeyQR CodeREJECTRandom PasswordRandom Password ComplexityRandom Password LengthRandom password length must be at least 6 characters.Refresh InviteReject traffic to private networks exiting on WAN interfaceRelatedReload EnabledReload WireGuardReload Wireguard serviceRemove VPN invitation for peerRequired User LevelReset firewall to defaultReseting
Report-Msgid-Bugs-To:
PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE
Last-Translator: FULL NAME <EMAIL@ADDRESS>
Language-Team: LANGUAGE <LL@li.org>
Language:
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=2; plural=(n != 1);
<h5>Erweiterte VPN‑Firewall‑Konfiguration</h5>
<p>
Diese Oberfläche ist ein umfassendes Werkzeug zur Verwaltung von Firewall‑Regeln. Sie erlaubt es, komplexe Verkehrsrichtlinien zwischen VPN‑Peers und ‑Netzen umzusetzen, vereinfacht die Einrichtung von Regeln, Paketfiltern und NAT‑Konfigurationen und ermÃglicht so eine präzise Kontrolle der Netzwerksicherheit. Nutzer kÃnnen Quell‑ und Ziel‑IP‑Adressen, Ports, Protokolle und Aktionen definieren, um den Datenfluss genau anzupassen und eine sichere, effiziente Umgebung zu gewährleisten.
</p>
<h5>Zielauswahl</h5>
<p>
Diese Regel kann auf eine bestimmte IP‑Adresse bzw. ein Netz und/oder auf mehrere Peers als Ziel angewendet werden.<br><br>
Wenn Sie "Peer‑Netze einbeziehen" aktivieren, werden automatisch alle Allowed‑IPs der ausgewählten Peers als Ziel einbezogen.<br><br>
Beachten Sie, dass bei Auswahl mehrerer Peers – sowohl für Quelle als auch Ziel – die Anzahl der generierten Regeln stark ansteigen kann.<br><br>
Die Option "Nicht Ziel" verneint die gewählte Ziel‑IP, das Netz oder die Peers.
</p>
<h5>Protokoll und Port</h5>
<p>
Hier sind nur die gängigsten Protokolle aufgeführt. BenÃtigen Sie ein anderes Protokoll, erÃffnen Sie bitte ein Issue auf GitHub.<br><br>
Die Auswahl "TCP+UDP" erzeugt für jedes Protokoll eine eigene Regel.<br><br>
Ports kÃnnen als Einzelwert (z.&nbsp;B. 8080) oder als Bereich (z.&nbsp;B. 8001:8999) angegeben werden.
</p>
<h5>Quellenauswahl</h5>
<p>
Diese Regel kann auf eine bestimmte IP‑Adresse bzw. ein Netz und/oder auf mehrere Peers angewendet werden.<br><br>
Wenn Sie "Peer‑Netze einbeziehen" aktivieren, werden automatisch alle Allowed‑IPs der ausgewählten Peers einbezogen.<br><br>
Beachten Sie, dass bei Auswahl mehrerer Peers – sowohl für Quelle als auch Ziel – die Anzahl der generierten Regeln stark ansteigen kann.<br><br>
Die Option "Nicht Quelle" verneint die gewählte Quell‑IP, das Netz oder die Peers.
</p>
<h5>Standard‑Ports</h5>
<p>Die mitgelieferte <code>docker-compose.yml</code> definiert den <b>TCP</b>‑Portbereich <b>8080‑8089</b>. Soll das Port‑Forwarding einen anderen Bereich verwenden, bearbeiten Sie die Datei manuell und wiederholen Sie den in den <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">Deploy‑Anweisungen</a> beschriebenen Docker‑Compose‑Schritt.</p>
2025-12-29 18:30:39 -03:00
<h5>Zieltyp Peer</h5>
<p>Die Weiterleitung verwendet vorrangig die erste Peer‑IP mit Priorität 0.</p>
<h5>Zieltyp IP‑Adresse</h5>
<p>Weiterleitungsregeln leiten an die angegebene IP-Adresse weiter. Denken Sie daran, die Adresse bzw. das Netz einem Peer zuzuweisen.</p>
<h5>Forward‑Regel hinzufügen</h5>
<p>Erzeugt automatisch eine Forward‑Regel für strengere Firewall‑Konfigurationen.</p>
<h5>Quelle maskieren</h5>
<p>Dient als ÜbergangslÃsung, wenn ein Peer die VPN‑Verbindung nicht als Standard‑Gateway nutzt. Nicht empfohlen, da die Quelladresse sämtlicher Verbindungen auf die IP der WireGuard‑Instanz umgeschrieben wird.</p>
<h4>Benutzerstufen</h4>
<h5>Debug‑Analyst</h5>
<p>Zugriff auf grundlegende Systeminformationen und Protokolle zur Fehlerbehebung. Kein Zugriff zum Ändern von Einstellungen oder zum Einsehen sensibler Daten wie Peer‑Schlüssel.</p>
<h5>Nur Ansicht</h5>
<p>Vollständiger Lesezugriff, einschließlich Peer‑Schlüssel und Konfigurationsdateien. Es kÃnnen jedoch keine Einstellungen oder Konfigurationen geändert werden.</p>
<h5>Peer‑Manager</h5>
<p>Berechtigung zum Hinzufügen, Bearbeiten und Entfernen von Peers und IP‑Adressen. Kein Zugriff auf die Konfiguration von WireGuard‑Instanzen oder hÃhere Systemeinstellungen.</p>
2025-12-29 18:30:39 -03:00
<h5>WireGuard‑Manager</h5>
<p>Befugnis zum Hinzufügen, Bearbeiten und Entfernen der Konfigurationen von WireGuard‑Instanzen.</p>
<h5>Administrator</h5>
<p>Vollzugriff auf das gesamte System. Kann alle Einstellungen und Konfigurationen anzeigen und ändern sowie Benutzer verwalten.</p>
<br>
<h4>Peer‑Gruppen</h4>
<p>Wählen Sie aus, auf welche Peer‑Gruppen dieser Benutzer zugreifen darf. Wenn keine Gruppe ausgewählt ist, hat der Benutzer Zugriff auf alle Peers.</p>
<h4>Konsole</h4>
<p>Aktivieren oder deaktivieren Sie den Zugriff auf die Web‑Konsole für diesen Benutzer.</p>
<h4>Erweiterter Filter</h4>
<p>Diese Option filtert die API‑Statusantwort, sodass nur Peers angezeigt werden, auf die der Benutzer Zugriff hat. Je nach Größe Ihrer Umgebung kann das Aktivieren dieser Option die Leistung beeinträchtigen. Um dem entgegenzuwirken, erhÃhen Sie gegebenenfalls das „Web‑Aktualisierungsintervall“, um die Anzahl der Anfragen zu reduzieren.</p>
2026-01-13 20:01:07 -03:00
<h5>Cluster-Modus</h5>
<p>Konfigurieren Sie, wie der Cluster arbeitet und Konfigurationen zwischen den Knoten synchronisiert.</p>
<h5>Synchronisationsintervalle</h5>
<p>Konfigurieren Sie, wie oft Statistiken und Cache-Daten zwischen den Cluster-Knoten synchronisiert werden.</p>
2026-01-13 20:01:07 -03:00