githubmirror/iputils

doc/rarpd.xml
184 строки5 KB
Philipp Kammerer
doc: Proofreading rarpd.xml
31 окт 2019, 19:57
31 окт 2019, 19:572059086
<refentry xmlns="http://docbook.org/ns/docbook" version="5.0"
xml:id="man.rarpd">

  <refentryinfo>
    <title>rarpd</title>
    <productname>iputils</productname>
  </refentryinfo>

  <refmeta>
    <refentrytitle>
      <application>rarpd</application>
    </refentrytitle>
    <manvolnum>8</manvolnum>
    <refmiscinfo class='manual'>iputils</refmiscinfo>
  </refmeta>

  <refnamediv>
    <refname>rarpd</refname>
    <refpurpose>answer RARP REQUESTs</refpurpose>
  </refnamediv>

  <refsynopsisdiv>
    <cmdsynopsis sepchar=" ">
      <command>rarpd</command>
      <arg choice="opt" rep="norepeat">
        <option>-AadevV</option>
      </arg>
      <arg choice="opt" rep="norepeat">
        <option>-b
        <replaceable>bootdir</replaceable></option>
      </arg>
      <arg choice="req" rep="norepeat">interface</arg>
    </cmdsynopsis>
  </refsynopsisdiv>

  <refsection xml:id="description">
    <info>
      <title>DESCRIPTION</title>
    </info>
    <para>Listens for RARP requests broadcasted by clients. If the MAC address
    of the client is found in <filename>/etc/ethers</filename> and the obtained
    hostname is resolvable to a valid IP address from the attached network,
    <command>rarpd</command> answers to the client with a RARPD reply
    and provides an IP address.</para>

    <para>To allow multiple boot servers on the network
    <command>rarpd</command> optionally checks if a Sun-like
    bootable image in the TFTP directory is present. It should be formatted like
    <emphasis remap="B">Hexadecimal_IP.ARCH</emphasis>. For example: To
    load sparc 193.233.7.98,
    <emphasis remap="I">C1E90762.SUN4M</emphasis> is linked to an
    image appropriate for SUN4M in the directory
    <filename>/etc/tftpboot</filename>.</para>
  </refsection>

  <refsection xml:id="warning">
    <info>
      <title>WARNING</title>
    </info>
    <para>This facility is deeply obsoleted by BOOTP and later DHCP
    protocols. However, some clients actually still need this to
    boot.</para>
  </refsection>

  <refsection xml:id="options">
    <info>
      <title>OPTIONS</title>
    </info>
    <variablelist remap="TP">
      <varlistentry>
        <term>
          <option>-a</option>
        </term>
        <listitem>
          <para>Listen on all available interfaces. Currently it is an
          internal option, its function is overwritten with the
          <emphasis remap="I">interface</emphasis> argument. It
          should not be used.</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <option>-A</option>
        </term>
        <listitem>
          <para>Listen not only to RARP but also ARP messages. Some
          rare clients use ARP for some unknown reason.</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <option>-v</option>
        </term>
        <listitem>
          <para>Be verbose.</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <option>-d</option>
        </term>
        <listitem>
          <para>Debug mode. Do not go to background.</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <option>-e</option>
        </term>
        <listitem>
          <para>Do not check for the presence of a boot image. Reply if
          MAC address resolves to a valid IP address using
          <filename>/etc/ethers</filename> database and DNS.</para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <option>-b</option>
          <emphasis remap="I">bootdir</emphasis>
        </term>
        <listitem>
          <para>TFTP boot directory. Default is
          <filename>/etc/tftpboot</filename></para>
        </listitem>
      </varlistentry>
      <varlistentry>
        <term>
          <option>-V</option>
        </term>
        <listitem>
          <para>Print version and exit.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsection>

  <refsection xml:id="see_also">
    <info>
      <title>SEE ALSO</title>
    </info>
    <para>
    <citerefentry>
      <refentrytitle>arping</refentrytitle>
      <manvolnum>8</manvolnum>
    </citerefentry>,
    <citerefentry>
      <refentrytitle>tftpd</refentrytitle>
      <manvolnum>8</manvolnum>
    </citerefentry>.</para>
  </refsection>

  <refsection xml:id="author">
    <info>
      <title>AUTHOR</title>
    </info>
    <para>
    <command>rarpd</command> was written by Alexey Kuznetsov
    &lt;kuznet@ms2.inr.ac.ru&gt;.</para>
  </refsection>

  <refsection xml:id="security">
    <info>
      <title>SECURITY</title>
    </info>
    <para>
    <command>rarpd</command> requires CAP_NET_RAW capability to
    listen and send RARP and ARP packets. It also needs
    CAP_NET_ADMIN to assist the kernel with ARP resolution; this
    is not strictly required, but some (to be more exact: most) of
    the clients are so badly broken that they are not able to answer
    to ARP before they are fully booted. This is no surprise, taking
    into account that clients using RARPD in 2002 are all
    unsupported relic creatures of the 90's and even earlier.</para>
  </refsection>

  <refsection xml:id="availability">
    <info>
      <title>AVAILABILITY</title>
    </info>
    <para>
    <emphasis remap="B">rarpd</emphasis> is part of the
    <emphasis remap="I">iputils</emphasis> package.</para>
  </refsection>
</refentry>