> On Wed, 5 Dec 2001, Richard Rauch wrote:
>
> > Oh, I forgot to add, my ipnat.conf (very basic):
> >
> >  /~~~ ipnat.conf
> >
> > map ppp0 192.168.1.1/16 -> 0/32 proxy port ftp ftp/tcp
> > map ppp0 192.168.1.1/16 -> 0/32 portmap tcp/udp 40000:60000
> > map ppp0 192.168.1.1/16 -> 0/32
> >
> >  \___ ipnat.conf
> >
> > ...lifted from the NetBSD Guide, actually.  (The example in
> > /usr/share/examples/ had a bogus trailing ``portmap'' that ipnat didn't
> > like on one line, and didn't have the FTP proxy, which I assume that I
> > need.)
>
> So it works now?

When I wrote the above, no.  At least not when trying to connect to
ftp.netbsd.org and www.netbsd.org with ftp & http respectively.

For a few minutes, ftp to ftp.netbsd.org worked when I came back this
morning.  But now that's stalling out again.  Using a web browser to
connect to www.netbsd.org has not yet worked a single time.


Everything works if I'm on the machine that's directly connected to the
'net.  At LEAST these two services fail when I try to connect to at LEAST
those two hosts.  But I CAN, e.g., point a web browser at
http://www.math.rice.edu/ from behind the NAT and everything works.

Like I asked previously: Is there something funky about the NetBSD site?
(It looks rather as if there is...)  If so, what (if anything) can I do
about it?

Not being able to connect to the NetBSD sites is rather a pain, since
pkgsrc often ends up going there for source tarballs (e.g., when the other
tarballs found don't match the checksum).  I also read these mailing lists
off of the NetBSD web pages, rather than having them stream into my
mailbox.  (Though I can get around that by running a browser on my
NAT/gateway box.)


  ``I probably don't know what I'm talking about.'' --rauch@math.rice.edu