From owner-freebsd-hackers  Wed May  7 16:18:48 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA24254
          for hackers-outgoing; Wed, 7 May 1997 16:18:48 -0700 (PDT)
Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA24246
          for <hackers@freebsd.org>; Wed, 7 May 1997 16:18:45 -0700 (PDT)
Message-Id: <199705072318.QAA24246@hub.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA039247015; Thu, 8 May 1997 09:16:55 +1000
From: Darren Reed <avalon@coombs.anu.edu.au>
Subject: Re: nat and arp
To: dkite@icomnet.com (Doug Kite)
Date: Thu, 8 May 1997 09:16:55 +1000 (EST)
Cc: hackers@freebsd.org
In-Reply-To: <3370ED28.4D66@icomnet.com> from "Doug Kite" at May 7, 97 04:59:20 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In some mail from Doug Kite, sie said:
> 
> Do I have to manually set up proxy arp entries on the external interface
> in order for nat to work?
> 
> Here is the rule:
> map ep0 192.168.5.11/32 -> 192.168.2.159/32
> 
> When I try to ping from the "internal" host (5.11), tcpdump on ep0 shows
> the echo request going out, then the arp request from the "external"
> host (2.2). But, of course, nothing answers, so no reply is issued.

Yes, you do.  Of course, I'd suggest that this is a bug: it should cache
the ethernet address it received the packet from as belonging to the IP#
(if that IP# isn't already in the arp cache).  Or is there a reason that
this isn't done ?

Darren