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

307 lines
59 KiB
Modelica
Raw Normal View History

2026-01-27 15:08:59 -03:00
Þ•à� (½!(¢ß*S‚.mÖ0ƒD4ªÈ9€s?ôAIC][I3¹KFíK/4M+dM'�M¸M
¿MÍMÝMäMìMóM÷MNN1N@NONdNmN
„N�N
—N¥N‰©N
3OAO\OuOˆO¦O ¼O ÈO'éOPP,P+;P¯gP@Q2XQ6‹Q6ÂQùQ1RIR NR
[RiRq‡RùR SSS#S@S
FSTS\SzS!ŠS¬S ÀSÍSÞS;õS&1TXT_TnT%�T³T»T ËTÕTÝTòT UU*UJU
cUAqU³U$ËU%ðU$V4;V2pV2£V"ÖV$ùVW/W >WJWdW!xWšWŸW±W,¹WæWýWXX7X4HXC}XJÁXF YSY ZYfY €Y ŒY"˜Y»YÊY!ÛYýYZZ&Z /Z<ZTZ²eZ[
[+[=[ U[
_[m[
s[
�[�[¦[+µ[
á[ï[\
\ \"\7\G\:_\š\«\Ê\à\D÷\W<]Q”]_æ]KF^’^«^»^Ø^ô^ __;'_ c_
o_z_0�_
À_WË_#`£`¸`%Ø`þ`a+a>a"Pa sa$”a#¹a Ýaêaòa&b *c6c;cDc Jc
WcAbc/¤cÔcÜc/ìc3d3PdW„dcÜd@e CePe Yeee ve€e”e@œeÝeíeFfHfgfvf,†f
³f$¾f&ãf
g(g :g[g dg ng1zg¬g½gÅg#Õgùg
h
h h*h3h 9h
EhPh`huhŽh«h¿hÓh"åhi %i2iDiIiQiWi[iri�i­iBÇi$
j2/j-bj�j¦j
j ÁjËj$Ójøj
üj
kk k06k#gk,‹k¸k½k'Ðk,øk %l1l5Pl †l “l8 l'Ùl'm')mQmHWm  m¬mIÁm# n//n"_n^‚n2án4o1Io${o o8¥o3Þo pp&1p$Xp}p�p žpªpÃpÒp5äpq+#q Oq[qdq
sq~q†q�q�q¸q5Ïqr;rPrXrgrxr‘r°rÄr¡Þr€s’s ¢s¯sÁs
Ûs$æs% t1t#Gtkt3|t2°tãt
õt u&u6u
;u.IuxuuH�uØu áu6íu
$v/v 6v @vLviv
ovzv+švÆvävõvw
w'w6w ;wHw=^w„œw‚!xD¤x»éx&¥y@Ìz)
{97{:q{9¬{%æ{? |eL|*²|®Ý|xŒ}~
!8
>Lirw<{
¸Æ Í×Þ.€H€c€%k€
‘€ œ€©€Å€&á€�$�-�
3�>�Q�e� m�
w�¦…�,‚B‚W‚`‚q‚‚‚œ‚¯‚ÂÕ‚é‚ú‚;ƒ=Kƒ‰ƒ˜ƒ§ƒǃçƒ(ýƒ&„A„&a„…ˆ„…
…
….…@…e^…Ä…Dä…)‡j1ŠCœ�Jà� +“�7˜ÒÅ�5˜ *Ρ´ù¨8®«%ç«3
­+A­#m­‘­™­©­¿­Ç­Э×­ß­ô­$ ®
1®<®!S®u®…®¡®
°®
»®É®yÏ®I¯"[¯%~¯¤¯¯á¯ô¯!°6%°\°!d°†°)˜°°QB±B”±,×±(²*-²<X²•²œ²®²'À²�è²x³‡³޳–³"¯³Ò³Ù³ë³/ó³#´(6´_´y´‰´¤´SÀ´4µIµXµ*sµ-žµ̵Ôµ çµôµúµ
"¶!-Ooˆ¶]�"û¶+·/J·,z·<§·:ä·D¸*d¸-�¸½¸Ó¸å¸#õ¸¹)2¹ \¹f¹~¹7—¹$Ϲô¹º(ºHº?aºK¡ºQíºL?»Œ»
•»£» À»Í»Õ»
ô»ÿ»!¼1¼C¼S¼
\¼j¼~¼š¼µ®¼d½k½|½"”½·½ƽÖ½ܽî½¾¾?-¾m¾¾
‘¾œ¾ ¤¾ ®¾Ͼß¾Fú¾A¿#W¿{¿˜¿6´¿Uë¿NAÀY�ÀPêÀ ;Á\Á-nÁœÁ¼ÁÓÁäÁ<õÁ 2 >ÂHÂ3\ �ÂUšÂzðÂkÃ!‚Ã3¤Ã-ØÃÄÄ5Ä)PÄ(zÄ1£Ä'ÕÄýÄÅÅ,Å5ÆDÆIÆXÆ ^Æ
jÆJxÆIÃÆ
ÇÇ&4Ç([Ç,„Çm±ÇdÈ„ÈŒÈ  È ªÈ´ÈÍÈÖÈ ìÈ5öÈ,É#>ÉHbÉ«ÉÉÉÛÉDùÉ>Ê$QÊ#vÊ$šÊ¿Ê-ØÊË
Ë#Ë<:ËwˉË�Ë'¡ËÉËàËðËÌ
ÌÌ"Ì;Ì DÌQÌ$mÌ’Ì ¥ÌÆÌÝÌïÌ*Í9ÍHÍ^ÍeÍuÍ{Í�Í&›Í*ÂÍíÍG
Î,UÎA‚Î.ÄÎóÎ
Ï Ï $Ï.Ï&=ÏdÏkÏ~Ï ‘Ï�Ï>ºÏ-ùÏ0'ÐXÐ]Ð*tÐ4ŸÐÔÐäÐDùÐ>ÑNÑ?`Ñ& Ñ,ÇÑ0ôÑ%ÒD+ÒpÒyÒQ�ÒáÒ'ûÒ%#ÓeIÓ@¯ÓFðÓ37Ô6kÔ¢Ô=©Ô=çÔ%Õ <Õ-]Õ,‹Õ¸ÕÏÕ ãÕðÕ
ÖÖ:<Ö wÖ�Ö
�Ö «ÖµÖÉÖ
ØÖãÖìÖ$×!'×:Iׄ×?›× Û×ç×ú×
Ø!)ØKØ.eØ“”Ø(ÙFÙZÙkÙÙ œÙ0©Ù4ÚÙÚ#(ÚLÚIfÚ?°ÚðÚ Û!Û*5Û`ÛhÛ=wÛµÛÇÛmÞÛLÜ[Ü9jÜ¤ÜªÜ ±Ü»Ü ÊÜëÜ
òÜ%Ý2&Ý$YÝ~Ý7˜ÝÐÝ×ÝîÝÞ ÞÞR8Þ^‹ÞeêÞ6Pß·‡ß?àK]á0©áEÚá: â5[â‘âM°âdþâc㜀ã|䳚ä Nå"Zå}åƒå$˜å
½åËåÐåMÔå"æ 4æ@æ
Pæ[æuæ�æ¨æÇæææ
ç+ç=çMçbç%‚ç-¨ç)Öçèèè!è!=è_è hè uè�‚èé!éAéJé^éréˆéŸé·éËéäéøé:ê<MêŠêžê¸ê#Öêúê,ë)Bë'lë"”ë…·ë=ìCìWìsì"ŠìH­ì"öìÞQJ1õTm>¿#ðS*%¨mŽÒ&:Ù…>Ë— ¦°¾FHìÕÔ„[hUx!ZH?ý¥jÉ9Ý'Ÿš¡“èpkv¡?`@êÿ�q
O{&·×÷†._@‡o¥Ì*[K"u«�9asÎØ�qÀNIy€í…á±À‘dY£¬çˆ‰gÞXjF›·Žg¾žœaø¯™~È/=ƒ¼ˆUÂ6µÐhbòO�,n²©ƒAÅÛWM´�Ù§7‘¦äW­4 ©v;‹Bx¸)/$Ѫ3سVºÐ“Gi§R\ {Ñ¢Š|ú€0ÛNÍY7ù3n´lÉ‹tfC+âÂKÔbžÃZEÄk™<]2~ÆþÊÊLQCñ”¢£=˼wÚû‡ul8Áе’Ä”%;Î0r^ }Á
ŒÏ `2\z^V
|�ÝT¤ÅÆÓãÇ• cºr®RX-}M¯5Õ8L³'˜Ö6cÈSÇÌ‚ëPe½1ô(—–4)« sšÜ†dPGzà’+Ó à¹#²ßEI‚�ߪ,›¸�˜¬Í üéA�­o!®<Œ„-»]½ y�D._¤Ü¹tåiæ¿$Ú»:–œ°ÃÖp
‰ïöÒD¨eó±J5(wBfÏ×"
<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>
2025-12-29 18:30:39 -03:00
<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>
<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-12-29 18:30:39 -03:00
2026-01-16 15:01:13 -03:00
<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>
<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>
2025-12-29 18:30:39 -03:00
<h5>Restart Mode</h5>
<p>Choose whether WireGuard services should be automatically restarted when configurations change, or if manual intervention is required.</p>
<h5>Worker Display</h5>
<p>Select how workers should be identified in the interface - by name, server address, location, or a combination.</p>
<h5>Peers</h5>
<p>Select which peers can be managed by users with this peer group.</p>
<h5>WireGuard Instances</h5>
<p>All peers in this WireGuard instance can be managed by users with this peer group, including adding or removing peers.</p>
<h5>Routing Templates</h5>
<p>Define routing configurations that can be applied to peers.</p>
2026-01-27 15:08:59 -03:00
<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>
2026-01-27 15:08:59 -03:00
<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>
<p>When enabled, the worker can only connect from the specified IP address.</p>
<h5>Location Information</h5>
<p>Optional location details for this worker (country, city, hostname).</p>
(Share this password via a separate secure channel)<h2>Welcome to Your VPN Setup</h2>
<p>Begin by downloading the WireGuard app for your device using one of the links below.</p>
<p>Once installed, you can either <strong>scan the QR code</strong> or <strong>download the configuration file</strong> to quickly import your settings and start using your secure VPN connection.</p>A peer can have only one IP with priority zero.A peer group with that name already exists.A worker with that name already exists.ACCEPTAccess DeniedAccess PasswordActionActionsActiveAddAdd Client routeAdd Filter ListAdd Forward Rule (allow)Add IP AddressAdd Peer GroupAdd Routing TemplateAdd 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 fileApplyApply Route TemplateApply templateAre you sure you want to create a new peer?At least one address does not appear in the wg show command output, which may indicate that another peer is using an overlapping IP or that the configuration file is outdated.At 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 CountCannot 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 serviceConsoleConsole EnabledCopy TextCountryCreate Firewall RuleCreate InstanceCreate PeerCreate Port forwarding RuleCreate a new WireGuard InstanceCurrent Active Template:Custom RoutesCustom routes should be empty when Route Type is 'Default Route'.DNS 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 WireGuard InstanceDescriptionDestinationDestination Hostname or IP AddressDestination IPDestination PeerDestination Peer Include NetworksDestination PortDestination TypeDigitsDisabledDisplay NameDisplay automatic rulesDownload ButtonsDownload the WireGuard app for your device using one of the links below. After installation, you can scan the QR code or download the configuration file to import on your device.EditEdit InstanceEdit Peer Group: Edit Routing Template: Edit UserEdit Worker: EmailEmail EnabledEmail MessageEmail Message TemplateEmail SettingsEmail Settings|Settings saved successfully.Email SubjectEmail or phone numberEnabledEncryptionEndpointsEnforce Route PolicyEnhanced FilterEnhanced Filter EnabledEnhanced fil
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 InterfaceInstanceInstance IDInstance TrafficInterfaceInternal IP AddressInvalidInvalid Destination. Either Peer or IP Address must be informed.Invalid commandInvalid config fileInvalid confirmation|Please confirm deletion of WireGuard instance: wgInvalid hostname or IP AddressInvalid targetInvite SettingsInvite Settings|Settings saved successfully.Invite URLInvite URL must end with '/invite/'.Invite URL must start with 'https://'.Invite data is not available.Invite refreshed.Invite text copied to clipboard.LanguageLast 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 templatesNameNetmaskNeverNewNew 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 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 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 KeyProtocolPublic AddressPublic KeyQR CodeREJECTRandom PasswordRandom Password ComplexityRandom Password LengthRandom password length must be at least 6 characters.Refresh InviteReject traffic to private networks exiting on WAN interfaceRelatedReload EnabledReload WireGuardReload Wireguard serviceRemove VPN i
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>
2025-12-29 18:30:39 -03:00
<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>
<h5>Enmascarar origen</h5>
<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>
2025-12-29 18:30:39 -03:00
2026-01-16 15:01:13 -03:00
<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>
<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>Modo de Cluster</h5>
<p>Configure cómo opera el cluster y sincroniza las configuraciones entre nodos.</p>
<h5>Intervalos de sincronización</h5>
<p>Configure con qué frecuencia se sincronizan las estadísticas y los datos de caché entre los nodos del cluster.</p>
2025-12-29 18:30:39 -03:00
<h5>Modo de reinicio</h5>
<p>Elija si los servicios WireGuard deben reiniciarse automáticamente cuando cambien las configuraciones, o si se requiere intervención manual.</p>
<h5>Visualización del worker</h5>
<p>Seleccione cómo deben identificarse los workers en la interfaz: por nombre, dirección del servidor, ubicación o una combinación.</p>
<h5>Peers</h5>
<p>Selecciona los peers que pueden gestionar los usuarios de este grupo.</p>
<h5>Instancias de WireGuard</h5>
<p>Todos los peers en esta instancia de WireGuard pueden ser gestionados por usuarios de este grupo, incluyendo añadir o eliminar peers.</p>
<h5>Plantillas de Enrutamiento</h5>
<p>Defina configuraciones de enrutamiento que se pueden aplicar a los pares.</p>
2026-01-27 15:08:59 -03:00
<h5>Plantilla Predeterminada</h5>
<p>Si está marcado, esta plantilla será la predeterminada para la instancia WireGuard seleccionada. Solo se permite una plantilla predeterminada por instancia.</p>
<h5>Tipo de Ruta</h5>
<p>Seleccione el tipo de rutas para enviar al cliente.</p>
<ul>
2026-01-27 15:08:59 -03:00
<li><strong>Ruta Predeterminada (0.0.0.0/0)</strong>: Redirige todo el tráfico a través de la VPN.</li>