In message <Pine.3.89.9503181041.C26030-0100000@gold.interlog.com>, Steven Vetz
al writes:
> On Fri, 17 Mar 1995 Todd.Williamson@cs.cmu.edu wrote:
> 
> > OR c) (assuming that you're using ethernet) - add a published ARP
> > entry on the ethernet-connected machine, indicating that packets for
> > your remote machine should be sent to it:
> > 
> > arp -s 204.191.16.2 <ethernet address of 204.191.161.9> pub
> 
> 204.191.16.9 is one side of a slip interface; it doesn't have an ethernet 
> address...

In message <Pine.3.89.9503181014.A26030-0100000@gold.interlog.com>, Steven Vetz
al writes:
> 
> I'm not sure that I adequately described my situation...
> 
>   [Router]---isdn---[Bridge]---ethernet---[Server]---slip---[Remote]
> 204.191.16.1      204.191.16.253     204.191.16.2 ed0     204.191.16.3
>                                      204.191.16.9 sl0
> |                                             |                      |
> +------Physical Network #1--------------------+-Physical Network #2--+

Proxy arp on the NetBSD box should enable communication in the left-to-right
direction.

Try:

	arp -s 204.191.16.3 <ethernet address of 204.191.16.2> pub

A default route on your [Remote] machine to 204.19.16.9 should give you
connectivity right-to-left.

> setting 204.191.16.9 as the default route lets me do 
> whatever I want with the server...

It should also get you access to the rest of the world once proxy arp is
in place and they can answer you.

Wayne