Thanks guys. It is now working perfectly.

1. IPNAT needs to set up at 192.168.1.1 to cater for packets coming from
192.168.2.0/24
2. route table needs to setup for 192.168.1.1 so that it knows where to send
packets back to 192.168.2.0 by
route add 192.168.2.0 192.168.1.21 (x.x.x.21 is the wireless router)
3. As Paul said the packets are going in one direction originally from
192.168.2.0 to 192.168.1.0 but not vice versa.

It is now resolved and I am typing away at the front yard about 30m away
from the wireless BSD server.

Regards
David
----- Original Message -----
From: Andrew Gillham <gillham@vaultron.com>
To: Paul Goyette <paul@whooppee.com>
Cc: Andrew Gillham <gillham@vaultron.com>; dkwok <dkwok@iware.com.au>;
<port-i386@netbsd.org>
Sent: Tuesday, September 11, 2001 2:27 PM
Subject: Re: Routing


> On Mon, Sep 10, 2001 at 08:49:12PM -0700, Paul Goyette wrote:
> > Hmmm.  If the netmask is set right in the ifconfig.xxx then that network
> > route should be there automatically.  But that's why I asked for the
> > netstat output!
>
> No, the "gateway computer" doesn't have an interface on 192.168.2.x, so
> it wouldn't have a route automatically.  The "router" machine between
> the wired and wireless would of course, but that doesn't help help the
> NAT machine's routing table. :)
>
> -Andrew
>