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

527 lines
106 KiB
Modelica
Raw Normal View History

2026-11-16 10:25:20 -03:00
Þ•D<]\4ÐE½ÑE¢�HS2Lm†NôQÞ
S~ìT‚kUwîUfV3„Wƒ¸Xx<^µ^šÇ`ñbaTdªpgÖm\ònŽOr€Þt&_w†zI£{]í�OK„3›„FÏ„/†+F†'r†š†¡†³†цí†
ö†‡‡#$‡!H‡j‡q‡y‡€‡ „‡�‡¢‡µ‡LJׇ쇈ˆ#ˆ3ˆ LˆVˆ_ˆ nˆ{ˆ Šˆ –ˆ ˆµˆLjЈ
çˆòˆ
úˆ‰‰ ‰–‰ œ‰
©‰·‰Ò‰ë‰ þ‰
Š0Š?JŠ%ŠŠ°Š$Ί"óŠ#‹!:‹\‹u‹„‹ š‹¦‹ ¸‹'Ù‹QŒ SŒ0_Œ.�Œ¿Œ&ÓŒ$úŒ�'1�%Y��!’�´� Ô�á�ç�ü�+ Ž77Ž=oŽ=­Ž@ëŽ>,�;k�E§�5í�8#�7\�@”�8Õ�3‘[B‘Bž‘¯á‘@‘’RÒ’2%“ X“ d“q“€“+–“)“ì“” ”68”6o”¦”1Ä”ö”• •%•7•
K•Y•w•Œ•q“•l–vr–Sé–A=—H—7È—˜4˜E˜J˜P˜_˜n˜‹˜
‘˜Ÿ˜§˜Ř!Õ˜÷˜ ™™)™;@™&|™£™ª™œ¹™$Vš{š%ššÀšÏšàšèš øš›
››2›O›d›|›“› £›¯›Ë›ã›œ œ
)œA7œyœ‹œ$£œ%Èœ6îœ$%�4J�2�>²�2ñ�0$ž"Už$xž�ž®ž ½ž)Éžóž
Ÿ!!ŸCŸHŸOŸaŸiŸ,xŸ¥Ÿ¼ŸÍŸÜŸöŸ4 C< J€ FË ¡¡(¡=¡S¡h¡!{¡�¡µ¡Ρë¡¢¢ ,¢8¢P¢e¢¢„¢�•¢ £ #£"/£R£a£!r£”£¥£¶£½£Æ£Õ£ò£¤ ¤)¤A¤H¤²Y¤ ¥¥ ¥3¥G¥Z¥k¥‹¥¡¥¸¥Ó¥é¥þ¥
¦¦ +¦ 5¦?¦Q¦`¦x¦ަ ¡¦
«¦¹¦
¿¦
ͦÛ¦ò¦+§
-§;§Q§
Y§g§
{§†§ާ —§¡§¶§Ƨ:Þ§¨*¨OI¨<™¨Ö¨ì¨D©>H©W‡©Qß©_1ªK‘ªݪ÷ª« «=«OY«©«¾«Í«;Ü« ¬Y$¬~¬†¬
�¬š¬0¯¬
à¬ë¬5­W6­Ž­®#®%C®i®‡®–®©®"»® Þ®$ÿ®$¯(A¯+j¯#–¯)º¯ä¯ë¯ ò¯&ÿ¯$&°%K°#q°•°¦°®°¿°Ô°
ç°ò°&ù° ²,²1²%:²`²f² n²
{²†²A–² ز/ù²)³ H³U³]³/m³3�³3ѳW´]´cf´Ê´ Í´Ú´ã´ ì´ø´ µµ"µ6µGµ@Oµ�µ:¢µݵíµýµFXwO‰¶Ù¶è¶,ø¶
%·$0·&U·|·š· ¬·Í·Ò· Û· å·1ñ·#¸4¸<¸#L¸p¸…¸–¸
Ÿ¸ ª¸¶¸Ÿθ Ô¸
à¸ë¸û¸¹¹0¹M¹j¹~¹’¹"¤¹ǹä¹ ì¹ù¹_ ºkºˆº�º”ºœº¢º¦º ½º ʺ Öº ãºïºòº# »0» G»h»„»)Ÿ»É»Ù»*ð»¼8¼V¼Bp¼$³¼ ؼù¼2½B½^½-w½¥½»½
˽ Ö½à½è½÷½
¾J¾<g¾2¤¾$×¾ü¾@¿V¿n¿„¿Š¿
Ž¿ œ¿
©¿´¿½¿0Ó¿<À#AÀeÀ,{À4¨À*ÝÀ4Á=Á UÁ"aÁ(„Á­ÁÌÁÑÁäÁ'ùÁ,! NÂZ yÂ5ƒÂ ¹Â
ÆÂ
Ô ßÂ8ìÂ'%Ã'MÃ,uâÃ<ÁÃ-þÃ,Ä:IÄ4„Ä'¹ÄáÄHçÄ0Å IÅUÅIjÅ9´Å#îÅ/Æ1BÆ"tÆ^—Æ2öÆ4)Ç1^Ç$�ÇµÇ ¼ÇÈÇ8ÍÇ3È :ÈGÈ&YÈ$€È¥È·È
ÆÈ?ÔÈ É É9ÉHÉ5ZÉ�É+™É ÅÉ ÑÉ ÞÉèÉñÉøÉ
ÊÊÊ!Ê(Ê8ÊSÊ5jÊ
 Ê«ÊºÊÉÊ;ÚÊËË-Ë>ËWË9v˰˹ËÍË¡çË‰Ì›Ì «Ì¸ÌÊÌäÌ
ìÌ
÷ÌÍ$Í%=ÍcÍjÍ#€Í¤Í3µÍ2éÍÎ
.Î <Î&HÎoÎxÎ}Î&†Î$­ÎÒÎäÎûÎÏD,ÏqÏF…Ï ÌÏ
ÖÏäÏëÏ.Ð4Ð;ÐHKДÐ"§ÐÊÐ
éÐôÐýÐ
Ñ &Ñ62Ñ
iÑtÑ {Ñ …Ñ‘Ñ ®Ñ
¸ÑÃÑ
ÉÑÔÑ+ôÑ Ò>ÒOÒlÒsÒzÒ‚Ò œÒ ¨Òj²ÒÓ "Ó.Ó0BÓAsÓ<µÓ2òÓD%Ô:jÔ
¥Ô³ÔÂÔ ÇÔÔÔ=êÔ¬(Õ„ÕÕ‚ZÖDÝÖ5"×6X×»�×&KØ@rÙN³ÙGÚ)JÚ9tÚI®Ú:øÚ93Û%mÛ?“ÛeÓÛ59ÜEoÜ*µÜ®àÜ"�Ý#²ÝxÖÝ+OÞ{ÞF�ß(Èß
ñßüß#à!)àKà!Zà|à�à“à
³àÁàÞàçàïàôà<øà95áoátá
|áŠá ‘á �á§á¸áÍáÝá÷áâ,â4â#=â0aâi’â%üâ
"ã -ã:ãVã@rã&³ãÚãöãÿã
ää#ä7ä ?ä Iä
Vä¦dä å!å 6å@åIåZåkå…å˜å¬å¾åÒåãå;øå=4æræ�æ�æ°æÐæ(ææç*çJç&Nç…uçûç
2025-08-12 08:54:05 -03:00
ÿç
èè -èNèelèÒè�òèû€êŒ|ív ñx€ó&ùöÿ ø… ú§¦ú…NûKÔûQ ý£rþ“Sª£þh¢¬ ȸ�®�ÈLºoÐ U@$ã–%¢z,Q/9o/t©/61+U1%�1§1¯1$Á1$æ1 22-2@2/S2,ƒ2°22¼2Å2Í2á2ü23/3B3`3y3™3²3)È3ò344'484M4
\4j4‡4¡4¸4Õ4ä4ë4ú4‰5Œ5•5¥5!¼5Þ5ü5626)D6En6.´6"ã6.7+57,a7)Ž7¸7Ô7æ7ÿ78$(8+M8Uy8
Ï8<Ú899Q90j9-›9É9-ß9*
:8:'I:$q:
–:
¡:¬:Ê:.Ý:< ;2I;C|;9À;7ú;;2<=n<-¬<4Ú<7=6G=8~=2·=Lê=I7>¹�>@;?h|?9å?@7@O@_@4w@1¬@Þ@ö@-
AC8AD|A,ÁACîA*2B]BdB
uBƒB“BC³B÷BC{C~“C•D\¨DIENOE=žE
ÜE;êE&F,F5FDF"WFzFƒF”F.œFËF$ÝFGG'G:GISG,�G
ÊGØG­íG*›H&ÆH%íHI*I:IBITIeImIŠI!ŸIÁIÝI#úIJ3J'BJjJ$‡J¬JÊJÙJJèJ3KEK)dK*ŽK?¹K)ùK>#L8bLB›LHÞL;'M)cM.�M¼M ÏM
ÛM5æM N=N)VN€N ‰N“N¤N¹N6ÒN" O,O>OSOqO-‡OLµOUPLXP¥P®PÃPâPQQ+4Q!`Q‚Q#ŸQÃQ%âQR
R,RKRfR
„R�R—¬RDSJS)PS zS‡S –S·S
ÆS ÑS
ÛSæS$÷ST5TNT bTƒT‹TФTuU~U•U±UÌUæU(úU#VBV \V}V"™V¼VÏVãVöVWW/WEWeW�WœW´WÆWÍWÞWîW X7XVXfX †X�X X ¸XÄXÔX
äXòXY$YABY„Y%™Y^¿YKZ jZ ‹ZT¬ZB[eD[dª[}\_�\í\
] .]3O]'ƒ]N«]ú]^0^LG^ ”^y ^_ #_
-_8_/M_ }_‡_9¡_YÛ_~5` ´`+Õ`:a/<ala~a˜a*¬a*×a,b./b:^b=™b*×b&c)c1c8c/Pc,€c4­c1âcd .d:dQdkd„d“dV›dòe f f+f If Uf_f hfrfCƒf&Çf3îf#"g Fg PgZg5ng7¤gAÜgKhjh]shÑh×h
êh
õh
ii &i0iCiVi ei>oi®iHÂi jj.jINj+˜jÄjXáj:kJk9_k
™k+§k-Ók#l%l.Dlsl|l‚l”lA¬lîl m m'!mImbm vm‚m™m
ªm ¸mÄmÓm
èmóm
nn-n Ln#mn‘n±nÍn#Ýn-o /o9oKoY\ooÔoÝoäoôoúopp3pJpbpyp'}p2¥pØp,øp'%q.Mq?|q¼qÜq:ûq(6r)_r‰rW¨r&s2's ZsF{s(Âs'ës:t(Nt
wt
2026-01-27 15:22:12 -03:00
…t “t �tªtºtÎtKætC2u8vu&¯uÖuMðu>vZvpvxv€v •v ¡v«v±v9ÂvGüv.Dwsw!†w3¨w,Üw5 x?x Ux+bx(Žx)·xáxæxùx/y3?y sy€y
—y=¥y
ãy ñy
ýyz2z.Mz,|z2©zÜzYúz6T{‹{Y¨{8|6;|r|Jx|5Ã| ù|}F}<^}*›}8Æ}'ÿ}"'~^J~D©~Aî~>08o¨ ±¾7Ã7û3€H€6d€6›€Ò€ä€þ€@�
O�]�{�Œ�=©�ç�,ð�‚0‚
?‚J‚S‚\‚l‚}‚
…‚�‚˜‚¨‚Æ‚5à‚ ƒ#ƒ6ƒIƒ?\ƒ
œƒ§ƒƒ"݃"„D#„h„$q„+–„À„ƒ…’…¥…¶…Î…î… õ… † †.+†=Z†˜†ž†%¹†߆?ô†;4‡p‡…‡™‡%¨‡·Õ‡ Þ‡+ë‡+ˆCˆWˆqˆŒˆH§ˆ$ðˆH‰
^‰i‰y‰!�‰<£‰à‰ñ‰_ŠdŠ$xŠ)�ŠÇŠ
ÚŠ(劋‹=1‹o‹�‹ ‡‹”‹ £‹Ä‹Ó‹â‹
ç‹%õ‹2Œ%NŒtŒ1“ŒÅŒÊŒ ҌތþŒ �€�ž�£�²�4Ç�@ü�G=Ž<…ŽMÂŽB�S�d�t�y�Š�M¥�¢ó�„–�u‘;‘‘9Í‘6’Ñ>’4“>E”L„”IÑ”3•6O•K†•6Ò•< –F–I\–z¦–4!—UV—1¬—Þ—+•˜(Á˜‰ê˜-t™¢™O´š'›
,›:›*C›*n›™›/¬›Ü›ô›"ú›œ(-œVœ]œdœhœHlœ>µœôœýœ��)� 8�E�]�y�"‘�(´�%Ý�
žž0ž0Kžƒ|ž1Ÿ2ŸJŸ3bŸ1–ŸPÈŸ3 ;M ‰   
¯ ½ × ð ÷  ¡
¡È)¡ò¡
¢"¢)¢2¢E¢V¢q¢†¢›¢®¢Æ¢Õ¢Eí¢?3£s£‚£%•£#»£ߣ,÷£#$¤-H¤v¤{¤�›¤)¥1¥C¥]¥+n¥%š¥dÀ¥#%¦9å?ø•"D„Aå P�¦ãY— lZf·šØ-LǸÐ(SC0ý…«¼p€&n"¨sñÒ²¾�^/)—4 ´Ùƒ¾@ùŒO“4Q Y†ÍÀ¤ícÜ\jˆãH­>ì0KÑ}‚zÝŽÝ×ßòVöhß|
@±R4OÞ3§iÂ?`}��Îà”u–K…ÍÄùê¸8žÓµkaˆÇû«Zëoä èjxŽè©AQ­° C`Çê�<Iîu¿2âO‘‘Ïê-8s˜,*ÿ­òCF…6P‰ƒào{¡Ë™1aõ®Ö„îV9„ X�~]‡5b#.W¨SSªIv銯ôÆÐq�´î<rG9Ð :‚#1½JþÁ›æ¢]º8y
¡ÊnÜR¥ `d°³ÂÒB3Út.7wíbGe0'VÄ ^盃™œe"¤ð/Ôm+¡$˜Qhâ0-û̽EDšÛ>ýñœv£ÙxÂ
Úd¥¢f%Ÿ~µsw¯Ã‰Å:zë&›G
?ë$˜õ,+Éñ‹¼¬xöÕËÏ(þÍ 6œi×'·¦§ìgXºèFv•ý² �  '+I=!–|}ö#ª»{õåÿM/5ÛKü&Xг9ú
)ËjáÀñ÷�ÊN_fJT¹MÁ;ÿ\ØyT Ì4~@ÎN”Ãò†•�¨£oïL’BHÞ1d©·²§ü³l!ppBÄÛþ°Á{"æ5c*žŠ<m%U3;6wa‡Å¬øT÷8*b2žŸµ×㢇[û¼úónâ¹ðWEÑ‹ÈÉ;ÒÔ™Éz>ÌÊú>“—‘–Œ®(^UðtqJ¥�È’có¾_æ.�¿Æá£Ü)Ô6_÷@%7k/´LáCä2i¿‹MªDï½”tøqFůE(3|Ö©'u
D®¤Z
 ¸Ùä*íÞì<±$ÑéàÆÈ[%7=º?m[“ç:#,ÏÓk»5rÚ‚&ßô‰]ÖÎ$H7Õ!ݬŽhùePY»\
Nü=€óŸ«€ˆgUç’A�+AéÕr,†:-gl� =1yWRŒ¦!2À.Ø;ï �¹šBô)Ó
<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.
2025-08-12 08:54:05 -03:00
</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>
2026-03-13 20:44:45 -03:00
<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>
2026-03-18 11:24:10 -03:00
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.
2026-03-15 17:31:19 -03:00
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.
WireGuard private and public keys for this interface.
<br>
2025-08-12 08:54:05 -03:00
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>
<h5>Public Policy</h5>
<p>A Public policy allows access to the application without requiring any authentication.</p>
2026-02-09 22:07:48 -03:00
<h4>Authentication Types</h4>
<p>Select how users will authenticate through this method.</p>
<h5>Local Password</h5>
<p>Users will authenticate using a standard username and password stored locally. Only one of this type can be created.</p>
2025-12-29 18:30:39 -03:00
2026-03-12 18:54:37 -03:00
<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>
<p>Gatekeeper users are used for authenticating against protected applications managed by this gateway.</p>
2026-03-13 20:44:45 -03:00
<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
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
2025-12-29 18:30:39 -03:00
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>
<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>
2025-08-12 08:54:05 -03:00
2026-03-12 18:54:37 -03:00
<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-08-12 08:54:05 -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>
2025-12-29 18:30:39 -03:00
<p>API Keys allow external applications to interact with the WireGuard WebAdmin API.</p>
2026-01-16 15:01:13 -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>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>
<h5>Sync Intervals</h5>
2025-12-29 18:30: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>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>
<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>
2026-01-27 15:22:12 -03:00
<h5>Action</h5>
2025-08-12 08:54:05 -03:00
<p><strong>Allow</strong>: Grants access to the specified IP/network.<br>
2026-11-16 10:25:20 -03:00
<strong>Deny</strong>: Specifically blocks access from the specified IP/network.</p>
2025-08-12 08:54:05 -03:00
<h5>Description</h5>
<p>An optional note to help identify this entry (e.g., "Office Network", "Blocked Attacker").</p>
<h5>Peers</h5>
2026-11-16 10:25:20 -03:00
<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>
2025-08-12 08:54:05 -03:00
<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>
2026-01-27 15:22:12 -03:00
<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 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)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 one uppercase letter.Passwords do not match.Path PrefixPath prefix cannot contain spaces.Path prefix con
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=4; plural=(n % 1 == 0 && n == 1 ? 0 : n % 1 == 0 && n >= 2 && n <= 4 ? 1 : n % 1 != 0 ? 2: 3);
<h5>Pokro�ilá konfigurácia VPN firewall</h5>
<p>
Toto rozhranie slúži ako komplexný nástroj na správu firewall pravidiel, umožňujúci používateľom implementovať pokro�ilé politiky komunikácie medzi VPN peermi a sieťami. Zjednodušuje vytváranie firewall pravidiel, filtrovanie paketov a NAT konfigurácie, umožňujúc presný kontrol nad sieťovou bezpe�nosťou. Používatelia môžu definovať zdrojové a cieľové IP adresy, porty, protokoly a akcie na prispôsobenie toku komunikácie, zabezpe�ujúc bezpe�né a efektívne sieťové prostredie.
2025-08-12 08:54:05 -03:00
</p>
<h5>Výber cieľa</h5>
<p>
Máte možnosť aplikovať toto pravidlo na špecifickú IP adresu alebo sieť a/alebo na viacero peerov ako cieľ.<br><br>
Povolenie možnosti "Zahrnúť peer siete" automaticky zahrnie všetky povolené IP adresy spojené s každým vybraným peerom ako cieľ.<br><br>
Prosím všimnite si, že výber viacerých peerov so zahrnutými sieťami na strane zdroja aj cieľa môže viesť k rýchlemu nárastu po�tu vygenerovaných firewall pravidiel, v závislosti od vašej konfigurácie.<br><br>
Možnosť "Nie cieľ" neguje vybraný cieľový IP, sieť alebo peer(y).
</p>
<h5>Protokol a port</h5>
2026-03-13 20:44:45 -03:00
<p>
Tu sú uvedené len naj�astejšie používané protokoly. Ak potrebujete špecifický protokol, prosím otvorte issue na GitHub.<br><br>
Výber TCP+UDP bude mať za následok duplikáciu vygenerovaných pravidiel.<br><br>
Porty môžu byť špecifikované ako jednotlivé �ísla (napr. 8080) alebo ako rozsahy (napr. 8001:8999).
</p>
<h5>Výber zdroja</h5>
<p>
Máte možnosť aplikovať toto pravidlo na špecifickú IP adresu alebo sieť a/alebo na viacero peerov.<br><br>
Povolenie možnosti "Zahrnúť peer siete" automaticky zahrnie všetky povolené IP adresy spojené s každým vybraným peerom.<br><br>
Prosím všimnite si, že výber viacerých peerov so zahrnutými sieťami na strane zdroja aj cieľa môže viesť k rýchlemu nárastu po�tu vygenerovaných firewall pravidiel, v závislosti od vašej konfigurácie.<br><br>
Možnosť "Nie zdroj" neguje vybranú zdrojovú IP, sieť alebo peer(y).
</p>
2026-03-18 11:24:10 -03:00
DNS servery odoslané peerom.
<br>
Použitie internej IP ako primárneho DNS umožňuje interné rozlíšenie názvov
a filtrovanie DNS.
Vynucuje smerovacie pravidlá definované smerovacími šablónami pomocou pravidiel firewallu.
<br>
Peeri s predvolenou trasou (0.0.0.0/0) nie sú obmedzení.
<br><br>
Poznámka: v závislosti od po�u trás a peerov môže táto možnosť vygenerovať
veľký po�et pravidiel firewallu.
2026-03-15 17:31:19 -03:00
Interná IP adresa a sieťová maska používaná rozhraním WireGuard.
Interval používaný na obnovenie informácií o stave WireGuard vo webovom používateľskom rozhraní.
Voliteľný názov používaný iba na zobrazenie vo webovom rozhraní.
Verejný názov hostiteľa alebo IP adresa a UDP port, ktorý používajú peeri na pripojenie.
<br>
<b>Port po�úvania</b> musí byť sprístupnený a namapovaný vo vašom súbore Docker compose (YAML).
Súkromné a verejné kľú�e WireGuard pre toto rozhranie.
<br>
2025-08-12 08:54:05 -03:00
Súkromný kľú� musí zostať v tajnosti.
Jeho zmena vyžaduje aktualizáciu konfigurácií všetkých peerov.
<h5>Predvolené porty</h5>
<p>Predvolený <code>docker-compose.yml</code> súbor špecifikuje <b>TCP</b> rozsah portov <b>8080-8089</b>. Ak si želáte zmeniť presmerovanie portov na iný rozsah, musíte manuálne upraviť <code>docker-compose.yml</code> súbor a znovu spustiť Docker Compose krok uvedený v <a href="https://github.com/eduardogsilva/wireguard_webadmin?tab=readme-ov-file#deployment">pokynoch na nasadenie</a>.</p>
<h5>Typ cieľa: Peer</h5>
<p>Presmerovanie portov bude uprednostňovať prvú IP adresu peer s prioritou nula.</p>
<h5>Typ cieľa: IP adresa</h5>
<p>Pravidlá presmerovania portov budú presmerovávať na špecifikovanú IP adresu. Nezabudnite prideliť IP adresu alebo sieť peer.</p>
<h5>Pridávanie pravidla presmerovania</h5>
<p>Automaticky generuje pravidlo presmerovania pre prispôsobenie prísnejších nastavení firewall.</p>
<h5>Maskovanie zdroja</h5>
<p>Toto slúži ako do�asné riešenie ke� peer nepoužíva VPN ako svoju predvolenú bránu. Je dôležité poznamenať, že táto konfigurácia nie je odporú�aná, pretože mení zdrojovú adresu všetkých pripojení tak, aby zodpovedala IP adrese WireGuard inštancie.</p>
<h5>Politika odmietnutia</h5>
<p>Politika odmietnutia blokuje všetok prístup k zodpovedajúcim trasám.</p>
<h5>Chránená politika</h5>
<p>Chránená politika vyžaduje, aby sa používatelia pred prístupom k aplikácii overili.</p>
<ul>
<li><strong>Povolené skupiny</strong>: Obmedzuje prístup pre konkrétne skupiny používateľov. Poznámka: Používanie skupín vyžaduje výber autentifika�nej metódy typu „Miestne heslo“.</li>
<li><strong>Autentifika�né metódy</strong>: Špecifikujte, ktoré metódy môžu používatelia použiť na overenie (napr. miestne heslo, TOTP, OIDC).</li>
</ul>
<h5>Verejná politika</h5>
<p>Verejná politika umožňuje prístup k aplikácii bez vyžadovania akéhokoľvek overenia.</p>
2026-02-09 22:07:48 -03:00
<h4>Typy autentifikácie</h4>
<p>Vyberte, ako sa budú používatelia overovať pomocou tejto metódy.</p>
<h5>Lokálne heslo</h5>
<p>Používatelia sa budú overovať pomocou štandardného používateľského mena a hesla uloženého lokálne. Je možné vytvoriť iba jednu metódu tohto typu.</p>
2025-12-29 18:30:39 -03:00
2026-03-12 18:54:37 -03:00
<h5>OIDC (OpenID Connect)</h5>
<p>Používatelia sa budú overovať prostredníctvom externého poskytovateľa identity (napríklad Keycloak alebo Google). Vyžaduje URL poskytovateľa, ID klienta a tajný kľú� klienta.</p>
<h5>TOTP (�asovo založené jednorazové heslo)</h5>
<p>Používatelia budú musieť zadať rotujúci token z autentifika�nej aplikácie. Ak používateľ nemá nakonfigurované osobné TOTP, namiesto toho sa použije <strong>globálne tajomstvo TOTP</strong>. </p>
<h4>Používateľ Gatekeeper</h4>
<p>Používatelia Gatekeeper sa používajú na autentifikáciu vo�i chráneným aplikáciám spravovaným touto bránou.</p>
2026-03-13 20:44:45 -03:00
<h5>Heslo</h5>
<p>Vyžaduje sa pri vytváraní používateľa. Pri úprave ponechajte obe polia pre heslo prázdne, aby sa zachovalo aktuálne heslo.
Heslá sa ukladajú pomocou hašovania <strong>Argon2id</strong>.</p>
<h5>TOTP tajomstvo</h5>
<p>Voliteľné TOTP tajomstvo pre konkrétneho používateľa. Ke� je nastavené, tento používateľ sa bude autentifikovať pomocou vlastného tajomstva namiesto
globálneho TOTP tajomstva konfigurovaného v metóde autentifikácie. Pomocou tla�idiel pod poľom vygenerujte
náhodné tajomstvo a naskenujte QR kód pomocou vašej aplikácie autentifikátora. Pred uložením overte tajomstvo zadaním aktuálneho
2025-12-29 18:30:39 -03:00
6-miestneho kódu PIN.</p>
<h4>Úrovne používateľov</h4>
<h5>Analytik ladenia</h5>
<p>Prístup k základným systémovým informáciám a logom na riešenie problémov. Žiadny prístup na úpravu nastavení alebo zobrazenie citlivých údajov ako sú kľú�e peerov.</p>
<h5>Len na prezeranie</h5>
<p>Plný prístup na prezeranie vrátane kľú�ov peerov a konfigura�ných súborov. Nemôže upravovať žiadne nastavenia alebo konfigurácie.</p>
<h5>Správca peer</h5>
<p>Oprávnenia na pridávanie, upravovanie a odstraňovanie peerov a IP adries. Nezahŕňa prístup na úpravu konfigurácií WireGuard inštancií alebo nastavení vyššej úrovne.</p>
2025-08-12 08:54:05 -03:00
2026-03-12 18:54:37 -03:00
<h5>Správca WireGuard</h5>
<p>Oprávnenie na pridávanie, upravovanie a odstraňovanie konfigurácií WireGuard inštancií.</p>
<h5>Administrátor</h5>
<p>Plný prístup k celému systému. Môže zobrazovať a upravovať všetky nastavenia, konfigurácie a spravovať používateľov.</p>
<br>
<h4>Peer skupiny</h4>
<p>Vyberte ktoré peer skupiny môže tento používateľ pristupovať. Ak nie sú vybrané žiadne peer skupiny, používateľ bude mať prístup ku všetkým peerom.</p>
<h4>Konzola</h4>
<p>Povoliť alebo zakázať prístup k webovej konzole pre tohto používateľa.</p>
2025-08-12 08:54:05 -03:00
<h4>Rozšírený filter</h4>
<p>Táto možnosť filtruje odpove� API stavu tak, aby zahŕňala len peerov, ku ktorým má používateľ prístup. V závislosti od veľkosti vášho prostredia môže povolenie tejto možnosti ovplyvniť výkon. Na zmiernenie zvážte zvýšenie "Intervalu obnovenia webu" na zníženie po�tu požiadaviek.</p>
<h5>Kľú�e API</h5>
2025-12-29 18:30:39 -03:00
<p>Kľú�e API umožňujú externým aplikáciám komunikovať s API WireGuard WebAdmin.</p>
2026-01-16 15:01:13 -03:00
<p><strong>Token:</strong> Tajný token používaný na autentifikáciu. Uchovávajte ho v bezpe�í.</p>
<p><strong>Povolené inštancie:</strong> Inštancie WireGuard, ktoré tento kľú� môže spravovať. Ak nie sú vybrané žiadne, kľú� má prístup ku VŠETK�M inštanciám.</p>
<p><strong>Povolenia:</strong> špecifické akcie povolené pre tento kľú�.</p>
<h5>Trasa aplikácie</h5>
<p>Trasa definuje prefix cesty v rámci tejto aplikácie, ktorý vyžaduje špecifickú politiku prístupu.</p>
<ul>
<li><strong>Názov trasy</strong>: Interný identifikátor pre túto trasu (napr. „public_api“, „admin_area“). Používa sa na referenciu a exporty.</li>
<li><strong>Prefix cesty</strong>: Cesta URL, ktorá spúšťa túto trasu (napr. <code>/api/</code> alebo <code>/admin/</code>). Použite <code>/</code> na zhodu so všetkými zostávajúcimi cestami.</li>
<li><strong>Politika</strong>: Politika prístupu, ktorá sa vynúti, ke� používateľ pristúpi k tejto ceste.</li>
<li><strong>Poradie</strong>: Ur�uje prioritu tejto trasy pri vyhodnocovaní požiadavky. Nižšie �ísla sa vyhodnocujú ako prvé. Ak sa s cestou zhoduje viacero trás, vyhráva tá s najnižším poradím.</li>
</ul>
<h5>Aplikácia</h5>
<p>Definujte hlavné podrobnosti aplikácie, ktorú chcete vystaviť prostredníctvom brány.</p>
<ul>
<li><strong>Názov</strong>: Jedine�ný interný identifikátor pre túto aplikáciu (napr. „wiki“, „crm“). Obsahuje iba písmená, �ísla, poml�ky alebo pod�iarkovníky.</li>
<li><strong>Zobrazený názov</strong>: Priateľský, �itateľný názov na ú�ely zobrazenia.</li>
<li><strong>Upstream</strong>: Cieľová URL adresa, kam sa budú požiadavky presmerovávať (napr. <code>http://10.188.18.27:3000</code>). Musí za�ínať na <code>http://</code> alebo <code>https://</code>.</li>
</ul>
<h5>Režim clustra</h5>
<p>Nakonfigurujte, ako cluster funguje a ako sa synchronizujú konfigurácie medzi uzlami.</p>
<h5>Intervaly synchronizácie</h5>
2025-12-29 18:30:39 -03:00
<p>Nakonfigurujte, ako �asto sa synchronizujú štatistiky a údaje vyrovnávacej pamäte medzi uzlami clustra.</p>
<h5>Režim reštartu</h5>
<p>Vyberte, �i sa majú služby WireGuard automaticky reštartovať pri zmene konfigurácie, alebo �i je potrebný manuálny zásah.</p>
<h5>Zobrazenie workera</h5>
<p>Vyberte, ako sa majú workery identifikovať v rozhraní – podľa názvu, adresy servera, umiestnenia alebo ich kombinácie.</p>
<h5>Zoznam IP adries</h5>
<p>Spravujte konkrétne IP adresy alebo siete, ktorým je povolený alebo odmietnutý prístup pri používaní metódy autentifikácie pomocou zoznamu IP adries.</p>
<h5>IP adresa a prefix</h5>
<p>Zadajte jednu IP adresu (napr. 192.168.1.50) alebo sieťovú adresu. Použite dĺžku prefixu pre notáciu CIDR (napr. 24 pre sieť /24). Ponechajte prefix prázdny pre jedného hostiteľa (/32 pre IPv4, /128 pre IPv6).</p>
2026-01-27 15:22:12 -03:00
<h5>Akcia</h5>
2025-08-12 08:54:05 -03:00
<p><strong>Povoliť</strong>: Udeľuje prístup k zadanej IP/sieti.<br>
2026-11-16 10:25:20 -03:00
<strong>Odmietnuť</strong>: Špecificky blokuje prístup zo zadanej IP/siete.</p>
2025-08-12 08:54:05 -03:00
<h5>Popis</h5>
<p>Voliteľná poznámka, ktorá pomôže identifikovať tento záznam (napr. „Kancelárska sieť“, „Blokovaný úto�ník“).</p>
<h5>Peeri</h5>
2026-11-16 10:25:20 -03:00
<p>Vyberte ktoré peeri môžu byť spravované používateľmi s touto peer skupinou.</p>