From: Ted Lemon Date: Sat, 22 Feb 1997 13:08:03 +0000 (+0000) Subject: moved to relay/ X-Git-Tag: DHCP_970222~15 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=6693cdf42298c122c83d74a649f8b23ec282672c;p=thirdparty%2Fdhcp.git moved to relay/ --- diff --git a/dhcrelay.cat8 b/dhcrelay.cat8 deleted file mode 100644 index 6c60d6c77..000000000 --- a/dhcrelay.cat8 +++ /dev/null @@ -1,132 +0,0 @@ - - - -dhcrelay(8) dhcrelay(8) - - -NNAAMMEE - dhcpd - Dynamic Host Configuration Protocol Relay Agent - -SSYYNNOOPPSSIISS - ddhhccrreellaayy [ --pp _p_o_r_t ] [ --dd ] [ --ii _i_f_0 [ ...... --ii _i_f_N ] ] - _s_e_r_v_e_r_0 [ _._._._s_e_r_v_e_r_N ] - -DDEESSCCRRIIPPTTIIOONN - The Internet Software Consortium DHCP Relay Agent, dhcre- - lay, provides a means for relaying DHCP and BOOTP requests - from a subnet to which no DHCP server is directly to one - or more DHCP servers on other subnets. - -OOPPEERRAATTIIOONN - The DHCP Relay Agent listens for DHCP requests on all - interfaces attached to a host, or only on those interfaces - specified on the command line with the _-_i flag. When a - query is received, it forwards it to the list of DHCP - servers specified on the command line. When a reply is - received, it is broadcast or unicast on the network from - whence the original request came. - - It is possible to specify a set of interfaces on which - dhcrelay will listen, so that if dhcrelay is connected - through one interface to a network on which there is no - DHCP server, but is connected on another interface to a - network on which there is a DHCP server, it will not relay - DHCP and BOOTP requests from the network on which the - server exists to that server. This is an imperfect solu- - tion. - -CCOOMMMMAANNDD LLIINNEE - The names of the network interfaces that dhcrelay should - attempt to configure may be specified on the command line - using the _-_i option. If no interface names are specified - on the command line dhcrelay will identify all network - interfaces, elimininating non-broadcast interfaces if pos- - sible, and attempt to configure each interface. - - If dhcrelay should listen and transmit on a port other - than the standard (port 67), the --pp flag may used. It - should be followed by the udp port number that dhcrelay - should use. This is mostly useful for debugging purposes. - - Dhclient will normally run in the foreground until it has - configured an interface, and then will revert to running - in the background. To run force dhcrelay to always run as - a foreground process, the --dd flag should be specified. - This is useful when running dhcrelay under a debugger, or - when running it out of inittab on System V systems. - - The name of at least one DHCP server to which DHCP and - BOOTP requests should be relayed must be specified on the - command line. - - - - 1 - - - - - -dhcrelay(8) dhcrelay(8) - - -SSEEEE AALLSSOO - dhclient(8), dhcpd(8), dhcrelay.conf(5), dhcre- - lay.leases(5) - -AAUUTTHHOORR - ddhhccrreellaayy((88)) has been written for the Internet Software - Consortium by Ted Lemon in cooperation - with Vixie Enterprises. To learn more about the Internet - Software Consortium, see hhttttpp::////wwwwww..vviixx..ccoomm//iisscc.. To learn - more about Vixie Enterprises, see hhttttpp::////wwwwww..vviixx..ccoomm.. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2 - -