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

521 lines
107 KiB
Modelica
Raw Normal View History

2026-11-16 16:52:14 -03:00
Þ•H\cœ4(F½)F¢çHSŠLmÞNLRÞeS~DU‚ÃUwFV¾V3ÜWƒYx”^
_šañºa¬dªÈgÖsm\Joާr€6u&·wÞzIû{]E‚O£„3ó„F'…/n†+ž†'ʆò†ù† ‡)‡E‡
N‡\‡l‡#|‡! ‡‡ɇч؇ ܇è‡ú‡
ˆˆ/ˆDˆZˆjˆ{ˆ‹ˆ ¤ˆ®ˆ·ˆ ƈÓˆ ∠îˆøˆ
‰‰(‰
?‰J‰
R‰`‰‰d‰î‰ ô‰
ŠŠ*ŠCŠ VŠ
cŠ0qŠ?¢Š%⊋$&‹"K‹#n‹!’‹´‹Í‹Ü‹ ò‹þ‹ Œ'1ŒQYŒ «Œ0·Œ.èŒ�&+�$R�w�'‰�%±�×�!ê� Ž ,Ž9Ž?ŽTŽ+cŽ7�Ž=ÇŽ=�@C�>„�;Ã�Eÿ�5E�8{�7´�@ì�8-‘3f‘[š‘Bö‘¯9’@é’R*“2}“ °“ ¼“ɓؓ+î“)”D”[” o”6�”6Ç”þ”1•N•k• p•}•�•
£•±•Ï•ä•që•l]–vÊ–SA—A•—H×—7 ˜X˜4h˜�˜¢˜¨˜·˜Ƙã˜
é˜÷˜ÿ˜™!-™O™ c™p™�™;˜™&Ô™û™šœš$®šÓš%òš›'›8›@› P›Z›b›w›Š›§›¼›Ô›ë› û›œ#œ;œ[œ tœ
�œA�œÑœãœ$ûœ% �6F�$}�4¢�2×�>
ž2Iž0|ž"­ž$ОõžŸŸ4(Ÿ ]Ÿ)iŸ“Ÿ­Ÿ!ÁŸãŸèŸïŸ   , E \ m | – 4§ CÜ J ¡Fk¡²¡¹¡È¡Ý¡ó¡¢!¢=¢U¢n¢‹¢£¢º¢ ̢آ𢣣$£�5£ ·£ ã"Ï£ò£¤!¤4¤E¤V¤]¤f¤u¤’¤§¤ ¼¤ɤá¤褲ù¤¬¥±¥À¥Ó¥ç¥ú¥ ¦+¦A¦X¦s¦‰¦ž¦
®¦¼¦ ˦ Õ¦ߦñ¦§§.§ A§
K§Y§
_§
m§{§’§+¡§
ͧÛ§ñ§
ù§¨
¨&¨.¨ 7¨A¨V¨f¨:~¨¹¨ʨOé¨<9©v©Œ©D£©>è©W'ªQª_ѪK1«}«—«°«À«Ý«Où«I¬^¬m¬;|¬ ¸¬YĬ­&­
/­:­0O­
€­‹­5 ­WÖ­.®®®î%ã® ¯'¯6¯I¯"[¯ ~¯$Ÿ¯į(á¯+
°#6°)Z°„°‹° ’°&Ÿ°$ư%ë°#±5±F±N±_±t±
‡±’±&™± À²̲Ѳ%Ú²³³ ³
³&³A6³ x³/™³ɳ è³õ³ý³/
´3=´3q´W¥´ý´cµjµ mµzµƒµ Œµ˜µ ©µ³µµÖµçµ@ïµ0:B}��F±¶ø¶·O)·!y·›·ª·,º·
ç·$ò·&¸>¸\¸ n¸�¸”¸ �¸ §¸1³¸å¸ö¸þ¸#¹2¹G¹X¹
a¹ l¹x¹‡¹�¹ –¹
¢¹­¹½¹ĹÙ¹ò¹º,º@ºTº"fº‰º¦º ®º»º_ͺ-»J»Q»V»^»d»h» » Œ» ˜» ¥»±»´»#λò» ¼*¼F¼)a¼‹¼›¼*²¼ݼú¼½B2½$u½ š½»½2ѽ¾ ¾-9¾g¾}¾
�¾ ˜¾¢¾ª¾¹¾̾JÞ¾<)¿2f¿$™¿¾¿@׿À0ÀJFÀ‘À—À
›À ©À
¶ÀÁÀÊÀ0àÀ<Á#NÁrÁ,ˆÁ4µÁ*êÁ4ÂJ bÂ"nÂ(‘ºÂÙÂÞÂñÂ'Ã,.à [Ãgà †Ã5�à ÆÃ
ÓÃ
áà ìÃ8ùÃ'2Ä'ZÄ,‚įÄ<ÎÄ- Å9Å:VÅ4‘Å'ÆÅîÅHôÅ=Æ VÆbÆIwÆ9ÁÆ#ûÆ/Ç1OÇ"�Ç^¤Ç2È46È1kÈ$�ÈÂÈ ÉÈÕÈ8ÚÈ3É GÉTÉ&fÉ$�ɲÉÄÉ
ÓÉ?áÉ !Ê-ÊFÊUÊ5gÊ�Ê+¦Ê ÒÊ ÞÊ ëÊõÊþÊË
ËË'Ë.Ë5ËEË`Ë5wË
­Ë¸ËÇËÖË;çË#Ì+Ì:ÌKÌdÌ9ƒÌ½ÌÆÌÚÌ¡ôÌ–Í¨Í ¸ÍÅÍ×ÍñÍ
ùÍ
ÎÎ$%Î%JÎpÎwÎ#�αÎ3ÂÎ2öÎ)Ï
;Ï IÏ&UÏ|Ï…ÏŠÏ&“Ï$ºÏßÏñÏÐ'ÐD9Ð~ÐF’Ð ÙÐ
ãÐñÐøÐ.ÑAÑHÑHXÑ¡Ñ"´Ñ×Ñ
öÑÒ
Ò
(Ò 3Ò6?Ò
vÒ�Ò ˆÒ ’ÒžÒ »Ò
2025-04-16 14:34:46 -03:00
ÅÒÐÒ
ÖÒáÒ+Ó-ÓKÓ\ÓyÓ€Ó‡Ó�Ó ©Ó µÓj¿Ó*Ô /Ô;Ô0OÔA€Ô<ÂÔ2ÿÔD2Õ:wÕ
²ÕÀÕÏÕ ÔÕáÕ=÷Õ¬5Ö„âÖ‚g×Dê×5/Ø6eØ»œØ&XÙ@ÚNÀÚGÛ)WÛ9�ÛI»Û:Ü9@Ü%zÜ? ÜeàÜ5FÝE|Ý*ÂÝ®íÝ"œÞ#¿ÞxãÞ+\߈ßFŽà(Õà
þà á#á!6áXá!gá‰ášá á
ÀáÎáëáôáüáâ<â9Bâ|â�â
‰â—â žâ ªâ´âÅâÚâêâãã9ãAã#Jã0nãiŸã% ä
/ä :äGäcä@ä&Àäçäå å
åå0åDå Lå Vå
cå¦qåæ.æ CæMæVægæxæ’æ¥æ¹æËæßæðæ;ç=AççŽç�ç½çÝç(óçè7èWè&[è…‚èé
é
é(é :é[éeyéßéAÿé Aë Nî•ïñ€…ô&øù-ù†'û–®ûzEü1ÀüSòýFÿ™\Eö¡<6ÞN �dô¡ ¨«ÙTj.!R™$Àì%°­,¢^/50p702¨1+Û1#2+222#H2l2
Œ2
š2¨2¸2*Í2&ø23&3.3 43>3U3s3�3«3Á3ß3#ý3!404%J4p4€4 �4œ4°4É4Ú4é45(5!;5]5 n5
x5†5“Œ5 6)6?6#W6%{6¡6¿6×6+ò6B7,a7#Ž7)²7%Ü7'8#*8N8m88ž8­8 Ä82å8Â9 Û97ç93:S:*k:&–:½:*Ò:&ý:$;"9;\; {;ˆ;�;­;0¼;<í;?*<Cj<D®<Aó<;5=Iq=5»=8ñ=6*>?a><¡>=Þ>_?F|?¸Ã? |@_A?}A½A×AòAB0B,LByB”B+«B6×BCC+RC=~C*¼CçCîCDD*D';DcD�D�ŠD‰E‰¤Es.FR¢FXõFGNG–G7¥GÝGäGëGþG3HHHOH^H'fHŽH%¡HÇHàHðH IK)I3uI©I¸I·ÒI%ŠJ.°J-ßJ
K!K1K9K LKYK_KyK‹K«KÃKÚKôK
L&L7L*SL~L
’L�LS²LM"M,?M/lMBœM-ßMH
N?VNB–NGÙN:!O(\O-…O³OËOÚO<ôO1P2@P!sP•P,³PàPéPðPQQ1$QVQ
rQ€Q’Q«Q/ºQNêQS9RQ�RßRçRüRS3SLS(`S‰S¥S!ÁSãSüST -T:TXTvT–TœT›±T MUYUaU
|UŠU šU»UÌUÜU åUòU'V)VEVaVtV�V™VέV|WƒW™W´WÎWæW'ùW!X<X WXxX�X«X¿XÑX
âX ðXüXY(YFYcY€Y�Y Y¦Y·YÉYåY<þY;ZLZ
iZ tZ�Z šZ§Z·ZÈZÙZùZ [H([q[%†[[¬[E\N\h\O\FÏ\c]az]‚Ü]Y_^¹^Ò^ï^-_ 0_VQ_¨_À_
Ð_;Þ_ `m'`•`�` ¦`°`9Ä` þ`aK alla™Ùasb!Œb3®b/âbc%cAc'\c#„c.¨c#×c4ûc50d fd+‡d³d »dÇd'Ûd#e*'e&ReyeŽe”e©e¼e
ÐeÞeSåe9g HgRg)dg
Žg™g
¡g ¬g¹g˜Ðg#ihD�hÒh
òhii<)i:fi<¡imÞi
Lj`Wj¸jÀjÕj
2026-01-27 15:22:12 -03:00
Ýj
èjój
kk(k =k Jk@Tk•kF©kðkl#lV8l�l©l²Ál*tmŸm±m>Ìm n2 n2Sn*†n±n8Ånþno o#o=9owo‰o�o&¡oÈoáoúo
p p &p
2p@pHpZpcp zp„p% pÆp'åp!
q/qIq#Yq&}q¤q¬q¼q`Ðq1r
Qr_rdrur{r€r�r´rÈrßrór'ør/ sPs,ps#�s&Ás.èst/t/Ot*t+ªtÖtWôt6Lu$ƒu¨u<Àu(ýu(&v<OvŒv ¦v ³v ¿v
ËvÙvìvwYwFsw?ºw%úw xI;x…xŸxNµxy
yy%y 6yByHy<_yHœy+åyz'*z4Rz*‡z4²zçz{/{3D{)x{¢{§{¾{3×{6 |B|R|p|N|Î|ß|ó|}?},S}*€}2«}Þ}?ú}5:~p~>‹~5Ê~,-Q3… ¥±ÂÆC‰€0Í€Aþ€7@�,x�e¥�? ‚CK‚<�‚5Ì‚ ƒ ƒƒ:$ƒ8_ƒ˜ƒ °ƒ6у2„;„R„k„J‚„
̈́ۄù„ …> …
_…&j…
‘…Ÿ… ®… ¸…Â…Ë…Þ…
í…ø…†† †:†2V†‰†’†¡†³†?Æ ‡‡%‡<‡ \‡>}‡ ¼‡ɇ!䇸ˆ¿ˆÒˆçˆ‰‰6‰ ?‰ L‰Y‰*u‰. ‰ωÕ‰!퉊?$Š<dСзŠÌŠ$ÜŠ‹ ‹‹,‹(E‹n‹„‹¢‹Á‹EÕ‹ŒG1Œ yŒƒŒ
“Œ&žŒ6ÅŒüŒ�P'�x�*��+º�æ�û�' Ž
3Ž
AŽ>OŽŽŽ§Ž ®Ž»ŽÊŽêŽùŽ �
�#�4B�w�—�4�ë�ò� ú���.�t7�¬� ±�¾�<Ö�E‘DY‘=ž‘OÜ‘H,’u’„’“’™’«’RÇ’­“‘È“ŠZ”Jå”90•:j•Û¥•Y�–7Û—^˜Nr˜7Á˜Aù˜>;™<z™9·™ñ™ šs±š>%›]d›(›·ë›(£œ)Ìœ…öœ2|�¯�VÈž(ŸHŸ _Ÿ,lŸ(™ŸŸ ÙŸúŸ  3 $H m  | ‰ Ž P’ Sã 7¡ ?¡L¡ ^¡j¡y¡ˆ¡¢¡»¡!Õ¡!÷¡ ¢ :¢D¢*M¢0x¢v©¢- £N£_£!t£'–£L¾£4 ¤)@¤j¤ s¤}¤ޤ#«¤Ϥפî¤
ý¤º ¥Æ¥â¥ ¦¦¦+¦@¦_¦w¦�¦¥¦Á¦Õ¦;ð¦9,§f§z§�§#­§ѧ2î§)!¨%K¨q¨#u¨�™¨)© /©<©X©%p©%–©l¼©&)ªž©Ka– ûiާ�1ÓìÄÇËRîâ6ÕÝžÔ'QÝOT{â
US`ˆ,*{�ô½?$ ¦ÏLzgãÊùh-€ÔJߣ&* ÔLVzú#¿rÁŒ/2jFï‚b>ü"oç]»gˆ®í%‚Hý
†Ô0ŸZ!&$C|o
D5Çæ/ƒÅP÷NkëFî#ïêm5ÊUr¬Ä_ 
òÝ;N=ä%h³OI·n[õ¥"�Šë�¢®¨˜�Ñ?¤sì¹tFÎs]uw7Œaqý8¬ã]ÕR \~”ÊR_áåÃYêZãóŠ}gtß´ÜcÞ,&»Øö’=¼Ãßfò7YÏŽ8‡…ñveÌ!ý¤‘�ÁEµ›éA!³å1/6~@MEö•l²kÙdñB×à*£ ñºáJ.¼eiwé-.È÷«P*)ƒç9+)ˆ(<ç¾GCô§À�3^y2=GÞÜ`(�Îx¤À4(W,’­;p@Ž\D´JI·ÆSõø#&Ðo;†CyÚ°HøM9ªè:O½—ù¿ K;ÐG8ä
±ÿ%q¬½–ÍA}$Z„ œ)$¯W‚XI0·.¹ï¨„™ÌD?z†Í.¼l<l¾ŸÑË:0hHûxàt>¥EÞ“îÒÿ–"Úa¥ü¢?>úÙ€‡šB'ÂÉ¡Ò3•ªàv±—!Ðæb28�W ÿc
nÅ ø[7éKV�©Š÷
£¸By®¡¯ì,„+ƒ Û)Ø ªFdcQºÖÅÖUÓò‘žêט©'=ëšÂ›s7`“f‹è¸¾’v0Æ‘1ûäA@­T°4'ð^ «Àó•9XÈü:” œËXHBâÈ"ÍC‰�[œ+E§p5̱1áºGþÜm¸iQ“rصL¦3|nš-…>fÕP×þÛÁ9SjŸÓÇÆqAö‹4µú<xÛ…k%YÏu¯¡Ò�<~M™j 4 —:dNbw(�#íèÉå¿ó°Öm53 ð\«íÙõ­´€³ô¹² ¦‰™Ä6}p²ÉÑ�ð‹DV‰‡6/ù»@Œ›Tþ|æ�u-eÎ2^¨Ú¢_{+˜

<h5>Advanced VPN Firewall Configuration</h5>
2025-04-16 11:31:08 -03:00
<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>
2026-03-13 20:44:45 -03:00
<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>
2026-03-18 11:24:10 -03:00
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>
2026-03-15 17:31:19 -03:00
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.
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.
2025-04-15 12:16:50 -03:00
WireGuard private and public keys for this interface.
<br>
The private key must remain secret.
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>
<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>
<h5>Deny Policy</h5>
<p>A Deny policy blocks all access to the matched routes.</p>
<h5>Protected Policy</h5>
<p>A Protected policy requires users to authenticate before accessing the application.</p>
<ul>
<li><strong>Allowed Groups</strong>: Limits access to specific user groups. Note: Using groups requires selecting an Authentication Method of type "Local Password".</li>
<li><strong>Authentication Methods</strong>: Specify which methods users can use to authenticate (e.g., Local Password, TOTP, OIDC).</li>
</ul>
2026-02-09 22:07:48 -03:00
<h5>Public Policy</h5>
<p>A Public policy allows access to the application without requiring any authentication.</p>
<h4>Authentication Types</h4>
<p>Select how users will authenticate through this method.</p>
2025-12-29 18:30:39 -03:00
<h5>Local Password</h5>
2026-03-12 18:54:37 -03:00
<p>Users will authenticate using a standard username and password stored locally. Only one of this type can be created.</p>
<h5>OIDC (OpenID Connect)</h5>
<p>Users will authenticate via an external identity provider (like Keycloak or Google). Requires Provider URL, Client ID, and Client Secret.</p>
<h5>TOTP (Time-Based One-Time Password)</h5>
<p>Users will need to enter a rotating token from an authenticator app. If a user does not have a personal TOTP configured, the <strong>Global TOTP Secret</strong> will be used instead. </p>
<h4>Gatekeeper User</h4>
2026-03-13 20:44:45 -03:00
<p>Gatekeeper users are used for authenticating against protected applications managed by this gateway.</p>
<h5>Password</h5>
<p>Required when creating a user. When editing, leave both password fields blank to keep the current password.
Passwords are stored using <strong>Argon2id</strong> hashing.</p>
<h5>TOTP Secret</h5>
<p>Optional per-user TOTP secret. When set, this user will authenticate using their own secret instead of the
2025-12-29 18:30:39 -03:00
global TOTP secret configured on the Authentication Method. Use the buttons below the field to generate a
random secret and scan the QR code with your authenticator app. Validate the secret by entering the current
6-digit PIN before saving.</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>
2025-04-15 12:16:50 -03:00
<h5>Peer Manager</h5>
2026-03-12 18:54:37 -03:00
<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>
<h4>Console</h4>
2025-04-15 12:16:50 -03:00
<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>
2025-12-29 18:30:39 -03:00
2026-01-16 15:01:13 -03:00
<h5>API Keys</h5>
<p>API Keys allow external applications to interact with the WireGuard WebAdmin API.</p>
<p><strong>Token:</strong> The secret token used for authentication. Keep this secure.</p>
<p><strong>Allowed Instances:</strong> The WireGuard instances this key can manage. If none are selected, the key has access to ALL instances.</p>
<p><strong>Permissions:</strong> specific actions allowed for this key.</p>
<h5>Application Route</h5>
<p>A Route defines a path prefix within this Application that requires a specific Access Policy.</p>
<ul>
<li><strong>Route Name</strong>: An internal identifier for this route (e.g., "public_api", "admin_area"). Used for reference and exports.</li>
<li><strong>Path Prefix</strong>: The URL path that triggers this route (e.g., <code>/api/</code> or <code>/admin/</code>). Use <code>/</code> to match all remaining paths.</li>
<li><strong>Policy</strong>: The Access Policy that will be enforced when a user accesses this path.</li>
<li><strong>Order</strong>: Determines the priority of this route when evaluating the request. Lower numbers are evaluated first. If multiple routes match a path, the one with the lowest order wins.</li>
</ul>
<h5>Application</h5>
<p>Define the main details of the application you want to expose through the gateway.</p>
<ul>
<li><strong>Name</strong>: A unique internal identifier for this application (e.g., "wiki", "crm"). Contains only letters, numbers, hyphens, or underscores.</li>
<li><strong>Display Name</strong>: A friendly, human-readable name for display purposes.</li>
<li><strong>Upstream</strong>: The destination URL where requests will be forwarded (e.g., <code>http://10.188.18.27:3000</code>). Must start with <code>http://</code> or <code>https://</code>.</li>
</ul>
<h5>Cluster Mode</h5>
<p>Configure how the cluster operates and synchronizes configurations between nodes.</p>
2025-12-29 18:30:39 -03:00
<h5>Sync Intervals</h5>
<p>Configure how frequently statistics and cache data are synchronized between cluster nodes.</p>
<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>IP Address List</h5>
<p>Manage specific IP addresses or networks that are allowed or denied access when using the IP Address List authentication method.</p>
<h5>IP Address & Prefix</h5>
2026-01-27 15:22:12 -03:00
<p>Enter a single IP address (e.g., 192.168.1.50) or a network address. Use the prefix length for CIDR notation (e.g., 24 for a /24 network). Leave prefix blank for a single host (/32 for IPv4, /128 for IPv6).</p>
2025-04-16 10:18:23 -03:00
2026-11-16 16:52:14 -03:00
<h5>Action</h5>
2025-04-16 10:18:23 -03:00
<p><strong>Allow</strong>: Grants access to the specified IP/network.<br>
<strong>Deny</strong>: Specifically blocks access from the specified IP/network.</p>
<h5>Description</h5>
<p>An optional note to help identify this entry (e.g., "Office Network", "Blocked Attacker").</p>
2026-11-16 16:52:14 -03:00
<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>Routing Templates</h5>
<p>Define routing configurations that can be applied to peers.</p>
2025-04-15 12:16:50 -03:00
<h5>Default Template</h5>
2025-04-16 14:34:46 -03:00
<p>If checked, this template will be the default for the selected WireGuard instance. Only one default template is allowed per instance.</p>
<h5>Route Type</h5>
<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>
2026-01-27 15:22:12 -03:00
<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>
'%(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.ACCEPTAPI DocumentationAPI Key deleted successfully.API Key saved successfully.API KeysAccess DeniedAccess PasswordAccess PoliciesAccess Policy deleted successfully.Access Policy saved successfully.ActionActionsActiveAddAdd API KeyAdd Access PolicyAdd Allowed DomainAdd Allowed EmailAdd ApplicationAdd Application HostAdd Application RouteAdd Auth MethodAdd Client routeAdd Filter ListAdd Forward Rule (allow)Add GroupAdd HostAdd IP AddressAdd IntervalAdd Peer GroupAdd ProfileAdd RouteAdd 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.AllowAllow ExportAllow ForwardAllow Instance to InstanceAllow Peer Custom RoutesAllow Peer to PeerAllow ReloadAllow RestartAllow access to everyone without authentication.Allow invalid or self-signed TLS certificates from the upstreamAllow invalid/self-signed certificateAllow traffic from VPN to WANAllowed Domain deleted successfully.Allowed Domain saved successfully.Allowed Email deleted successfully.Allowed Email saved successfully.Allowed Emails & DomainsAllowed GroupsAllowed IP or NetworkAllowed IPsAllowed InstancesAllowedIPs at Peer section of wgAllowedIPs at client configuration fileAllowing peer custom routes is not applicable when Route Type is 'Default Route'.ApplicationApplication Default Policy deleted successfully.Application Default Policy saved successfully.Application DetailsApplication Host deleted successfully.Application Host saved successfully.Application HostsApplication Route deleted successfully.Application Route saved successfully.Application RoutesApplication deleted successfully.Application saved successfully.ApplicationsApplyApply Route TemplateApply templateAre you sure you want to create a new peer?Are you sure you want to delete the API Key "%(name)s"?Are you sure you want to delete the IP address "%(address)s"?Are you sure you want to delete the access policy "%(name)s"?Are you sure you want to delete the allowed domain "%(domain)s"?Are you sure you want to delete the allowed email "%(email)s"?Are you sure you want to delete the application "%(name)s"?Are you sure you want to delete the authentication method "%(name)s"?Are you sure you want to delete the group "%(name)s"?Are you sure you want to delete the host "%(hostname)s"?Are you sure you want to delete the profile "%(name)s"?Are you sure you want to delete the route "%(name)s" (%(path)s)?Are you sure you want to delete the user "%(username)s"?Are you sure you want to delete this time interval?Are you sure you want to regenerate the token? The old token will stop working immediately.Are you sure you want to remove the default policy for "%(name)s"?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 least one user group must be selected when using Local Password authentication.At this stage, only core features are implemented:Auth MethodAuth MethodsAuthenticationAuthentication MethodAuthentication Method deleted successfully.Authentication Method saved successfully.Authentication MethodsAuthentication TypeAuto-apply failed for wg%(id)s: Automatic Rule: Firewall Settings Instance to InstanceAutomatic Rule: Firewall Settings Peer to Peer trafficAutomatic Rule: Port forward.Automatic rule: Allow established/related trafficAutomatic rule: Route PolicyBackBack to ListBecomes active atBecomes inactive atCa
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 extrasHostHostnameHostname contains invalid characters.HostsHour(s)I UnderstandIP AddressIP Address ListIP Address cannot be used without selecting a WireGuard instance.IP Address deleted successfully.IP Address is required when IP Lock is enabled.IP Address saved successfully.IP AddressesIP 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.IdentityIf 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 TOTP PIN.Invalid TOTP secret format. Must be a valid Base32 string.Invalid action.Invalid commandInvalid config fileInvalid confirmation|Please confirm deletion of WireGuard instance: wgInvalid hostname or IP AddressInvalid hostname.Invalid route format: '%(line)s'. Please use CIDR notation (e.g., 10.0.0.0/24).Invalid search domain: %(domain)sInvalid 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 CharactersLinked Peers (Debug)List Peer GroupsList URLList UsersListen PortLocal PasswordLocationLoginLogin againMASQUERADEMain ip addressManageManage Firewall RuleManage Firewall SettingsManage IP address or NetworkManage Peer Schedule ProfileManage Port ForwardManage client routeMasquerade SourceMasquerade traffic from VPN to WANMaster Cache Processing TimeMembersMemory usageMessage templatesMinimum 8 characters, with at least one uppercase letter, one lowercase letter, and one number.Missing a method or feature?MondayNameNetmaskNeverNewNew WireGuard InstanceNext DisableNext EnableNext disableNext enableNoNo Access Policies found.No Allowed Emails or Domains found.No Applications found.No Authentication Methods found.No Gatekeeper Groups found.No Gatekeeper Users found.No Hosts configured for this application.No Hosts found.No IP Addresses found.No Routes configured for this application.No 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 peers linked to this profile.No profile associatedNo 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 setOIDC Client IDOIDC Client SecretOIDC Provider URLOIDC authentication is temporarily unavailable and will be available soon.OIDC fields must be empty for Local Password authentication.OIDC fields must be empty for TOTP authentication.One route per line in CIDR notation.One-Time Password (TOTP)Only one Local Password authentication method can be configured.Open an issue on GitHubOpenID Connect (OIDC)Optional. One or more domains separated by commas (e.g. vpn, example.com).OrderOutOut InterfacePacket StateParametersPasswordPassword ConfirmationPassword confirmation is required for new users.Password for local authentication (leave blank if not using)Password is required for new users.Password is required.Password must be at least 8 characters long.Password must contain at least one lowercase letter.Password must contain at least one number.Password must contain at least
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>
2025-04-16 11:31:08 -03:00
<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>
<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>
2026-03-13 20:44:45 -03:00
<h5>Protocolo e Porta</h5>
<p>
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>
2026-03-18 11:24:10 -03:00
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>
2026-03-15 17:31:19 -03:00
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.
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).
2025-04-15 12:16:50 -03:00
Chaves privada e pública do WireGuard para esta interface.
<br>
A chave privada deve permanecer em segredo.
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>
<h5>Tipo de Destino: Endereço IP</h5>
<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>
<h5>Política de Negação</h5>
<p>Uma política de Negação bloqueia todo o acesso às rotas correspondentes.</p>
<h5>Política Protegida</h5>
<p>Uma política Protegida exige que os usuários se autentiquem antes de acessar o aplicativo.</p>
<ul>
<li><strong>Grupos Permitidos</strong>: Limita o acesso a grupos de usuários específicos. Nota: O uso de grupos requer a seleção de um Método de Autenticação do tipo "Senha Local".</li>
<li><strong>Métodos de Autenticação</strong>: Especifique quais métodos os usuários podem usar para se autenticar (ex: Senha Local, TOTP, OIDC).</li>
</ul>
2026-02-09 22:07:48 -03:00
<h5>Política Pública</h5>
<p>Uma política Pública permite o acesso ao aplicativo sem exigir nenhuma autenticação.</p>
<h4>Tipos de Autenticação</h4>
<p>Selecione como os usuários irão se autenticar através deste método.</p>
2025-12-29 18:30:39 -03:00
<h5>Senha Local</h5>
2026-03-12 18:54:37 -03:00
<p>Os usuários se autenticarão usando um nome de usuário e senha padrão armazenados localmente. Apenas um deste tipo pode ser criado.</p>
<h5>OIDC (OpenID Connect)</h5>
<p>Os usuários se autenticarão por meio de um provedor de identidade externo (como Keycloak ou Google). Requer URL do Provedor, ID do Cliente e Segredo do Cliente.</p>
<h5>TOTP (Senha de Uso Único Baseada em Tempo)</h5>
<p>Os usuários precisarão inserir um token rotativo de um aplicativo autenticador. Se um usuário não tiver um TOTP pessoal configurado, o <strong>Segredo TOTP Global</strong> será usado em seu lugar.</p>
<h4>Usuário do Gatekeeper</h4>
2026-03-13 20:44:45 -03:00
<p>Usuários do Gatekeeper são usados para autenticação em aplicações protegidas gerenciadas por este gateway.</p>
<h5>Senha</h5>
<p>Obrigatório ao criar um usuário. Ao editar, deixe ambos os campos de senha em branco para manter a senha atual.
As senhas são armazenadas usando hash <strong>Argon2id</strong>.</p>
<h5>Segredo TOTP</h5>
<p>Segredo TOTP opcional por usuário. Quando definido, este usuário irá se autenticar usando seu próprio segredo em vez do
2025-12-29 18:30:39 -03:00
segredo TOTP global configurado no Método de Autenticação. Use os botões abaixo do campo para gerar um
segredo aleatório e ler o código QR com seu aplicativo autenticador. Valide o segredo inserindo o PIN atual de
6 dígitos antes de salvar.</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>
2025-04-15 12:16:50 -03:00
<h5>Gerente de Peers</h5>
2026-03-12 18:54:37 -03:00
<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>
<h4>Console</h4>
2025-04-15 12:16:50 -03:00
<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>
2025-12-29 18:30:39 -03:00
2026-01-16 15:01:13 -03:00
<h5>Chaves de API</h5>
<p>As Chaves de API permitem que aplicativos externos interajam com a API do WireGuard WebAdmin.</p>
<p><strong>Token:</strong> O token secreto usado para autenticação. Mantenha-o seguro.</p>
<p><strong>Instâncias Permitidas:</strong> As instâncias do WireGuard que esta chave pode gerenciar. Se nenhuma for selecionada, a chave terá acesso a TODAS as instâncias.</p>
<p><strong>Permissões:</strong> ações específicas permitidas para esta chave.</p>
<h5>Rota de Aplicação</h5>
<p>Uma Rota define um prefixo de caminho dentro desta Aplicação que requer uma Política de Acesso específica.</p>
<ul>
<li><strong>Nome da Rota</strong>: Um identificador interno para esta rota (ex: "public_api", "admin_area"). Usado para referência e exportações.</li>
<li><strong>Prefixo do Caminho</strong>: O caminho da URL que aciona esta rota (ex: <code>/api/</code> ou <code>/admin/</code>). Use <code>/</code> para corresponder a todos os caminhos restantes.</li>
<li><strong>Política</strong>: A Política de Acesso que será aplicada quando um usuário acessar este caminho.</li>
<li><strong>Ordem</strong>: Determina a prioridade desta rota ao avaliar a solicitação. Números menores são avaliados primeiro. Se várias rotas corresponderem a um caminho, a de menor ordem vence.</li>
</ul>
<h5>Aplicação</h5>
<p>Defina os detalhes principais da aplicação que você deseja expor através do gateway.</p>
<ul>
<li><strong>Nome</strong>: Um identificador interno único para esta aplicação (ex: "wiki", "crm"). Contém apenas letras, números, hífens ou sublinhados.</li>
<li><strong>Nome de Exibição</strong>: Um nome amigável e legível para fins de exibição.</li>
<li><strong>Upstream</strong>: A URL de destino para onde as solicitações serão encaminhadas (ex: <code>http://10.188.18.27:3000</code>). Deve começar com <code>http://</code> ou <code>https://</code>.</li>
</ul>
<h5>Modo do Cluster</h5>
<p>Configure como o cluster opera e sincroniza as configurações entre os nós.</p>
2025-12-29 18:30:39 -03:00
<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>
<h5>Modo de Reinicialização</h5>
<p>Escolha se os serviços WireGuard devem ser reiniciados automaticamente quando as configurações mudarem ou se é necessária intervenção manual.</p>
<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>Lista de Endereços IP</h5>
<p>Gerencie endereços IP ou redes específicas que têm acesso permitido ou negado ao usar o método de autenticação por Lista de Endereços IP.</p>
2026-02-03 15:13:46 -03:00
<h5>Endereço IP e Prefixo</h5>
<p>Insira um único endereço IP (ex: 192.168.1.50) ou um endereço de rede. Use o comprimento do prefixo para notação CIDR (ex: 24 para uma rede /24). Deixe o prefixo em branco para um único host (/32 para IPv4, /128 para IPv6).</p>
2025-04-16 10:18:23 -03:00
2026-11-16 16:52:14 -03:00
<h5>Ação</h5>
2025-04-16 10:18:23 -03:00
<p><strong>Permitir</strong>: Concede acesso à rede/IP especificado.<br>
<strong>Negar</strong>: Bloqueia especificamente o acesso da rede/IP especificado.</p>
<h5>Descrição</h5>
<p>Uma nota opcional para ajudar a identificar esta entrada (ex: "Rede do Escritório", "Atacante Bloqueado").</p>
2026-11-16 16:52:14 -03:00