blymn@awadi.com.AU (Brett Lymn) writes:
...
> OK now we are getting somewhere.  The next thing to check is if the
> routers know that to get to your NetBSD box they need to use
> 204.191.16.9 as the gateway.  I would guess that the router just sees
> the machine 204.191.16.2 on the same subnet and blasts the packet out
> the correct interface when it should be forwarding the packet to
> 204.191.16.9 to be sent down the SL/IP interface.  What you need to do
> is:
> 
>  a) update the router's routing tables to define 204.191.16.9 to be
>     the gateway for 204.191.16.2 
> 
> OR b) put 204.191.16.2 on an unallocated
>       subnet and tell the router that 204.191.16.9 is the gateway for
>       that subnet.
> 

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

> If you do not have control of the router then you are more or less
> stuck :-(
> 
> -- 
> Brett Lymn, Computer Systems Administrator, AWA Defence Industries
> ============================================================================\
===
> "It's fifteen hundred miles to Ankh-Morpork" he said.  "We've got
> three hundred and sixty three elephants, fifty carts of forage, the
> monsoon's about to break and we're wearing ... we're wearing ... sort
> of things, like glass, only dark... dark glass things on our eyes..."
>         - Terry Pratchett "Moving Pictures".

-Todd.