|
1 | 1 | { |
2 | 2 | "$schema": "https://inlang.com/schema/inlang-message-format", |
3 | | - "add_location_welcome_title": "Add new location", |
4 | | - "add_location_welcome_subtitle": "Welcome! Let's set up a new location to organize users, manage access, and connect gateways for activity tracking and monitoring.", |
| 3 | + "add_location_welcome_title": "Add new VPN location", |
| 4 | + "add_location_welcome_subtitle": "Configure the VPN location public endpoint and internal VPN network settings.", |
5 | 5 | "add_location_page_title": "Create new location", |
6 | | - "add_location_step_common_description": "Manage core details and connection parameters for your VPN location.", |
7 | | - "add_location_step_public_facing_data_label": "Public-facing data", |
| 6 | + "add_location_step_common_description": "Configure VPN location details.", |
| 7 | + "add_location_step_public_facing_data_label": "Public Endpoint", |
8 | 8 | "add_location_step_internal_vpn_label": "Internal VPN", |
9 | 9 | "add_location_step_network_settings_label": "Network Settings", |
10 | 10 | "add_location_step_mfa_label": "Multi-Factor Authentication", |
|
24 | 24 | "add_location_firewall_gateway_activation_subtitle": "To activate your location, you must add at least one gateway connection. You can do this immediately after creation or later in the location settings.", |
25 | 25 | "add_location_firewall_gateway_activation_checkbox": "Run the gateway activation wizard once the location is created", |
26 | 26 | "add_location_create_location": "Create location", |
27 | | - "add_location_start_public_address_title": "Gateway public address", |
28 | | - "add_location_start_public_address_description": "Used by VPN users to connect.", |
29 | | - "add_location_start_label_endpoint": "Gateway VPN IP address or domain name", |
30 | | - "add_location_start_helper_endpoint": "", |
31 | | - "add_location_start_label_port": "Gateway port", |
32 | | - "add_location_start_helper_port": "", |
33 | | - "add_location_internal_vpn_gateway_address_title": "Gateway address", |
34 | | - "add_location_internal_vpn_gateway_address_description": "The VPN network will be derived from this address (e.g., 10.10.10.1 → 10.10.10.0). You can specify multiple addresses separated by commas. The first one is used as the primary address for device IP assignment.", |
35 | | - "add_location_internal_vpn_label_address": "Gateway VPN IP address and netmask", |
36 | | - "add_location_internal_vpn_helper_address": "", |
37 | | - "add_location_internal_vpn_allowed_ips_title": "Allowed IPs", |
38 | | - "add_location_internal_vpn_allowed_ips_description": "List of addresses/masks that should be routed through the VPN network.", |
| 27 | + "add_location_start_public_address_title": "VPN Public IP or Domains", |
| 28 | + "add_location_start_public_address_description": "This IP or domain address must be public, as clients will use it to connect to the VPN in this location. This is configured now (before gateway deployment) because it will be distributed to all clients in their configuration and stored in the location details.", |
| 29 | + "add_location_start_label_endpoint": "VPN Public IP or Domain", |
| 30 | + "add_location_start_helper_endpoint": "This IP/domain must be configured on the host where the gateway will be deployed (this occurs at a later stage), or at least have its VPN port forwarded to the gateway.", |
| 31 | + "add_location_start_label_port": "VPN WireGuard® Port", |
| 32 | + "add_location_start_helper_port": "The VPN Gateway will run on this port. At a later stage, when you deploy the Gateway component, if it is not publicly accessible, please forward this port from the public VPN WireGuard® IP address to the gateway's internal IP and port.", |
| 33 | + "add_location_internal_vpn_gateway_address_title": "VPN network", |
| 34 | + "add_location_internal_vpn_gateway_address_description": "We need to configure this location internal VPN network. Set the IP address/mask for the gateway server, and we will configure the VPN network based on it. You can configure multiple addresses separated by commas.", |
| 35 | + "add_location_internal_vpn_label_address": "Internal VPN address (CIDR)", |
| 36 | + "add_location_internal_vpn_helper_address": "The gateway IP address must be in CIDR format: IP/mask (e.g., 10.10.0.1/24). Based on this address, we will configure the VPN network (e.g., 10.10.0.0/24). You can define multiple IPv4 and IPv6 addresses (networks) separated by commas.", |
| 37 | + "add_location_internal_vpn_allowed_ips_title": "Allowed IPs (routing networks)", |
| 38 | + "add_location_internal_vpn_allowed_ips_description": "The defined networks (comma-separated) will be made available to clients connecting to the VPN.", |
39 | 39 | "add_location_internal_vpn_allowed_ips_from_firewall_rules": "Allowed IPs are generated automatically from firewall rules", |
40 | 40 | "add_location_internal_vpn_label_allowed_ips": "Allowed IPs", |
41 | 41 | "add_location_internal_vpn_helper_allowed_ips": "", |
|
59 | 59 | "location_mfa_external": "External", |
60 | 60 | "location_mfa_internal": "Internal", |
61 | 61 | "location_mfa_label_client_disconnect_threshold": "Client disconnect threshold (seconds)", |
62 | | - "location_mfa_helper_client_disconnect_threshold": "", |
| 62 | + "location_mfa_helper_client_disconnect_threshold": "The Client disconnect threshold (seconds) is the inactivity timeout after which Defguard drops a VPN connection. If no WireGuard® traffic is detected for this duration, the client is disconnected and will be required to re-authorize via MFA when reconnecting.", |
63 | 63 | "location_allowed_groups_all": "All allowed", |
64 | 64 | "location_access_all_groups_have_access": "All groups have access", |
65 | 65 | "location_type_regular": "Regular", |
|
69 | 69 | "location_service_mode_prelogon": "Service location: Pre-logon", |
70 | 70 | "location_service_mode_always_on": "Service location: Always on", |
71 | 71 | "location_network_label_keepalive_interval": "Keep alive interval (seconds)", |
72 | | - "location_network_helper_keepalive_interval": "", |
| 72 | + "location_network_helper_keepalive_interval": "The Keepalive Interval in WireGuard® is a setting that sends a small, encrypted packet at regular intervals to ensure that NAT-based firewalls or routers keep the connection 'hole' open and active.", |
73 | 73 | "location_network_label_mtu": "Maximum Transmission Unit (MTU)", |
74 | | - "location_network_helper_mtu": "", |
| 74 | + "location_network_helper_mtu": "MTU (Maximum Transmission Unit) is the largest size of a data packet, measured in bytes, that a network device can transmit over a connection in a single transaction.", |
75 | 75 | "location_network_label_fwmark": "Firewall Mark (FwMark)", |
76 | | - "location_network_helper_fwmark": "", |
| 76 | + "location_network_helper_fwmark": "Firewall Mark is a numerical label attached to network packets by the kernel to help the system make specialized routing or filtering decisions. If unused leave 0.", |
77 | 77 | "location_firewall_option_disabled": "Disable firewall option", |
78 | 78 | "location_firewall_option_default_allow": "Users/devices can access all resources unless limited by ACL rules.", |
79 | 79 | "location_firewall_option_default_deny": "All traffic not explicitly allowed by an ACL rule will be blocked.", |
|
82 | 82 | "location_delete_failed": "Failed to delete location", |
83 | 83 | "location_edit_title": "Edit location: {name}", |
84 | 84 | "location_form_label_name": "Location name", |
85 | | - "location_form_helper_name": "", |
| 85 | + "location_form_helper_name": "This will be visible on the dashboard and in the desktop and mobile clients to help users identify where they are connecting.", |
86 | 86 | "location_form_label_endpoint": "Gateway IP address or domain name", |
87 | 87 | "location_form_helper_endpoint": "", |
88 | 88 | "location_mfa_option_internal": "Internal MFA", |
|
0 commit comments