From: "Jarlath Burke" <burkejarlath@eircom.net>
To: <davem@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: RARP server support on Linux 2.4
Date: Thu, 2 May 2002 15:48:41 +0100 [thread overview]
Message-ID: <000701c1f1e8$739cff20$a07fa8c0@mofo> (raw)
Thanks for the reply - I'm still somewhat confused.
Is all I have to do is add hardware to IP address
mappings in /etc/ethers and the rarpd daemon
will pick them up and add them to the kernel?
Is there any way to monitor what the kernel has
in it's rarp cache, similiar to running the rarp command
on the old 2.2.x kernels?
Thanks in advance,
Jarlath.
> -----Original Message-----
> From: David S. Miller [mailto:davem@redhat.com]
> Sent: 08 April 2002 16:55
> To: jarlath.burke@asitatech.com
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: RARP server support on Linux 2.4
>
>
>
> You have to maintain the ethernet address to IP address database
> in /etc/ethers.
next reply other threads:[~2002-05-02 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 14:48 Jarlath Burke [this message]
2002-05-02 15:28 ` RARP server support on Linux 2.4 Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 14:50 Jarlath Burke
2002-04-08 15:54 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000701c1f1e8$739cff20$a07fa8c0@mofo' \
--to=burkejarlath@eircom.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox