From owner-freebsd-hackers  Tue Sep  3 11:48:49 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA18021
          for hackers-outgoing; Tue, 3 Sep 1996 11:48:49 -0700 (PDT)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA18013
          for <freebsd-hackers@freebsd.org>; Tue, 3 Sep 1996 11:48:45 -0700 (PDT)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA22697; Tue, 3 Sep 1996 11:47:09 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22) by whistle.com via smap (V1.3)
	id sma022695; Tue Sep  3 11:46:56 1996
Message-ID: <322C7CD8.41C67EA6@whistle.com>
Date: Tue, 03 Sep 1996 11:45:44 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: kavitha <kavitha@watson.ibm.com>
CC: freebsd-hackers@freebsd.org
Subject: Re: host specific route.
References: <9609031512.AA20057@hawpub1.watson.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

kavitha wrote:
> 
> Hello,
I think that
your specific route is 'superceding' the ARP entry for that machine....

You may be able to hack teh arp routines to set the flags you want

> 
>      I'm using FreeBSD 2.1.0 on Thinkpad. When I create a host specific route
> to a machine on the directly connected network I'm not able to ping that
> machine.