Hello everyone,

I've experienced some strange problems with IP-NAT and would like
to get an explanation and a fix, if possible. Here goes:

I have a tiny home network of three machines:

 maailma is a pentium box, running NetBSD 1.3.3. This machine is
connected to internet through ppp0 with dynamic address. It also
has NE2000 ISA card that shows up as ne1.
 idiootti is a 486 machine running 1.3.3. It is connected to
maailma through ne1.
 wahoo is Amiga running 1.3.3 and also AmigaOS. It is connected
to idiootti using slip (Amiga ethernet cards are not expensive,
they are really expensive)

maailma is 192.168.0.2, idiootti 192.168.0.3 and wahoo
192.168.0.1. Ipnat.conf on maailma is as follows:

map ppp0 192.168.0.0/24 -> 0/32 portmap tcp/udp 10000:40000
map ppp0 192.168.0.0/24 -> 0/32

For some reason ipnat -l complains about bad addresses and
stuff and shows me nothing. maailma kernel has IP filter,
GATEWAY option and all the stuff.

 Inside the LAN everything works great and from
maailma access to 'net via ppp0 has no problems. Strange
things start to happen once wahoo or idiootti attempt to
access WWW pages (passive ftp, DNS, pinging, they work.
This mail was sent from wahoo (running AmigaOS), modem connected
to maailma).

Lynx and Mozilla both fail on a wide range of URL's (www.lynx.org,
www.qnet.fi (my ISP) are good examples) but surprisingly they
can also access some (www.netbsd.org for example).

Now, I'd like to get that HTTP working. How can it be that
some addresses work, some don't. To make it all astonishing,
AmigaOS running the Miami TCP/IP stack and Voyager
WWW browser works with EVERY URL I threw at it! With proxies
and without. No problems there!

What is wrong with the NetBSD access? How to make it work?
On the NetBSD, name lookup is OK, same for HTTP connection
and request but lynx and mozilla both just wait and wait
with: HTTP request sent; waiting for reply.

-- 
Arto Huusko
E-Mail : arto.huusko@pp.qnet.fi
WWW URL: www.qnet.fi/ahuusko/