[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[LCFC] templates://dhcp3/{dhcp3-relay.templates,dhcp3-server.templates,dhcp3-client.templates}



This is the last call for comments for the review of debconf
templates for dhcp3.

The reviewed templates will be sent on Tuesday, May 22, 2007 to the package
maintainer as a bug report and a mail will be sent to this list with
"[BTS]" as a subject tag.


-- 


Template: dhcp3-relay/servers
Type: string
_Description: Servers the DHCP relay should forward requests to:
 Please enter the hostname or IP address of at least one DHCP server
 to which DHCP and BOOTP requests should be relayed.
 .
 You can specify more than one server; server names or
 IP addresses should then be space-separated.

Template: dhcp3-relay/interfaces
Type: string
_Description: Interfaces the DHCP relay should listen on:
 Please enter the names of the network interfaces that dhcp3-relay
 should attempt to configure, as a space-separated list.
 .
 Leave this field blank to allow for automatic detection and
 configuration of network interfaces by dhcp3-relay, in which case
 only broadcast interfaces will be used (if possible).

Template: dhcp3-relay/options
Type: string
_Description: Additional options for the DHCP relay daemon:
 Please specify any additional options for the DHCP relay daemon.
 .
 For example: "-m replace" or "-a -D".
Template: dhcp3-server/config_warn
Type: note
_Description: Manual configuration required after installation
 After the DHCP server is installed, you will need to manually configure it
 by editing the file /etc/dhcp3/dhcpd.conf. Please note that the dhcpd.conf
 supplied is just a sample, and must be adapted to the network environment.
 .
 Please configure the DHCP server as soon as the installation finishes.

Template: dhcp3-server/interfaces
Type: string
_Description: Network interfaces on which the DHCP server should listen:
 Please enter a space-separated list of interfaces names (e.g. eth0) 
 on which the server should answer DHCP requests.
 .
 The interfaces will be automatically detected if this field is left
 blank.

# Should probably be dropped
Template: dhcp3-server/new_auth_behavior
Type: note
_Description: Non-authoritative version of DHCP server
 The version 3 DHCP server is non-authoritative by default.
 .
 This means that if a client requests an address that the server knows
 nothing about and the address is incorrect for that network segment, the
 server will _not_ send a DHCPNAK (which tells the client it should stop
 using the address). If you want to change this behavior, you must
 explicitly state in dhcpd.conf what network segments your server is
 authoritative for using the 'authoritative' statement.

# Should probably be dropped
Template: dhcp3-server/new_next-server_behaviour
Type: note
_Description: Change in default behaviour of the next-server directive
 From version 3.0.3, the DHCP server's default value of the
 next-server directive has changed. If you are network booting clients, and
 your TFTP server is your DHCP server, you need to explicitly set a
 next-server directive to state this. Please see
 /usr/share/doc/dhcp3-server/NEWS.Debian.gz and
 /usr/share/doc/dhcp3-common/RELNOTES.gz for more information.
# Should probably be dropped
Template: dhcp3-client/dhclient-script_moved
Type: note
_Description: dhclient-script moved
 As of 3.0.4-2, dhclient-script is installed in /sbin and is no longer
 registered as a configuration file. /etc/dhcp3/dhclient-script
 appears to have been modified at some point, so it has not been
 removed. However it is no longer being used.
 .
 Please consider using the hook infrastructure (see dhclient-script(8)
 for more information) instead of modifying dhclient-script.

# Should probably be dropped
Template: dhcp3-client/dhclient-needs-restarting
Type: note
_Description: dhclient needs restarting
 As always, dhclient is not restarted on upgrade, so you are still running the
 previous version of dhclient. You can restart it by doing an ifdown and ifup
 on the interface(s) that are configured to use DHCP, or by explicitly killing
 and restarting dhclient.
 .
 Naturally, you should exercise caution if you are managing a remote server via
 an interface using DHCP.
Source: dhcp3
Section: net
Priority: important
Maintainer: Eloy A. Paris <peloy@debian.org>
Uploaders: Matt Zimmerman <mdz@debian.org>, Andrew Pollock <apollock@debian.org>
Build-Depends: debhelper (>= 4.1.16), dpkg-dev (>= 1.13.2), groff, dpatch, po-debconf
Standards-Version: 3.5.6

Package: dhcp3-server
Priority: optional
Architecture: any
Depends: debianutils (>= 2.8.2), dhcp3-common (= ${Source-Version}), ${shlibs:Depends}, ${misc:Depends}
Conflicts: dhcp
Description: DHCP server for automatic IP address assignment
 This is the server from version 3 of the Internet Software
 Consortium's implementation of DHCP. For more information, visit
 http://www.isc.org.
 .
 Dynamic Host Configuration Protocol (DHCP) is a protocol like BOOTP
 (actually dhcpd includes much of the functionality of bootpd). It
 gives client machines "leases" for IP addresses and can
 automatically set their network configuration.
 .
 This server can handle multiple ethernet interfaces.

Package: dhcp3-common
Architecture: any
Section: net
Depends: debianutils (>= 2.8.2), ${shlibs:Depends}, ${misc:Depends}
Description: common files used by all the dhcp3* packages
 This package contains the files used by all the packages from ISC
 DHCP version 3.

Package: dhcp3-dev
Priority: optional
Architecture: any
Section: devel
Depends: libc6-dev
Description: API for accessing and modifying the DHCP server and client state
 OMAPI is an API for accessing and modifying the DHCP server and
 client state.

Package: dhcp3-client
Architecture: any
Depends: debianutils (>= 2.8.2), dhcp3-common (= ${Source-Version}), ${shlibs:Depends}, ${misc:Depends}
Suggests: resolvconf, avahi-autoipd
Conflicts: dhcp-client (<< 3.0), samba-common (<< 3.0.0beta1-2)
Description: DHCP client
 This is the client from version 3 of the Internet Software
 Consortium's implementation of DHCP. For more information visit
 http://www.isc.org.
 .
 Dynamic Host Configuration Protocol (DHCP) is a protocol like BOOTP
 (actually dhcpd includes much of the functionality of bootpd). It
 gives client machines "leases" for IP addresses and can
 automatically set their network configuration. If your machine
 depends on DHCP (especially likely if it's a workstation on a large
 network, or a laptop, or attached to a cable modem), keep this or
 another DHCP client installed.
 .
 Extra documentation can be found in the package dhcp3-common.

Package: dhcp3-client-udeb
Priority: extra
Architecture: any
Section: debian-installer
Depends: ${shlibs:Depends}
Conflicts: dhcp-client-udeb
XC-Package-Type: udeb
Description: DHCP Client for debian-installer
 dhcp-client-udeb is a minimal dhcp package used by the debian-installer.

Package: dhcp3-relay
Priority: optional
Architecture: any
Depends: debianutils (>= 2.8.2), dhcp3-common (= ${Source-Version}), ${shlibs:Depends}, ${misc:Depends}
Conflicts: dhcp-relay
Description: DHCP relay daemon
 This is the relay from version 3 of the Internet Software
 Consortium's implementation of DHCP. For more information visit
 http://www.isc.org.
 .
 Installing this package will make the machine a DHCP relay, which
 requires a reachable DHCP or BOOTP server in order to function.
 .
 Extra documentation can be found in the package dhcp3-common.

Attachment: signature.asc
Description: Digital signature


Reply to: