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

382 lines
75 KiB
Modelica
Raw Normal View History

2026-02-10 10:55:39 -03:00
Þ•^ )ü% 2½¡2¢_5S9mV;Ä>ÞÝ?~¼A‚;Bw¾B6C3TDƒˆEª KÖ·P€ŽRUI,V]v\OÔ^3$_FX_/Ÿ`+Ï`'û`#a*aHada
ma{a‹a’aša¡a ¥a±aÂaÒaëa úab b"b7bIbRb
ibtb
|bŠb‰Žb c
%c3cNcgc zc
‡c•c³c ÉcÕc çc'dQ0d‚dˆd�d+¬d7Ød7e3He¯|e@,f2mf6 f6×fg1,g^g{g €g�gŸg
³gÁgßgqægXhhhmhsh‚h‘h®h
´hÂhÊhèh!øhi .i;iLi;ci&ŸiÆiÍiÜi%ûi!j0j8j HjRjZjoj j‹j§j¿jßj øj
kAkUkgk$k%¤k$Êk4ïk2$l2Wl"Šl$­lÒlãl òlþlm!,mNmSmem,mmšm±mÂmÑmëm4ümC1nJunFÀnoo o)oAoVo po |o"ˆo«oºo!Ëoíoþoppp.pKp`p up‚pšp²«p^qcq
rq€q �q ™q£qµqÄqÜqòq r
rr
#r
1r?rVr+er
‘rŸrµr
½rËr
ßrêròr ûrss*s:Bs}sŽs­sÃsDÚsWtQwt_ÉtK)uuuŽužu»uO×u'v<vKv;Zv –vY¢v
üvw0w
MwWXw°w0xEx%ex‹x©x¸xËx"Ýx y$!yFy(cy+Œy#¸yÜy ãyðyøy& z 0{<{A{J{ P{
]{Ah{/ª{Ú{â{/ò{3"|3V|WŠ|câ|F} I}V}_} h}t} …}�}ž}²}Ã}@Ë} ~~,~F@~‡~¦~O¸~,'
T$_&„«É Ûü€
€ €1 €R€c€k€#{€Ÿ€´€Å€
΀ Ù€å€î€ ô€
� ��0�I�f�ƒ�—�«�"½�à� ý�
‚‚#‚(‚0‚6‚:‚ Q‚ ^‚ j‚ w‚ƒ‚†‚£‚Á‚BÛ‚$ƒ Cƒdƒ2zƒ­ƒɃ-⃄&„
6„ A„K„$S„x„
|„ Š„—„ „0¶„#ç„, …8…=…P…'e…,�… º…Æ… å…5ï… %†
2†
@† K†8X†'‘†'¹†á†<‡-=‡k‡:ˆ‡4Ç'ø‡ ˆH&ˆ oˆ{ˆI�ˆ#Úˆ/þˆ".‰^Q‰2°‰4ã‰1Š$JŠoŠ8tŠ3­Š áŠîŠ&‹$'‹L‹^‹ m‹y‹’‹¡‹5³‹é‹+ò‹ Œ *Œ7Œ@Œ
OŒZŒbŒiŒpŒ€Œ›Œ5²Œ
èŒóŒ��;"�^�f�u�†�Ÿ�¾�Ò�¡ì�ŽŽ Ž °Ž½ŽÏŽ
éŽôŽ$
�%/�U�#k���3 �2Ô��
� '�&3�Z�c�h�&q�$˜�½�Ï�æ�‘D‘\‘Fp‘ ·‘
Á‘.Ï‘þ‘’H’^’
g’ r’6~’
µ’À’ Ç’ Ñ’Ý’ ú’
““
“ “+@“l“Š“›“¸“¿“Æ“Γ è“ ô“
þ“ ”” ”-”=C”„�”‚•D‰•»Î•&Š–@±—Nò—GA˜)‰˜9³˜Ií˜:7™9r™%¬™?Ò™eš5xš*®š®Ùšxˆ›œF�
N�Y�#b�!†�¨�!·�Ù�ß�
ÿ�
ž*ž3ž;ž@ž<Dž9�ž
»žÉž ОÚžážòžŸŸ1ŸKŸfŸ%nŸ
”Ÿ ŸŸ¬ŸÈŸ&äŸ  ' 0 
6 A T h  p 
z ¦ˆ /¡E¡ Z¡d¡m¡~¡�¡©¡¼¡Сâ¡ö¡¢;¢=X¢–¢¥¢´¢Ô¢ô¢(
£3£N£n£&r£…™£¤
#¤
1¤?¤Q¤eo¤Õ¤Aõ¤ë7¦Q#©Du¬Rº®3
²A³ŠTµžßµ‡~¶:·PA¸›’¹d.¿ “Å´Ç7ÌÊ)̯.Ó\ÞÕ;;Ö‘wÖ; Ø0EØ$vØ›Ø#¤Ø%ÈØ îØúØ Ù!Ù(Ù0Ù6Ù>ÙUÙnÙ"‹Ù®ÙÅÙÛÙöÙÚ&ÚEÚ\Ú{ÚŠÚ’Ú¡ÚЦÚ1ÛIÛ[Û.{ÛªÛÂÛÜÛ&öÛÜ5ÜEÜ%[Ü2�Üx´Ü -Ý7ÝWÝ/lÝ?œÝ;ÜÝ>Þ­WÞTßFZßL¡ßDîß(3à8\à)•à¿àÆàÙàêà
ýà/ á;á•CáÙáëáñáùáâ"!âDâKâ]â'eâ�â,�âÊâæâöâ
ãJ*ã0uã¦ã­ã,Æã.óã"ä;äCäVäfäkä‹äŸä(®ä!×ä&ùä å7åFå`]å¾å#Ðå,ôå.!æ*Pæ;{æ;·æ>óæ.2ç.aç�ç¦ç·çÆçæç'è
-è8èNè5dè"šè½èÖèìè
éBéaaéYÃédê ‚êŒê¤ê$¶êÛê ûê ë (ë*4ë_ëqë(…ë®ëÂëÖë ßëëë&þë %ìFìdì!tì–ìݲì�í™í³íÇíÝíðíîî 7î#Xî|î›î´îÇîÐîáîòîï=#ïaï"wïšï¢ï±ï Ëï ×ï ãïðï!ð(ð7ðENð”ð*­ð.Øð.ñG6ñl~ñfëñnRò\Áò3óRó;ió1¥óq×ó)IôsôˆôT�ôòônúô
iõtõ@‰õ ÊõiÔõ‡>öÆö3ãö9÷4Q÷†÷œ÷¼÷,Ö÷.ø32ø#fø1Šø2¼ø,ïøù%ù @ùJùlaùÎúáú
çúõú üú
ûQû@fû§û·û$Ïû-ôû0"ügSüp»ü,ý4ýGýOýXýký ‚ýŒý¡ý´ýÄýCÍýþ"þ!4þWVþ$®þÓþ]éþGÿVÿCqÿµÿ;Èÿ94>s5‹ÁÇÎâAù;MU(g�¤ÀÐè ù 
)?$^#ƒ)§Ñï$!$Fk†š ¤«²ºÖï2"6#Y}Bš,Ý
(9>&x"Ÿ@Â -
: E%Qw~‘ ¡®KË:6R‰Ž¤,¼+é&FTV«Á
ÔâMñ'? -g • H³ 9ü 6
FR
:™
1Ô
 P 
] k `ƒ ,ä : 'L ct =Ø 9
1P
6‚
¹
@¾
2026-01-27 15:22:12 -03:00
9ÿ
9M-l/šÊã ù"):CV š3¤ Ø
å óý
$,3&K#rM–
äïI3}…œ°$Ïô°+Üö
" 8
Yg*‡*²Ý'ö;17m¥¹Ê1Ñ

/!1Qƒ!œ$¾ãO÷GR^
±¿8Îs) �©¼HÐ & 0#<`o …,’0¿%ð91kr {…¤¹ÂÑâ
èöX’h‘ûJ�ÂØ0›GÌbNwEÆH NU=¤Aâ5$ NZ q© A!8]!Ç–!‹^"ñê"KÜ#($/$+5$-a$�$'¤$Ì$ Ò$ó$&% .%8%>%C%VG%Sž%ò% & &&%&=&]&%r&&˜&(¿&è&3÷&+'>''W'-'0­'1Þ'( $(1(@(!_(�(
‰(
—(›¥(A) ])~)‡)�)¡)²)Î)á)õ) *&*7*=P*AŽ*Ð*à*ô*$+8++T+&€+(§+Ð+*Ô+‘ÿ+‘,–,¨,·,,Ê,^÷,"V-0P¢ü+P)œ½�p-6ËL™—µs-?5¾A®rÇí�ݱÔG-$='@ e…µß£…1*Ñ·W Dôóœ©W†ÀV»�.+ƒ¢GƺCiAèÜF@�˜¹nhqt[¿c&›y^ÈÊàª
±ÚžÞö®R|⼕An(™�ŒS%^†‘,89’Øê“¦ÅQãu劂û¿YÏÐ0~J<Í'ë‡D"_JðIá{/Y'i›#(î* vð^Ä5M86•¤óìBC}¬k/ÃÊT 7úc ´K÷Z1!3;ü@sX? b}oj\|ÀÅÓø–ø]4O2hVd¬oUS¤ÞkZÁâ;TGÎ=äÙEªYÜÇa²gêK>áfzÄf½ˆX2%xLýM\õ–I­zN˜Ö]NöM7:LÒ×`1Ï+Ž>„tT)4£[8ù‡ÿاOu´
Û
ñ¡BéÖþEb79
ï»Õù :S0&”¸õ:lÈ­ ßwE  Ìg#�ˆ\¼*ôq¯ý·,Ƒ‚É÷ÝC�’{Á$ «~Vç]ÉÑÙç;U¡ƒË9/!¥OU =.§FQ€ñ?Ô«°<_„H5)vwÒíº²©.¾3<Ћ
åNHú¦>3 mŽÌQ°"Í"þ2%p³“š€òaRÓdHò¨By—èŸ�K[Îj” (�!,æ`�ûé#³ælÕI‰DŸ¸rìRïPšm6×¹xãZèX늌¯Je$Úä
ÿàW&ÛF‹4‰
<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
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.
Interval used to refresh WireGuard status information in the web UI.
Optional name used only for display in the web interface.
2026-02-09 22:07:48 -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.
2025-12-29 18:30:39 -03:00
<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>
<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>
2025-12-29 18:30:39 -03:00
2026-01-16 15:01:13 -03:00
<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>
<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>
2025-12-29 18:30:39 -03:00
<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>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>
<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>
2026-01-27 15:22:12 -03:00
<p>Select how workers should be identified in the interface - by name, server address, location, or a combination.</p>
2026-02-10 10:55:39 -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>
2026-02-10 10:55:39 -03:00
<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>
<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>
2026-01-27 15:22:12 -03:00
'%(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 Key deleted successfully.API Key saved successfully.API KeysAccess DeniedAccess PasswordActionActionsActiveAddAdd API KeyAdd 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 ExportAllow ForwardAllow Instance to InstanceAllow Peer Custom RoutesAllow Peer to PeerAllow ReloadAllow RestartAllow traffic from VPN to WANAllowed 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 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 trafficAutomatic rule: Route PolicyBackBack to ListBecomes active atBecomes inactive atCache 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 Firewall RuleCreate 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 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 API KeyDelete PeerDelete Schedule ProfileDelete Time IntervalDelete WireGuard InstanceDescriptionDestinationDestination Hostname or IP AddressDestination IPDestination PeerDestination
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 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 PortLocationLoginLogin againMASQUERADEMain ip addressManage Firewall RuleManage Firewall SettingsManage IP address or NetworkManage Peer Schedule ProfileManage Port ForwardManage client routeMasquerade SourceMasquerade traffic from VPN to WANMaster Cache Processing TimeMemory usageMessage templatesMondayNameNetmaskNeverNewNew WireGuard InstanceNext DisableNext EnableNext disableNext enableNoNo 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 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 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 reactivated successfully.Peer reactivated, but failed to reload WireGuard interface: Peer scheduling profile updated successfully.Peer suspended successfully.Peer suspended, but failed to reload WireGuard interface: Peer suspension/unsuspension scheduled 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
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>Configuration avancée du pare‑feu VPN</h5>
<p>
Cette interface est un outil complet de gestion des règles de pare‑feu ; elle permet de définir des politiques de trafic avancées entre pairs VPN et réseaux. Elle simplifie la création de règles, le filtrage de paquets et les configurations NAT afin d’offrir un contrôle précis sur la sécurité. Les utilisateurs peuvent spécifier adresses IP source et destination, ports, protocoles et actions pour ajuster le flux de trafic, garantissant ainsi un environnement réseau sûr et efficace.
</p>
<h5>Sélection de la destination</h5>
<p>
Cette règle peut s’appliquer à une adresse IP ou à un réseau précis et/ou à plusieurs peers comme destination.<br><br>
« Inclure les réseaux du peer » ajoute automatiquement toutes les IP autorisées de chaque peer sélectionné en destination.<br><br>
Le choix de plusieurs peers avec réseaux inclus en source et destination peut générer un grand nombre de règles.<br><br>
L’option « Non‑destination » annule la destination IP, le réseau ou le/les peer(s) sélectionné(s).
</p>
<h5>Protocole et port</h5>
<p>
Seuls les protocoles les plus courants sont listés. Si vous en avez besoin d’un autre, ouvrez une issue sur GitHub.<br><br>
Choisir TCP+UDP dupliquera les règles générées.<br><br>
Les ports peuvent être indiqués individuellement (ex. 8080) ou en plages (ex. 8001:8999).
</p>
<h5>Sélection de la source</h5>
<p>
Vous pouvez appliquer cette règle à une adresse IP ou un réseau précis et/ou à plusieurs peers.<br><br>
L’option « Inclure les réseaux du peer » ajoute automatiquement toutes les IP autorisées associées à chaque peer sélectionné.<br><br>
Attention: choisir plusieurs peers avec réseaux inclus en source et en destination peut rapidement augmenter le nombre de règles générées.<br><br>
L’option « Non‑source » annule la source IP, le réseau ou le/les peer(s) sélectionné(s).
</p>
Serveurs DNS poussés vers les pairs.
<br>
L'utilisation de l'IP interne comme DNS primaire permet la résolution de noms interne
et le filtrage DNS.
Applique les règles de routage définies par les modèles de routage à l'aide de règles de pare-feu.
<br>
Les pairs avec une route par défaut (0.0.0.0/0) ne sont pas restreints.
<br><br>
Remarque : selon le nombre de routes et de pairs, cette option peut générer
un grand nombre de règles de pare-feu.
Adresse IP interne et masque de réseau utilisés par l'interface WireGuard.
Intervalle utilisé pour rafraîchir les informations d'état de WireGuard dans l'interface web.
Nom facultatif utilisé uniquement pour l'affichage dans l'interface web.
2026-02-09 22:07:48 -03:00
Nom d'hôte public ou adresse IP et port UDP utilisés par les pairs pour se connecter.
<br>
Le <b>port d'écoute</b> doit être exposé et mappé dans votre fichier Docker compose (YAML).
Clés privée et publique WireGuard pour cette interface.
2025-12-29 18:30:39 -03:00
<br>
La clé privée doit rester secrète.
Le changer nécessite la mise à jour de toutes les configurations des pairs.
<h5>Ports par défaut</h5>
<p>Le fichier <code>docker-compose.yml</code> par défaut définit la plage de ports <b>TCP</b> <b>8080‑8089</b>. Si vous souhaitez rediriger vers une autre plage, modifiez ce fichier manuellement, puis relancez l’étape Docker Compose décrite dans les <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">instructions de déploiement</a>.</p>
<h5>Type de destination: Peer</h5>
<p>La redirection de port privilégiera la première adresse IP du peer dont la priorité est zéro.</p>
<h5>Type de destination: Adresse IP</h5>
<p>Les règles de transfert de port pointeront vers l’adresse IP spécifiée. N’oubliez pas d’associer cette IP ou ce réseau à un peer.</p>
<h5>Ajouter une règle Forward</h5>
<p>Génère automatiquement une règle de transfert afin de respecter des paramètres de pare‑feu plus stricts.</p>
<h5>Masquer l’adresse source</h5>
<p>Solution temporaire lorsque le peer n’utilise pas le VPN comme passerelle par défaut. Cette configuration est déconseillée, car elle remplace l’adresse source de toutes les connexions par l’IP de l’instance WireGuard.</p>
<h4>Niveaux d’utilisateur</h4>
<h5>Analyste de débogage</h5>
<p>Accès aux informations système de base et aux journaux pour le dépannage. Aucun droit de modifier les paramètres ni de consulter des données sensibles (comme les clés des peers).</p>
2025-12-29 18:30:39 -03:00
2026-01-16 15:01:13 -03:00
<h5>Lecture seule</h5>
<p>Droit de tout visualiser, y compris les clés des peers et les fichiers de configuration. Impossible de modifier quoi que ce soit.</p>
<h5>Gestionnaire de peers</h5>
<p>Peut ajouter, modifier et supprimer des peers et des adresses IP, sans toutefois modifier la configuration des instances WireGuard ni d’autres paramètres avancés.</p>
<h5>Gestionnaire WireGuard</h5>
<p>Autorisé à ajouter, modifier et supprimer les configurations des instances WireGuard.</p>
<h5>Administrateur</h5>
<p>Accès complet au système: peut consulter et modifier tous les paramètres, configurations et gérer les utilisateurs.</p>
<br>
<h4>Groupes de peers</h4>
<p>Sélectionnez les groupes de peers accessibles à cet utilisateur. Sans sélection, il aura accès à tous les peers.</p>
<h4>Console</h4>
<p>Activer ou désactiver l’accès à la console Web pour cet utilisateur.</p>
<h4>Filtre avancé</h4>
<p>Limite la réponse de l’API aux seuls peers autorisés pour l’utilisateur. Selon la taille de votre environnement, cette option peut affecter les performances. Pour compenser, augmentez éventuellement l’« intervalle d’actualisation Web » afin de réduire le nombre de requêtes.</p>
<h5>Clés d'API</h5>
<p>Les clés d'API permettent à des applications externes d'interagir com a API do WireGuard WebAdmin.</p>
2025-12-29 18:30:39 -03:00
<p><strong>Token:</strong> Le jeton secret utilisé pour l'authentification. Gardez-le en sécurité.</p>
<p><strong>Instances autorisées:</strong> Les instances WireGuard que cette clé peut gérer. Si aucune n'est sélectionnée, la clé a accès à TOUTES les instances.</p>
<p><strong>Permissions:</strong> actions spécifiques autorisées pour cette clé.</p>
<h5>Mode de cluster</h5>
<p>Configurez le fonctionnement du cluster et la synchronisation des configurations entre les nœuds.</p>
<h5>Intervalle de synchronisation</h5>
<p>Configurez la fréquence à laquelle les statistiques et les données de cache sont synchronisées entre les nœuds du cluster.</p>
<h5>Mode de redémarrage</h5>
<p>Choisissez si les services WireGuard doivent être redémarrés automatiquement lorsque les configurations changent, ou si une intervention manuelle est requise.</p>
<h5>Affichage du worker</h5>
2026-01-27 15:22:12 -03:00
<p>Sélectionnez la manière dont les workers doivent être identifiés dans l’interface - par nom, adresse du serveur, emplacement ou une combinaison.</p>
2026-02-10 10:55:39 -03:00
<h5>Peers</h5>
<p>Sélectionnez les peers que les utilisateurs de ce groupe peuvent gérer.</p>
<h5>Instances WireGuard</h5>
<p>Tous les peers de cette instance WireGuard pourront être gérés par les utilisateurs du groupe, y compris l’ajout et la suppression.</p>
2026-02-10 10:55:39 -03:00
<h5>Modèles de Routage</h5>