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

367 lines
68 KiB
Modelica
Raw Normal View History

2026-02-03 11:47:11 -03:00
Þ•äϬ!è,½é,¢§/SJ3mž5 9Þ%:~<‚ƒ<w=~=3œ>ƒÐ?ªTE€ÿJ€MI�N]çTOEW3•WFÉW/Y+@Y'lY”Y
›Y©Y¹YÀYÈYÏYÓYäYôY
Z Z)Z 8ZDZYZkZtZ
‹Z–Z
žZ¬Z‰°Z
:[H[c[|[�[­[ Ã[ Ï['ð[Q\j\p\…\+”\7À\3ø\¯,]@Ü]2^6P^6‡^¾^1Ü^_ _
_._L_qS_Å_Õ_Ú_à_ï_ `
` `(`F`!V`x` Œ`™`ª`;Á`&ý`$a+a:a%YaaŽa–a ¦a°a¸aÍa Ýaéabb=b
VbAdb¦b¸b$Ðb%õb$c4@c2uc2¨c"Ûc$þc#d4d CdOdid!}dŸd¤dd,¾dëdee"e<e4MeC‚eJÆeFfXf _fkfƒf˜f ²f ¾f"Êfífüf!
g/g@gQgXgag ~g‹g£g²´ggh
lhzh ‰h “h�h¯h¾hÖhìh ÿh
ii
i
+i9iPi+_i
‹i™i¯i
·iÂiÊi ÓiÝiòij:jUjfj…j›jD²jW÷jQOk_¡kKlMlflvl“l¯lÄlÓl;âl m
*m5m0Jm
{mW†mÞm^nsn%“n¹n×nænùn" o .o$Oo#to˜o Ÿo¬o´o&Åo ìpøpýpq q
qA$q/fq–qžq/®q3Þq3rWFrcžrs sss $s0s AsKsZsnss@‡sÈsØsFìs3tORt¢t±t,Át
ît$ùt&uEucu uu–u›u ¤u ®u1ºuìuýuv#v9vJv
Sv ^vjvsv yv
…v�v vµvÎvëvÿvw"%wHw ewrw„w‹w�w˜wžw¢w¹wÖwôwBx$Qx2vx©xÅx-Þx y"y
2y =yGy$Oyty
xy †y“yœy0²y#ãy,z4z9zLz'az,‰z zÂz5áz { ${81{'j{'’{'º{â{Hè{ 1|=|IR|#œ|/À|"ð|^}2r}4¥}1Ú}$ ~1~86~3o~ £~°~&Â~$é~  /;Tc5u«+´ à ìù€
€€$€+€;€V€5m€£€;²€î€ö€��/�N�b�¡|�‚0‚ @‚M‚_‚
y‚„‚$š‚%¿‚å‚#û‚ƒ30ƒ2dƒ—ƒ
©ƒ ·ƒ&Ãêƒóƒ&øƒ$„D„V„ m„
w„.…„´„»„HË„… …6)…
`…k… r… |…ˆ… ¥…
¯…º…
À…Ë…+ë…†5†F†c†j†
q††ކ “† †=¶†„ô†‚y‡Dü‡»Aˆ&ýˆ@$Š)eŠ9�ŠIÉŠ:‹9N‹%ˆ‹?®‹eî‹*TŒ®Œx.�§�
­Ž¸Ž#ÁŽ!åŽ�!�8�
>�L�i�r�z��<ƒ�
À�Î� Õ�ß�æ�÷� ��6�P�k�%s�
™� ¤�±�Í�&é�‘,‘5‘
;‘F‘Y‘m‘ u‘
‘¦�‘4’J’ _’i’r’ƒ’”’®’Á’Õ’ç’û’ “;!“=]“›“ª“¹“Ù“ù“(”8”S”&s”…š” •
$•
2025-04-16 14:34:46 -03:00
2•@•R•ep•Ö•Aö• 8— Eš•æ�€| &ý£ù$¥†§–¥§z<¨1·¨Sé©=«�S±Ùã·R½ºÀ¼°ÑÂQ‚Å5ÔÅp
Æ2{Ç+®Ç#ÚÇþÇ
ÈÈ#È*È2È 8ÈBÈQÈ%kÈ ‘ȞȲÈËÈÜÈûÈÉ!.ÉPÉ aÉ
kÉyÉ€ÉÊ#Ê%<ÊbÊ#€Ê¤ÊÃÊ ÒÊ2óÊa&ˈË�Ë­Ë0¼Ë6íË=$̸bÌPÍ?lÍ6¬ÍCãÍ+'Î=SΑΘάÎ'½ÎåÎ�îÎ~Ï�ϔϛÏ3±ÏåÏìÏûÏ'Ð+Ð%>ÐdÐ}Ð�ШÐKÆÐ3ÑFÑUÑ.oÑ-žÑÌÑàÑèÑ ûÑÒÒ&Ò
7Ò&BÒiÒ*…Ò°ÒÄÒSÙÒ-Ó"CÓ,fÓ/“Ó-ÃÓHñÓ?:ÔGzÔ(ÂÔ-ëÔÕ1Õ@Õ!OÕqÕ,�Õ¼ÕÅÕ×Õ1éÕÖ
7ÖEÖWÖpÖ/ÖN¯ÖSþÖQR×¤× ¬×¹×××õ× Ø!Ø)Ø
DØRØ bØƒØ”Ø¤Ø ­Ø'ºØâØõØÙÎ%ÙôÙûÙ
Ú
Ú ,Ú8ÚPÚdÚ‚ÚŸÚ¼ÚÌÚÜÚâÚóÚÛ!Û<:ÛwÛˆÛ
¥Û °Û½ÛÍÛÞÛïÛÜ!ÜH>܇Ü%œÜÂÜÜÜOóÜcCÝa§Ý‚ ÞYŒÞæÞß-ß Dßeß}ß
�ß;›ß ×ß äßîß9à <àlFà™³àMá!fá3ˆá/¼áìáÿáâ'6â#^â.‚â ±â ÒâÞâòâøâS
ãaä päzä
Ί
—ä ¢äL¯äDüäAåPå<jå:§å<âådæ`„æåæíæç
ç
ç ç 7çAçUç jç wç@�çÂç#ÔçVøçOèYièÃèÕè>ðè/é2Dé2wé*ªéÕé8éé"ê)ê0êGê=]ê›ê­ê´ê&Åêìêëë+ë
1ë?ëGëYëbëyë%•ë»ë!Úëüëì#&ì&Jìqì�ì
•ì£ì¨ì¹ì¿ìÄì*áì+ í8íWVí6®í<åí("î(Kî<tî±î Ëî Øî äî
ðî%þî$ï+ï?ïPïVï<mï+ªï'Öïþïðð33ð6gðžð®ðNÌðñ,ñ?=ñ,}ñ*ªñ,ÕñòQò Zòfòa{ò0ÝòAó,Póe}ó?ãóC#ô<gô5¤ôÚô:àô8õTõ lõ6�õ2Äõ÷õö
'ö5öSöfö>zö
¹ö&Äö
ëöùö ÷÷%÷
4÷?÷G÷ X÷y÷2•÷È÷?Ú÷ ø&ø<øSø sø”ø!¯ø¸ÑøŠù�ù²ùÌùâù úú**ú.Uú„ú!œú¾ú?Óú<ûPûfû{û$‹û°û¸û,¿û(ìûü+ü IüSü6cüšü­üPÅüý
&ý>4ýsýŒý “ý ý¯ýÏýÞýîý
õý#þ4'þ\þ|þ4›þÐþ×þßþîþýþÿÿR1ÿ‘„ÿŠJ¡ÛìYÈ7"7ZA’>Ô<9PŠP©sú(n·—…OÕî ,(?h  ¦$»à ïü P V  h t  ƒ � § À !Ú !ü  
 ?
-I
2026-01-27 15:22:12 -03:00
w
ˆ
!�
'¿
4ç
) F  O Y j #‡ « ³ 
Ê ºØ “ ¯  Î Û ä ø 
,
D
]
r
Ž
¢
;½
9ù
3G\#zž2»)î%#>�bò ø!%9l_&Ì]5eMÂ…l#ÔÿüÈù¬ î�Kµ 5ª2Í£’Ì‹©¿Àï ê@0*7øj� rhg<”ßHpü|
Ç9‡ÀþkÓI
ä(ðOmi§ìE«:áQ‘yÒ�8�Âà ¡_QsŸFP h±Šw¸B ·#CuA;0Ü¢Mq\)­ÜXcðy öK÷�^ÕËFÉt½Û
V¯—G¡ùbv¯µCØÔ™cxλúç 8Í=¾o•Æ~3•‹zýZßó¿’kô_
.-€³ò1wJ¹†UX‰˜ƒ%E™r仪!+çÑ!°„L I�ÇК" |R€t,/í¾bŸúTÈ7´´è«a¼Ý:¼/Ù[ÞЍ^�àOÞ…iÁÊ9÷Ž‚Dn¥ž{®W¨2ݧn“åòà%‘fï¥Lœ‰j=m6·Ï�T$Zæ¸)¦Ò4ë{×þÖ}нP‡ÿd¬-?ÆBÅ<†'éýÄÏ~ê.›â\Õš'ºe©Œ]vûA¤ã˜Ù"áqÛ ¢zfN&Ö±Ø�¹H>$û
õŽÁãlxSYpYíé`S4,ƒNëˆ?3Ê&ºâ[ž–öÓ®}Ú
ÉUÌoÄîœG�›Ñ²*@£D³ˆÎg„ñ—sì×óø1­°ôåa;JV²dR“+>6‚ÚËæ–`ÅuÔŒñ¦è¤(Wõ
<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>
2025-04-16 11:31:08 -03:00
<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>
2025-04-15 12:16:50 -03:00
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>
DNS servers pushed to peers.
<br>
Using the internal IP as primary DNS enables internal name resolution
and DNS filtering.
Enforces routing rules defined by routing templates using firewall rules.
<br>
Peers with a default route (0.0.0.0/0) are not restricted.
<br><br>
Note: depending on the number of routes and peers, this option may generate
a large number of firewall rules.
Internal IP address and netmask used by the WireGuard interface.
2025-12-29 18:30:39 -03:00
Interval used to refresh WireGuard status information in the web UI.
Optional name used only for display in the web interface.
Public hostname or IP address and UDP port used by peers to connect.
<br>
The <b>listen port</b> must be exposed and mapped in your Docker compose (YAML) file.
WireGuard private and public keys for this interface.
<br>
The private key must remain secret.
2025-04-15 12:16:50 -03:00
Changing it requires updating all peer configurations.
<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>
<h5>Destination Type: Peer</h5>
<p>Port redirection will prioritize the first Peer IP address assigned a priority of Zero.</p>
2025-12-29 18:30:39 -03:00
<h5>Destination Type: IP Address</h5>
2026-01-16 15:01:13 -03:00
<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>
<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>
2025-12-29 18:30:39 -03:00
<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>
<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-27 15:22:12 -03:00
<h5>Restart Mode</h5>
2025-04-16 10:18:23 -03:00
<p>Choose whether WireGuard services should be automatically restarted when configurations change, or if manual intervention is required.</p>
2026-02-03 11:47:11 -03:00
2025-04-16 10:18:23 -03:00
<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>
2026-02-03 11:47:11 -03:00
<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>Routing Templates</h5>
<p>Define routing configurations that can be applied to peers.</p>
<h5>Default Template</h5>
<p>If checked, this template will be the default for the selected WireGuard instance. Only one default template is allowed per instance.</p>
2025-04-15 12:16:50 -03:00
<h5>Route Type</h5>
2025-04-16 14:34:46 -03:00
<p>Select the type of routes to push to the client.</p>
<ul>
<li><strong>Default Route (0.0.0.0/0)</strong>: Redirects all traffic through the VPN.</li>
<li><strong>Routes from Peers on same Interface</strong>: Pushes routes for other peers on the same WireGuard interface.</li>
<li><strong>Routes from All Peers</strong>: Pushes routes for all peers across all interfaces.</li>
<li><strong>Custom Routes</strong>: Allows you to specify custom CIDR ranges.</li>
</ul>
<h5>Custom Routes</h5>
<p>Enter custom routes in CIDR notation, one per line (e.g., 192.168.1.0/24).</p>
<h5>Allow Peer Custom Routes</h5>
<p>If checked, allows specific peers to add their own custom routes on top of this template.</p>
<h5>Enforce Route Policy</h5>
<p>If enabled, firewall rules will be applied to strictly enforce this routing policy.<br>The peer will only be able to access networks explicitly defined by the assigned routing template.<br>Any traffic to destinations outside these routes will be blocked.</p>
<p>Note: depending on the number of routes and peers, enabling this option may generate a large number of firewall rules.</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>
2026-01-27 15:22:12 -03:00
<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>
'%(line)s' is not a network address. Use the network address (e.g., '%(net)s').(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 PasswordActionActionsActiveAddAdd Client routeAdd Filter ListAdd Forward Rule (allow)Add IP AddressAdd IntervalAdd Peer GroupAdd ProfileAdd Routing TemplateAdd Time IntervalAdd UserAdd WireGuard InstanceAdd WorkerAddressAdministratorAllAll 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 Custom RoutesAllow Peer to PeerAllow traffic from VPN to WANAllowed IP or NetworkAllowed IPsAllowedIPs at Peer section of wgAllowedIPs at client configuration fileAllowing peer custom routes is not applicable when Route Type is 'Default Route'.ApplyApply Route TemplateApply templateAre you sure you want to create a new peer?Are you sure you want to delete the profile "%(name)s"?Are you sure you want to delete this time interval?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 least one route must be provided when Route Type is 'Custom'.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 trafficBackBack to ListCache EnabledCache Web Load Previous CountCancelCannot apply template: This template does not allow custom routes, but the peer has custom client routes defined.Change LanguageCityClearClient RoutingClipboard API not supported.CloseClose QR CodeClusterCluster Cache Processing TimeCluster 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 serviceConfirm DeleteConsoleConsole EnabledCopy TextCountryCreate Firewall RuleCreate InstanceCreate PeerCreate Port forwarding RuleCreate Schedule ProfileCreate a new WireGuard InstanceCurrent Active Template:Custom RoutesCustom routes should be empty when Route Type is 'Default Route'.DNS ConfigurationDNS 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 AnalystDefaultDefault DNS Filter List created successfullyDefault Forward PolicyDefault PasswordDefault PolicyDefault Route (0.0.0.0/0)Default TemplateDefault 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 PeerDelete Schedule ProfileDelete Time IntervalDelete WireGuard InstanceDescriptionDestinationDestination Hostname or IP AddressDestination IPDestination PeerDestination Peer Include NetworksDestination PortDestination TypeDigitsDisabledDisabled WireGuard Peer ListDisplay 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
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 InterfaceInactiveInstanceInstance IDInstance TrafficInterfaceInterface KeysInternal IP AddressInternal NetworkInvalidInvalid 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 route format: '%(line)s'. Please use CIDR notation (e.g., 10.0.0.0/24).Invalid 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 refreshed.Invite text copied to clipboard.KeysLanguageLast SeenLast UpdateLast seen more than 10 minutes ago or never seen.Latest 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 WANMaster Cache Processing TimeMemory usageMessage templatesMondayNameNetmaskNeverNewNew WireGuard InstanceNo WireGuard Instances FoundNo WireGuard instances found.No active VPN invitationsNo interfaces found|No WireGuard interfaces were found to process.No invite data available to refresh.No routing templates available for this interface.No schedule profiles found.No time intervals found.No traffic history, please wait a few minutesNo workers configuredNot DestinationNot SourceNot StateNot setOne route per line in CIDR notation.OutOut 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 Configuration: Peer 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.Pre-Shared KeyPrimary DNSPrimary Enable WireGuardPrimary ServerPrimary WireGuardPrimary node mirroring (WireGuard and firewall rules)PriorityPriority must be greater than or equal to 1Private KeyProfile NameProtocolPublic AddressPublic KeyQR CodeREJECTRandom PasswordRandom Password ComplexityRandom Pa
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>Configuração Avançada do Firewall da VPN</h5>
<p>
Esta interface serve como uma ferramenta abrangente para gerenciar regras de firewall, permitindo que os usuários implementem políticas de tráfego avançadas entre peers de VPN e redes. Ela simplifica o estabelecimento de regras de firewall, o filtro de pacotes e as configurações de NAT, possibilitando um controle preciso sobre a segurança da rede. Os usuários podem definir endereços IP de origem e destino, portas, protocolos e ações para ajustar o fluxo de tráfego, garantindo um ambiente de rede seguro e eficiente.
</p>
2025-04-16 11:31:08 -03:00
<h5>Seleção de Destino</h5>
<p>
Você tem a opção de aplicar esta regra a um endereço IP ou rede específica e/ou a múltiplos peers como destino.<br><br>
Habilitar a opção "Include peer networks" irá incluir automaticamente todos os IPs permitidos associados a cada peer selecionado como destino.<br><br>
Por favor, note que selecionar múltiplos peers com redes incluídas tanto na origem quanto no destino pode resultar em um rápido aumento no número de regras de firewall geradas, dependendo da sua configuração.<br><br>
A opção "Not Destination" nega o endereço IP, rede ou peer(s) selecionado(s).
</p>
<h5>Protocolo e Porta</h5>
<p>
2025-04-15 12:16:50 -03:00
Apenas os protocolos mais comumente utilizados estão listados aqui. Se você precisar de um protocolo específico, por favor, abra uma issue no GitHub.<br><br>
Selecionar TCP+UDP resultará na duplicação das regras geradas.<br><br>
As portas podem ser especificadas como números individuais (por exemplo, 8080) ou como intervalos (por exemplo, 8001:8999).
</p>
<h5>Seleção de Origem</h5>
<p>
Você tem a opção de aplicar esta regra a um endereço IP ou rede específica e/ou a múltiplos peers.<br><br>
Habilitar a opção "Include peer networks" irá incluir automaticamente todos os IPs permitidos associados a cada peer selecionado.<br><br>
Por favor, note que selecionar múltiplos peers com redes incluídas tanto na origem quanto no destino pode resultar em um rápido aumento no número de regras de firewall geradas, dependendo da sua configuração.<br><br>
A opção "Not Source" nega o endereço IP, rede ou peer(s) selecionado(s).
</p>
Servidores DNS enviados aos peers.
<br>
Usar o IP interno como DNS primário habilita a resolução de nomes interna
e filtragem de DNS.
Força as regras de roteamento definidas pelos modelos de roteamento usando regras de firewall.
<br>
Peers com uma rota padrão (0.0.0.0/0) não são restringidos.
<br><br>
Nota: dependendo do número de rotas e peers, esta opção pode gerar
um grande número de regras de firewall.
Endereço IP interno e máscara de rede usados pela interface WireGuard.
2025-12-29 18:30:39 -03:00
Intervalo usado para atualizar as informações de status do WireGuard na interface web.
Nome opcional usado apenas para exibição na interface web.
Nome de host público ou endereço IP e porta UDP usados pelos peers para se conectar.
<br>
A <b>listen port</b> deve estar exposta e mapeada em seu arquivo Docker compose (YAML).
Chaves privada e pública do WireGuard para esta interface.
<br>
A chave privada deve permanecer em segredo.
2025-04-15 12:16:50 -03:00
Alterá-la requer a atualização de todas as configurações dos peers.
<h5>Portas Padrão</h5>
<p>O arquivo padrão <code>docker-compose.yml</code> especifica o intervalo de portas <b>TCP</b> <b>8080-8089</b>. Se você deseja alterar o redirecionamento de portas para um intervalo diferente, é necessário editar manualmente o arquivo <code>docker-compose.yml</code> e executar novamente a etapa do Docker Compose descrita nas <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">instruções de implantação</a>.</p>
<h5>Tipo de Destino: Peer</h5>
<p>O redirecionamento de porta dará prioridade ao primeiro endereço IP do Peer com prioridade Zero.</p>
2025-12-29 18:30:39 -03:00
<h5>Tipo de Destino: Endereço IP</h5>
2026-01-16 15:01:13 -03:00
<p>As regras de encaminhamento de porta redirecionarão para o endereço IP especificado. Lembre-se de alocar o endereço IP ou rede para um Peer.</p>
<h5>Adicionando uma Regra de Encaminhamento</h5>
<p>Gera automaticamente uma regra de encaminhamento para acomodar configurações de firewall mais restritivas.</p>
<h5>Mascarar Fonte</h5>
<p>Isto serve como uma solução temporária quando um peer não utiliza a VPN como gateway padrão. É importante notar que esta configuração não é recomendada, pois altera o endereço de origem de todas as conexões para corresponder ao endereço IP da instância do WireGuard.</p>
<h4>Níveis de Usuário</h4>
<h5>Analista de Debug</h5>
<p>Acesso a informações básicas do sistema e logs para solução de problemas. Sem acesso para modificar configurações ou visualizar dados sensíveis, como chaves de peer.</p>
<h5>Somente Visualização</h5>
<p>Acesso total de visualização, incluindo chaves de peer e arquivos de configuração. Não pode modificar nenhuma configuração ou ajuste.</p>
<h5>Gerente de Peers</h5>
<p>Permissões para adicionar, editar e remover peers e endereços IP. Não inclui acesso para modificar configurações de instâncias do WireGuard ou configurações de nível superior.</p>
<h5>Gerente do WireGuard</h5>
<p>Autoridade para adicionar, editar e remover configurações de instâncias do WireGuard.</p>
<h5>Administrador</h5>
<p>Acesso total ao sistema. Pode visualizar e modificar todas as configurações, ajustes e gerenciar usuários.</p>
<br>
<h4>Grupos de Peers</h4>
<p>Selecione quais grupos de peers este usuário pode acessar. Se nenhum grupo de peers for selecionado, o usuário terá acesso a todos os peers.</p>
2025-12-29 18:30:39 -03:00
<h4>Console</h4>
<p>Ativar ou desativar o acesso ao console web para este usuário.</p>
<h4>Filtro Aprimorado</h4>
<p>Esta opção filtra a resposta do status da API para incluir apenas os peers aos quais o usuário tem acesso. Dependendo do tamanho do seu ambiente, ativar esta opção pode impactar o desempenho. Para mitigar isso, considere aumentar o "Intervalo de Atualização da Web" para reduzir o número de requisições.</p>
<h5>Modo do Cluster</h5>
<p>Configure como o cluster opera e sincroniza as configurações entre os nós.</p>
<h5>Intervalos de Sincronização</h5>
<p>Configure com que frequência as estatísticas e os dados de cache são sincronizados entre os nós do cluster.</p>
2026-01-27 15:22:12 -03:00
<h5>Modo de Reinicialização</h5>
2025-04-16 10:18:23 -03:00
<p>Escolha se os serviços WireGuard devem ser reiniciados automaticamente quando as configurações mudarem ou se é necessária intervenção manual.</p>
2026-02-03 11:47:11 -03:00
2025-04-16 10:18:23 -03:00
<h5>Exibição do Worker</h5>
<p>Selecione como os workers devem ser identificados na interface - por nome, endereço do servidor, localização ou uma combinação.</p>
<h5>Peers</h5>
<p>Selecione quais peers podem ser gerenciados por usuários com este grupo de peers.</p>
2026-02-03 11:47:11 -03:00