[re. NAT]
> As outgoing connections, they will "Just work". Incoming can be done with
> redirect rules in the ipnat configuration.

Hrm.  ping works.  Name service works.  traceroute works.

But, attempting to connect to {www,ftp}.netbsd.org seems to freeze up.
Here's an FTP example:

 /~~~ ftp

$ ftp ftp.netbsd.org
Trying 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea...
ftp: connect to address 3ffe:8050:201:1860:2a0:c9ff:feed:b7ea: No route to
host
Trying 204.152.184.75...
Connected to ftp.netbsd.org.
220 ftp.netbsd.org FTP server (NetBSD-ftpd 20010417) ready.
Name (ftp.netbsd.org:rkr): ftp
331 Guest login ok, type your name as password.
Password:
230-

 \___ ftp


...it freezes right there.  (Eventually it times out.)

Should those IPv6 addresses be worrying me?


Is there something special about the NetBSD site(s) that I need to handle?



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