--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Apr 07, 2002 at 03:05:41PM -0500, Frederick Bruckman wrote:
> On Sun, 7 Apr 2002, Julio Merino wrote:
>=20
> > It also shows up as IPv6 to me, but after failing, it connects fine
> > trought IPv4. I think this is setup this way so you can use 6bone
> > (or maybe any other 6 to 4 translation).
>=20
> Yours actually says "Connected"? I would expect that if you were not
> set up for ipv6, you would get "no route to host".
>=20

Nope, I don't. I was just throwing an idea... I may try to setup 6bone
to see if it works. As it works now:

/home/juli$ 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 20020201) ready.
[...]

Regards

--=20
Of course it runs NetBSD - http://www.netbsd.org
Netiquete (spanish): http://www.seei.es/netiquet.htm

Julio Merino <slink@unixbsd.org> #18961975

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE8sK6Tzz00ZOPKycwRAp9QAKCBf/LiYzPqWy7Jc0ZsSl9A2DD70gCfbwuP
Pv3VIgcpSYExBajMYn7w0Fo=
=SXjF
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--