netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Mayuresh Chitale <mchitale@gmail.com>
Cc: netdev@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: linux 2.6.16 routing problem
Date: Fri, 14 Jul 2006 06:31:23 -0600	[thread overview]
Message-ID: <20060714063123.A21577@openss7.org> (raw)
In-Reply-To: <d096a3ee0607140525r3e1fb9dbg399c87bb3fbe4205@mail.gmail.com>; from mchitale@gmail.com on Fri, Jul 14, 2006 at 05:55:10PM +0530

Mayuresh,

On Fri, 14 Jul 2006, Mayuresh Chitale wrote:
> 
> If anyone has solved similar problem or knows what causes this
> problem, please let me know.
> 
> Any suggestion is welcome.

Configure a static arp entry for the tester on the unit under test.
(Or configure the tester to respond to ARP queries.)

--brian


      reply	other threads:[~2006-07-14 12:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14 12:25 linux 2.6.16 routing problem Mayuresh Chitale
2006-07-14 12:31 ` Brian F. G. Bidulock [this message]

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=20060714063123.A21577@openss7.org \
    --to=bidulock@openss7.org \
    --cc=linux-net@vger.kernel.org \
    --cc=mchitale@gmail.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).