1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
|
<?xml version="1.0" encoding="utf-8"?>
<resources>
<string name="app_name">AndIodine</string>
<string name="app_about">About</string>
<string-array name="pref_entries_dnstype">
<item>autodetect</item>
<item>NULL</item>
<item>TXT</item>
<item>SRV</item>
<item>MX</item>
<item>CNAME</item>
<item>A</item>
</string-array>
<string-array name="pref_entries_nameserver_mode">
<item>Network default</item>
<item>Custom</item>
<item>Tunnel Endpoint</item>
</string-array>
<string name="main_description_add_account">Add Account</string>
<string name="pref_description_cancel">Cancel</string>
<string name="configitem_description_close">Close Tunnel</string>
<string name="pref_text_password_label">Password</string>
<string name="pref_text_topdomain_label">Tunnel Toplevel Domain</string>
<string name="pref_text_tunnel_nameserver_label">Tunnel Nameserver</string>
<string name="pref_text_nameserver_mode_label">Nameserver Mode</string>
<string name="pref_text_nameserver_address_label">Nameserver Address</string>
<string name="pref_text_name_label">Configuration Profile Name</string>
<string name="pref_text_use_default_nameserver">Use default Nameserver for tunneling</string>
<string name="pref_help_name">Name for this configuration.</string>
<string name="pref_help_topdomain">The dns traffic will be sent as queries for subdomains under _topdomain_. This is
normally a subdomain to a domain you own. Use a short domain name to get better throughput. If nameserver is the
iodined server, then the topdomain can be chosen freely. This argument must be the same on both the client and
the server.
</string>
<string name="pref_help_lazy">Use lazy mode for improved performance and decreased latency. A very small minority of
DNS relays appears to be unable to handle the lazy mode traffic pattern, resulting in no or very little data
coming through. The iodine client will detect this and try to switch back to legacy mode, but this may not
always work. In these situations use this switch.
</string>
<string name="pref_help_raw">If set used, iodine will try getting the public IP address of the iodined host and test
if it is reachable directly. If it is, traffic will be sent to the server instead of the DNS relay.
</string>
<string name="pref_help_tunnel_nameserver">The nameserver to use to relay the dns traffic. This can be any relaying
nameserver or the server running iodined if reachable. This field can be given as an IP address, or as a
hostname. This argument is optional, and if not specified the default system Nameserver will be used.
</string>
<string name="pref_help_password">This field is optional. Only the first 32 characters will be used</string>
<string name="pref_help_nameserver_mode">Source of the Nameserver to use for name resolution while tunnel is
active
</string>
<string name="pref_help_nameserver">Custom Nameserver IP-Address to set if Nameserver-mode is "Custom"</string>
<string name="pref_help_request_type">DNS request type override. By default, autodetection will probe for working
DNS request types, and will select the request type that is expected to provide the most bandwidth. However, it
may turn out that a DNS relay imposes limits that skew the picture, which may lead to an "unexpected" DNS
request type providing more bandwidth. In that case, use this option to override the autodetection. In
(expected) decreasing bandwidth order, the supported DNS request types are: NULL, TXT, SRV, MX, CNAME and A
(returning CNAME). Note that SRV, MX and A may/will cause additional lookups by "smart" caching nameservers to
get an actual IP address, which may either slow down or fail completely.
</string>
<string name="pref_request_hostname_size">Maximum size of upstream hostnames. Valid values are from 100 to 255.
Default is 255. Decrease if you find some DNS relays answer to full-length queries unreliably giving widely
varying results of fragment size autoprobe.
</string>
<string name="pref_response_fragment_size">Response fragment size. Autoprobed when set to 0 which is a default.
</string>
<string name="enable">Enable</string>
<string name="vpnservice_error_configuration_incomplete">Configuration is incomplete</string>
<string name="vpnservice_error_already_running">Cannot start VPN Service, VPN-Thread is already running</string>
<string name="vpnservice_error_thread_exited">VPN Thread exited unexpected</string>
<string name="vpnservice_error_cant_open_dnssocket">Can\'t open DNS Socket</string>
<string name="vpnservice_error_handshake_failed">Handshake failed</string>
<string name="vpnservice_error_unknown_error_code">Unknown Error. Code %d</string>
<string name="vpnservice_error_unknown_error_string">Unknown Error. Reason: %s</string>
<string name="vpnservice_error_dns_detect_failed">No valid IPv4 name servers detected</string>
<string name="vpnservice_error_create_interface_string">Failed to create tunnel network device</string>
<string name="idle">Idle</string>
<string name="warning">Warning</string>
<string name="error">Error</string>
<string name="configitem_description_manage">Configure this Connection Profile</string>
<string name="pref_title">Connection Configuration</string>
<string name="pref_help_default_route">Set default Route for the tunnel device</string>
<string name="main_create_tunnel">Create DNS Tunnel from Configuration named %s</string>
<string name="fragment_list_add">New Account</string>
<string name="main_about">About</string>
<string name="pref_delete">Delete</string>
</resources>
|
