>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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to