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

406 lines
84 KiB
Modelica
Raw Normal View History

2026-03-12 15:23:39 -03:00
Þ•ÇT¹Œ,p;½q;¢/>SÒAm&D”GÞ­H~ŒJ‚ KwŽKL3$MƒXNªÜSÖ‡YÅ^[€$^¥`IÂa] hOjj3ºjFîj/5l+el'‘l¹lÀlÒlðl m
m#m3m:mBmIm MmYmlm~mŽmŸm¯m ÈmÒm ámîm ým nn0n9n
Pn[n
cnqn‰unÿn o
o o;oTo go
to‚o$ o"Åo#èo! p.pGp ]pip {p'œpQÄpqq1q+@q7lq=¤q@âq>#rEbr5¨r7Þr8s3Os[ƒs¯ßs@�t2Ðt uuu+4u)`uŠu¡u6µu6ìu#v1Avsv�v •v¢v´vÈv
Øvævwq w}w�w’w˜w§wwÓw
Ùwçwïw
x!x?x Sx`xqx;ˆx&Äxëxòxy% yFyUy]y mywyyœy±yÉyày ðyüyz0zPz iz
vzA„zÆzØz$ðz%{$;{4`{2•{2È{"û{$|C|T| c|o|‰|!�|¿|Ä|Ö|,Þ| }"}3}B}\}4m}C¢}Jæ}F1~x~~Ž~¤~¹~Ö~î~ #;Pj o {"‡ª¹!Êìý€€€-€J€_€ t€�€™€ €²±€d�i�x�Œ�Ÿ�º�Ð�å�
õ�‚ ‚ ‚&‚8‚G‚_‚u‚ ˆ‚
’‚ ‚
¦‚
´‚‚Ù‚+è‚
ƒ"ƒ8ƒ
@ƒNƒ
bƒmƒuƒ ~ƒˆƒ�ƒ­ƒ:Ń„„O0„€„–„D­„>ò„W1…Q‰…_Û…K;†‡† †°†͆Oé†9‡N‡]‡;l‡ ¨‡6´‡Yë‡EˆMˆ
Vˆaˆ0vˆ
§ˆW²ˆ
‰ЉŸ‰%¿‰å‰ŠŠ%Š"7Š ZŠ${Š Š(½Š+æŠ#‹6‹ =‹&J‹$q‹%–‹#¼‹à‹ñ‹ù‹
Œ
Œ(Œ&/Œ V�b�g�p� v�
ƒ�Ž�Až� à�/Ž1Ž PŽ]ŽeŽ/uŽ3¥Ž3ÙŽW
�e�cn�Ò� Õ�â�ë� ô�� ��*�>�O�@W�˜�:ª�å�õ�‘F‘`‘‘O‘‘á‘ð‘,’
-’$8’&]’„’¢’ ´’Õ’Ú’ ã’ í’1ù’+“<“D“#T“x“�“ž“
§“ ²“¾“͓֓ Ü“
è“ó“”
””8”U”r”†”š”"¬”Ï”ì” ô”••0•7•<•D•J•N• e• r• ~• ‹•—•#š• ¾•ß•û•–-–J–h–B‚–$Å– ê– —2!—T—p—-‰—·—Í—
Ý— è—ò—ú— ˜˜<.˜2k˜
ž˜$©˜Θ@ç˜(™@™V™
Z™ h™
u™€™‰™0Ÿ™<Й#
š,1š^šcšvš'‹š,³š àšìš ›5› K›
X›
f› q›8~›'·›'ß›,œ4œ<Sœ-�œ¾œ:Ûœ4�'K�s�Hy�Â� Û�ç�Iü�9Fž#€ž/¤ž1Ôž"Ÿ^)Ÿ2ˆŸ4»Ÿ1ðŸ$" G 8L 3…  ¹ Æ &Ø $ÿ $¡6¡
E¡ S¡_¡x¡‡¡5™¡Ï¡+Ø¡ ¢ ¢¢&¢
5¢@¢H¢O¢V¢f¢�¢5˜¢
΢Ù¢è¢÷¢;£D£L£[£l£…£¤£­£Á£¡Û£}¤�¤ Ÿ¤¬¤¾¤ؤ
à¤4ë¤ ¥$6¥%[¥�¥#—¥»¥3Ì¥2¦3¦
E¦ S¦&_¦†¦�¦”¦&�¦$Ħé¦û¦§1§DC§ˆ§Fœ§ ã§
í§.û§*¨1¨HA¨Ѝ“¨
±¨ ¼¨6Ȩ
ÿ¨
© © ©'© D©
N©Y©
_©j©+Š©¶©Ô©å©ª ªªª 2ª >ª HªTª0hª<™ª2ÖªD «:N«
‰«—«¦« ««¸«=Ϋ„ ¬‚‘¬D­»Y­&®@<¯N}¯G̯)°9>°Ix°:°9ý°%7±?]±e�±5²E9²*²®ª²xY³Ò³FØ´
µ*µ#3µ!Wµyµ!ˆµªµ°µ
еÞµûµ
< 9]¶
—¶¥¶ ¬¶¶¶½¶ζã¶ó¶
·'·B·0J·%{·
¡· ¬·¹·Õ·&ñ·¸4¸=¸
C¸N¸a¸u¸ }¸ ‡¸
”¸¦¢¸I¹_¹ t¹~¹‡¹˜¹©¹ùÖ¹ê¹ü¹º!º;6º=rº°º¿ºκ($»M»h»ˆ»&Œ»…³»9¼
=¼
K¼Y¼k¼e‰¼ï¼D½T¾j\ÁCÇÄJ Ç1VʈˋŒÍš΄³Î@8ÏLyÐ ÆÑ�ÒÖ"`ÜIƒÞÒÍá5 ä*Öå´íQ¶ï8ð%Að3gñ+›ñ#Çñëñóñ" ò!/ò
Qò_òoò…ò�ò–ò�ò¥òºò%Ôò!úòó1ó$Ió
nó
|ó‡ó™ó°ó!¿óáóýó
ô)ô
8ô
CôQôyWôÑôÚôðô"õ%%õKõiõzõŒõ*«õ)Öõ6ö57ö+mö™ö¬ö»ö!Ñö6óöf*÷‘÷!™÷»÷)Í÷@÷÷D8øG}øRÅøMù9fù: ù?Ûù>úeZúÀúQ@ûB’ûÕûïûþû2ü1Kü}ü˜ü,¯ü(Üü*ý<0ý,mýšý¡ý³ýÃýÖýèý'úý"þ�+þ»þÊþÑþÙþïþ"ÿ+ÿ2ÿDÿ/Lÿ|ÿ(�ÿ¸ÿÒÿâÿýÿS4m¢±*Ì-÷%<D WdjŠ¢¹Õ
å!ð0P iu]Šè"û+/J,z<§:äD*d-�½Óå#õ)2 \f~7—$Ïô(H?aK¡QíL?Œ•«&Æ"í*I
` n�¬É ÑÞæ
  ! B T d 
m { (� ¹ Ð ç û 

µ3
é
ð
 $  D e € � ² Ã 
Ô â ñ  " B a | ‹ › ¡ ³ Å Ù ?ò 2
D

V
a
s
2026-01-27 15:22:12 -03:00
‡
 �
 ›
 §
 ±
Ò
â
Fý
D#Zf~å6FUUœNòYAP› ì
-M_mÍäõ< CBOm’ 3/ cUmzÃ>!U3w-«Ùì)#(M1v%¨@Î@'Px€,•+Â.î-Kbj|�¡¨±ÀÅÔ Ú
æôJ &WI~%Èî
ý &$(K,tm¡ d~†š £ ­·ÐÙì  5NGc«¾#ÐHô=[ZuÐâDE$X#}$¡Æ-ß
1<H…—ž'¯×ð  ' . 
@ K [ t  }  Š ” $° Õ *è  !4!K!]!*|!§!°!¿!%Õ!û!""""$">"V"k"ƒ"˜"A›"0Ý"*#,9#$f#&‹#*²#Ý#Gý#,E$&r$™$A°$,ò$'%.G%v%
’% �% §%±%À%Ó%ë%Q&@T& •&&Ÿ&!Æ&Mè&6'R'h'o'‚' •' ¡'­'>Ê'D (-N(0|(­(²(É(*â(4
)B)R)g)Sv)Ê)Ú)ê)ù)? *&K*,r*0Ÿ*Ð*Bì*8/+h+B„+0Ç+0ø+),D/,t,“,œ,Q²,I-N-'h-0�-%Á-eç-@M.FŽ.3Õ.6 /@/=G/=…/Ã/ Ú/-û/,)0V0m0�0 –0£0À0Ò0:ï0 *141
P1^1 p1z1Ž1
�1¨1±1¹1$Ï1!ô1:2 Q2[2k2‚2?’2 Ò2Þ2ñ23! 3 B3N3.h3“—3+4I4]4n4‚4Ÿ4 §4B´4÷4054C5x5#‘5µ5IÏ5?6Y6t6Š6*ž6É6Ñ6 Ù6-ã6,7>7X7"x7›7M²78O8 i8u8=„8Â8Ô8më8Y9$h9
�9›99ª9ä9ê9 ñ9û9
:+:::I:
P:%^:2„:$·:Ü:7ö:.;5; =;G;b;
r; };Š;;¢;OÞ;>.<Zm<IÈ<=)=>=D=U=Rs=^Æ=e%>6‹>·Â>z?K˜@cä@NHA0—AEÈAHB:WB5’BÈBMçBd5C>šCVÙC0DœMD|êD³gEYF uF�F)ˆF(²FÛF"ðFGG6G$KG
pG~G …G’G—GM›GMéG7H IHUH
eHpHŠH¤H½HÜHûH
I>&I+eI‘I¡II%ÖI-üI)*JTJ\JeJuJ!‘J³J ¼JÉJ ØJ�åJgK„K
¤K¯K¸KÌKàKöK
L%L9LRLfL:€L<»LøL M&M#DMhM,ƒM)°M'ÚMN"N…)N¯NµNÉNåN"üNHO"hOy>ÙV˜}Ñ/j¨ßi6Û¹
P/yo2�÷E|c´Ñ+¸å[ÄÇÜm±¾õH|ï–"«@P‚ĺD,ÞLt 1û‹!sl©š¼WÂ2¾fE0¤–˜>;�èzw­›9”𦢱ðBµqzUþ‡ç&a<~"\…æÿây<È4?8dœ™�- ÈZA)¥ |¿ñŽ
ªÝN¡ÀÐJÀtIž qC}jF¤þ®M�u.BÁ³%Vvcï(+,7‘úá1p¢×êˆ07Ò}*Ðä­´ìæ]åüdíܬ÷-‚Í9Ú‘„6©Cq'#ƒ2I;‰aOWŸ1ŠÊkN=“_UG·ž5u”œ
BOà¡èôÆ×Ͳ€îµ¬.†ª†9‰A
UÅXÉÅŽ ä3 ›ó#í Zx^œ²’˜Š]n
öÙ=‚T!)!bŠm¹ƒãJ&¸±ÆC»‹:áAùÔÏÀ{鄯gm€ S¸M¬Y®Q’Sýl{»Áàˆ x&i%D˼rRw´XÃêtÖ—h“̵H‹Q3 5(¿_™Ë8ÞLÄú4Ê:VØT>§Ãç¹^4fûE�³ŸŒýõë"�R\_7Y<£nl8%Qüº*ã®�K¥”Ø6‡`evF½jÖ;•·økÉDbˆ��Z¿\ŒÌsë½Fp­
,Ô™3Že¦‡oÅž?T$Óu]MÂr Úxºs¦R°G)iñ�b5š’«…fkN³Ã~KòÕ�`²éKeŒßr z¤–w¾/cöð@gh�°(¨?`Ÿ—IHÿ¯°$Y¨~«[¢‰£.ª©Ó �†¼—ÇóS• W¯îOXh$#0�€â'*do:¡Òø@ÁG½J¥ô·agΑ'pƒ§“Ý^-ì[L…+Æ•{Çò n£„§P=�»›ÕÎùÏvÛ
<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>
DNS servers pushed to peers.
<br>
Using the internal IP as primary DNS enables internal name resolution
2026-02-09 22:07:48 -03:00
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>
2025-12-29 18:30:39 -03:00
Note: depending on the number of routes and peers, this option may generate
2026-03-12 11:10:46 -03:00
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.
2025-12-29 18:30:39 -03:00
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.
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>
2025-12-29 18:30:39 -03:00
<h5>Masquerade Source</h5>
2026-01-16 15:01:13 -03:00
<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>
<h4>Console</h4>
<p>Enable or disable web console access for this user.</p>
2025-12-29 18:30:39 -03:00
<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>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>Authentication Types</h5>
<p>Select how users will authenticate through this method.</p>
<ul>
<li><strong>Local Password</strong>: Users will authenticate using a standard username and password stored locally. Only one of this type can be created.</li>
2026-01-27 15:22:12 -03:00
<li><strong>TOTP (Time-Based One-Time Password)</strong>: Users will need to enter a rotating token from an authenticator app. Requires setting a Global TOTP Secret.</li>
<li><strong>OIDC (OpenID Connect)</strong>: Users will authenticate via an external identity provider (like Keycloak, Google, or Authelia). Requires Provider URL, Client ID, and Client Secret.</li>
2026-03-12 15:23:39 -03:00
</ul>
<h5>Cluster Mode</h5>
<p>Configure how the cluster operates and synchronizes configurations between nodes.</p>
<h5>Sync Intervals</h5>
2026-03-12 15:23:39 -03:00
<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>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>
<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>
<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>
2026-01-27 15:22:12 -03:00
<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>
'%(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 PasswordActionActionsActiveAddAdd API KeyAdd Allowed DomainAdd Allowed EmailAdd Auth MethodAdd Client routeAdd Filter ListAdd Forward Rule (allow)Add GroupAdd 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.AllowAllow ExportAllow ForwardAllow Instance to InstanceAllow Peer Custom RoutesAllow Peer to PeerAllow ReloadAllow RestartAllow traffic from VPN to WANAllowed Domain deleted successfully.Allowed Domain saved successfully.Allowed Email deleted successfully.Allowed Email saved successfully.Allowed Emails & DomainsAllowed 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'.ApplyApply 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 allowed domain "%(domain)s"?Are you sure you want to delete the allowed email "%(email)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 profile "%(name)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.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:Auth MethodAuthenticationAuthentication MethodAuthentication Method deleted successfully.Authentication Method saved successfully.Authentication MethodsAuthentication TypeAutomatic 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 atBypass (public)Cache EnabledCache Web Load Previous CountCancelCannot apply template: This template does not allow custom routes, but the peer has custom client routes defined.Change LanguageCityClearClear ScheduleClient 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 Authentication MethodCreate Firewall RuleCreate Gatekeeper GroupCreate Gatekeeper UserCreate InstanceCreate PeerCreate Port forwarding RuleCreate Schedule ProfileCreate a new WireGuard InstanceCurrent Active Template:Current timeCustom 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 L
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 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 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 templatesMissing a method or feature?MondayNameNetmaskNeverNewNew WireGuard InstanceNext DisableNext EnableNext disableNext enableNoNo Allowed Emails or Domains found.No Authentication Methods found.No Gatekeeper Groups found.No Gatekeeper Users found.No IP Addresses found.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 fields must be empty for Local Password authentication.OIDC fields must be empty for TOTP authentication.One FactorOne 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)OutOut 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 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 ListPeer List Refresh Interval must be at least 5 secondsPeer ManagerPeer SchedulePeer StatePeer TrafficPeer and IP Address cannot be selected at the same time.Peer created|Peer created successfully.Peer deleted|Peer deleted successfully.Peer not created|Missing instance parameter.Peer reactivated successfully.Peer reactivated, but failed to reload WireGuard interface: Peer scheduling profile updated successfully.Peer suspen
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: es
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=2; plural=(n != 1);
<h5>Configuración avanzada del firewall VPN</h5>
<p>
Esta interfaz sirve como una herramienta completa para gestionar reglas de firewall, permitiendo a los usuarios implementar políticas de tráfico avanzadas entre peers de VPN y redes. Simplifica el establecimiento de reglas de firewall, el filtrado de paquetes y las configuraciones de NAT, posibilitando un control preciso de la seguridad de la red. Los usuarios pueden definir direcciones IP de origen y destino, puertos, protocolos y acciones para ajustar el flujo de tráfico, asegurando un entorno de red seguro y eficiente.
</p>
<h5>Selección de destino</h5>
<p>
Puedes aplicar esta regla a una dirección IP o red específica y/o a múltiples peers como destino.<br><br>
Habilitar "Include peer networks" incluirá automáticamente todas las IPs permitidas asociadas a cada peer seleccionado como destino.<br><br>
Ten en cuenta que seleccionar múltiples peers con redes incluidas tanto en origen como en destino puede incrementar rápidamente el número de reglas generadas, dependiendo de tu configuración.<br><br>
La opción "Not Destination" niega la IP, red o peer(s) seleccionado(s).
</p>
<h5>Protocolo y puerto</h5>
<p>
Solo se listan los protocolos más comunes. Si necesitas uno específico, abre un issue en GitHub.<br><br>
Seleccionar TCP+UDP duplicará las reglas generadas.<br><br>
Puedes especificar puertos como números individuales (por ejemplo, 8080) o rangos (por ejemplo, 8001:8999).
</p>
<h5>Selección de origen</h5>
<p>
Puedes aplicar esta regla a una dirección IP o red específica y/o a múltiples peers.<br><br>
Habilitar "Include peer networks" incluirá automáticamente todas las IPs permitidas asociadas a cada peer seleccionado.<br><br>
Ten en cuenta que seleccionar múltiples peers con redes incluidas tanto en origen como en destino puede incrementar rápidamente el número de reglas generadas, dependiendo de tu configuración.<br><br>
La opción "Not Source" niega la IP, red o peer(s) seleccionado(s).
</p>
Servidores DNS enviados a los pares.
<br>
El uso de la IP interna como DNS primario permite la resolución de nombres interna
2026-02-09 22:07:48 -03:00
y el filtrado de DNS.
Obliga as regras de roteamento definidas pelas modelos de roteamento usando regras de firewall.
<br>
Pares con una ruta predeterminada (0.0.0.0/0) no están restringidos.
<br><br>
2025-12-29 18:30:39 -03:00
Nota: dependiendo del número de rutas y pares, esta opción puede generar
2026-03-12 11:10:46 -03:00
un gran número de reglas de firewall.
Dirección IP interna y máscara de red utilizadas por la interfaz WireGuard.
Intervalo utilizado para actualizar la información de estado de WireGuard na interface web.
Nombre opcional utilizado solo para visualización en la interfaz web.
2025-12-29 18:30:39 -03:00
Nombre de host público o dirección IP y puerto UDP utilizados por los pares para conectarse.
<br>
El <b>Puerto de escucha</b> debe estar expuesta y mapeada en su archivo Docker compose (YAML).
Claves privada y pública de WireGuard para esta interfaz.
<br>
La clave privada debe permanecer secreta.
Cambiarla requiere atualizar todas las configuraciones de los pares.
<h5>Puertos predeterminados</h5>
<p>El archivo <code>docker-compose.yml</code> predeterminado especifica el rango de puertos <b>TCP</b> <b>8080-8089</b>. Si deseas cambiarlo, edita manualmente el archivo <code>docker-compose.yml</code> y vuelve a ejecutar Docker Compose según las <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">instrucciones de despliegue</a>.</p>
<h5>Tipo de destino: Peer</h5>
<p>La redirección de puerto dará prioridad a la primera IP del peer con prioridad cero.</p>
<h5>Tipo de destino: Dirección IP</h5>
<p>Las reglas redirigirán al IP especificado. Recuerda asignar esa IP o red a un peer.</p>
<h5>Añadir regla de reenvío</h5>
<p>Genera automáticamente una regla de reenvío para ajustarse a configuraciones más estrictas de firewall.</p>
2025-12-29 18:30:39 -03:00
<h5>Enmascarar origen</h5>
2026-01-16 15:01:13 -03:00
<p>Solución temporal cuando un peer no usa la VPN como puerta predeterminada. No se recomienda: cambia la IP de origen de todas las conexiones por la de la instancia WireGuard.</p>
<h4>Niveles de usuario</h4>
<h5>Analista de depuración</h5>
<p>Acceso a información básica y registros para depuración. Sin permiso para modificar ajustes o ver datos sensibles como claves de peer.</p>
<h5>Solo lectura</h5>
<p>Acceso completo de visualización, incluyendo claves y archivos de configuración. No puede modificar ajustes.</p>
<h5>Gestor de peers</h5>
<p>Permisos para añadir, editar y eliminar peers e IPs. No incluye modificar configuraciones de instancias WireGuard u otros ajustes.</p>
<h5>Gestor de WireGuard</h5>
<p>Autoridad para añadir, editar y eliminar configuraciones de instancias de WireGuard.</p>
<h5>Administrador</h5>
<p>Acceso total al sistema. Puede ver y modificar todas las configuraciones y gestionar usuarios.</p>
<br>
<h4>Grupos de peers</h4>
<p>Selecciona los grupos de peers a los que puede acceder este usuario. Si no seleccionas ninguno, tendrá acceso a todos.</p>
<h4>Consola</h4>
<p>Habilitar o deshabilitar acceso a la consola web para este usuario.</p>
2025-12-29 18:30:39 -03:00
<h4>Filtro mejorado</h4>
<p>Este filtro muestra solo los peers a los que el usuario tiene acceso. Según el tamaño de tu entorno, puede impactar rendimiento. Para mitigarlo, aumenta el "Intervalo de actualización web" para reducir las solicitudes.</p>
<h5>Claves de API</h5>
<p>Las claves de API permiten que aplicaciones externas interactúen com a API do WireGuard WebAdmin.</p>
<p><strong>Token:</strong> El token secreto utilizado para la autenticación. Manténgalo seguro.</p>
<p><strong>Instancias permitidas:</strong> Las instancias de WireGuard que esta clave puede gestionar. Si no se selecciona ninguna, la clave tiene acceso a TODAS las instancias.</p>
<p><strong>Permisos:</strong> acciones específicas permitidas para esta clave.</p>
<h5>Tipos de autenticación</h5>
<p>Seleccione cómo se autenticarán los usuarios a través de este método.</p>
<ul>
<li><strong>Contraseña local</strong>: los usuarios se autenticarán con un nombre de usuario y una contraseña estándar almacenados localmente. Solo se puede crear uno de este tipo.</li>
2026-01-27 15:22:12 -03:00
<li><strong>TOTP (Contraseña de un solo uso basada en el tiempo)</strong>: los usuarios deberán introducir un token rotativo de una aplicación de autenticación. Requiere configurar un secreto TOTP global.</li>
<li><strong>OIDC (OpenID Connect)</strong>: los usuarios se autenticarán a través de un proveedor de identidad externo (como Keycloak, Google o Authelia). Requiere la URL del proveedor, el ID de cliente y el secreto de cliente.</li>
2026-03-12 15:23:39 -03:00
</ul>
<h5>Modo de Cluster</h5>
<p>Configure cómo opera el cluster y sincroniza las configuraciones entre nodos.</p>
<h5>Intervalos de sincronización</h5>
2026-03-12 15:23:39 -03:00
<p>Configure con qué frecuencia se sincronizan las estadísticas y los datos de caché entre los nodos del cluster.</p>