Re: ping and inetd
On Aug 04, Noah Meyerhans <firstname.lastname@example.org> wrote:
>If iputils-ping becomes the default, does that mean that ping6 should be
>installed by default, or should the package be split? Personally, since
I do not think there is any reason to split it.
>It seems that this version of inetd will create separate listening
>sockets for e.g. tcp4 and tcp6, even on the same service.
>Unfortunately, this won't work on Linux due to its lack of support for
>the IPV6_V6ONLY socket option. Basically, unless you're running the
>USAGI kernels, tcp6 in inetd.conf will behave the same as tcp46. This
>really needs to be documented.
I'll write a decent README.Debian before uploading it to main. Please
note that support for "tcp46" is implemented as an undocumented local
hack. My rationale is that without USAGI there is no way to properly
support tcp6 (while binding to the wildcard address) and with USAGI
tcp46 does not exist, so people should just use tcp6 or tcp4+tcp6
depending on their kernel.
>It seems to me that inetd could create only a single IPv6 socket, which
>would then listen for both IPv6 and v4 connections and pass them off to
This is what it does:
inetd 14737 md 4u IPv6 16928 TCP ip6-localhost:2222 (LISTEN)
inetd 14737 md 5u IPv6 16930 TCP *:2220 (LISTEN)
inetd 14737 md 6u IPv4 16932 TCP *:2224 (LISTEN)
inetd 14737 md 7u IPv6 16934 TCP *:2226 (LISTEN)
ip6-localhost:2222 stream tcp46 nowait md /usr/sbin/tcpd /usr/sbin/in.telnetd
2220 stream tcp46 nowait md /usr/sbin/tcpd /usr/sbin/try-from
2224 stream tcp4 nowait.3 md /usr/sbin/tcpd /usr/sbin/try-from
2226 stream tcp6 nowait md /usr/sbin/tcpd /usr/sbin/try-from
With a non-USAGI kernel there is no difference between tcp6 and tcp46.