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
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119 | Template: netcfg/dhcp_hostname
Type: string
# :sl1:
_Description: DHCP hostname:
You may need to supply a DHCP host name. If you are using
a cable modem, you might need to specify an account number here.
.
Most other users can just leave this blank.
Template: netcfg/dhcp_progress
Type: text
# :sl1:
_Description: Configuring the network with DHCP
Template: netcfg/dhcp_progress_note
Type: text
# :sl1:
_Description: This may take some time.
Template: netcfg/dhcp_success_note
Type: text
# :sl1:
_Description: Network autoconfiguration has succeeded
Template: netcfg/no_dhcp_client
Type: error
# :sl2:
_Description: No DHCP client found
No DHCP client was found. This package requires pump or dhcp-client.
.
The DHCP configuration process has been aborted.
Template: netcfg/dhcp_options
Type: select
# :sl1:
#flag:translate!:1
__Choices: ${choices}
Default: Configure network manually
# :sl1:
_Description: Network configuration method:
From here you can choose to retry DHCP network autoconfiguration
(which may succeed if your DHCP server takes a long time to respond)
or to configure the network manually. Some DHCP servers require
a DHCP hostname to be sent by the client, so you can also choose
to retry DHCP network autoconfiguration with a hostname that you
provide.
Template: netcfg/dhcp_failed
Type: note
# :sl1:
_Description: Network autoconfiguration failed
Your network is probably not using the DHCP protocol. Alternatively, the
DHCP server may be slow or some network hardware is not working properly.
Template: netcfg/no_default_route
Type: boolean
# :sl2:
_Description: Continue without a default route?
The network autoconfiguration was successful. However, no default route
was set: the system does not know how to communicate with hosts on the
Internet. This will make it impossible to continue with the installation
unless you have the first installation CD-ROM, a 'Netinst' CD-ROM, or
packages available on the local network.
.
If you are unsure, you should not continue without a default route:
contact your local network administrator about this problem.
Template: netcfg/internal-nowifi
Type: select
# :sl1:
__Choices: Retry network autoconfiguration, Retry network autoconfiguration with a DHCP hostname, Configure network manually, Do not configure the network at this time
Template: netcfg/internal-wifireconf
Type: select
# :sl1:
# Note to translators : Please keep your translation
# below a 65 columns limit (which means 65 characters
# in single-byte languages)
__Choices: Retry network autoconfiguration, Retry network autoconfiguration with a DHCP hostname, Configure network manually, Reconfigure the wireless network, Do not configure the network at this time
Template: netcfg/dhcp_timeout
Type: string
Description: for internal use; can be preseeded
Timeout for trying DHCP
Default: 30
Template: netcfg/dhcp_ntp_servers
Type: text
Description: for internal use
NTP servers provided by DHCP
Template: netcfg/slaac_wait_title
Type: text
# IPv6
# :sl2:
_Description: Attempting IPv6 autoconfiguration...
Template: netcfg/ipv6_link_local_wait_title
Type: text
# IPv6
# :sl2:
_Description: Waiting for link-local address...
Template: netcfg/ipv6_config_flags_wait_title
Type: text
# IPv6
# :sl2:
_Description: Attempting IPv6 autoconfiguration...
Template: netcfg/dhcpv6_timeout
Type: string
Description: for internal use; can be preseeded
Timeout for trying DHCPv6
Default: 30
Template: netcfg/dhcpv6_progress
Type: text
# :sl2:
_Description: Configuring the network with DHCPv6
|