From owner-freebsd-current Thu Jan 27 12: 6:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 403CB14DE9 for ; Thu, 27 Jan 2000 12:06:22 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id B01C91E006; Thu, 27 Jan 2000 15:06:19 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id PAA09338; Thu, 27 Jan 2000 15:06:19 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id MAA10100; Thu, 27 Jan 2000 12:06:18 -0800 (PST) Message-Id: <200001272006.MAA10100@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: shin@nd.net.fujitsu.co.jp Subject: Re: With feature freeze being in place Cc: current@freebsd.org References: <20000122210136.B18600@daemon.ninth-circle.org> <200001271903.LAA09566@windsor.research.att.com> <20000128042719G.shin@nd.net.fujitsu.co.jp> Date: Thu, 27 Jan 2000 12:06:18 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Also, usual tools, rlogin, rlogind, rsh, rshd, telnet, >telnetd, ftp, ftpd, and inetd are already IPv6 capable. Hm. rlogin and rsh attempt to connect, but my inetd isn't listening; do I have to update inetd.conf to get inetd to listen on IPv6 addresses? telnet can't parse ::1: emachine% telnet ::1 ::1: Unknown host ftp prints a very odd message: emachine% ftp ::1 ftp: No control connection for command. I guess ftp parsed ::1 as a URL. What a pain. I tried putting "::1 v6-localhost" in /etc/hosts, but telnet and ftp couldn't use v6-localhost as a name while ping6, traceroute6, rlogin and rsh could. So far, the only tools I've been able to use to emit v6 packets are ping6, traceroute6, rlogin and rsh. I don't have any other v6 machines on my network, so I've just been using loopback. >Wmmm, maybe I should merge ping and pin6 before code freeze... I think it'd be very handy for the native ping (and traceroute, if possible) to be IPv4/IPv6 capable. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message