Date: Sun, 28 Jul 2002 16:51:33 +0000 (UTC) From: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-ports@freebsd.org Subject: net.inet6.ip6.v6only repercussions on -CURRENT Message-ID: <ai17el$2as1$1@kemoauc.mips.inka.de>
next in thread | raw e-mail | index | archive | help
On -CURRENT, the value of the net.inet6.ip6.v6only sysctl variable
now defaults to 1. This means that a wildcard bind(2) to an AF_INET6
socket will not receive IPv4 traffic any longer. See inet6(4).
In practical terms, server processes that are to deal with IPv4 and
IPv6 traffic will have to bind to two sockets, one for each protocol
family. Servers that fail to do so and rely on the old IPv4 mapped
addresses will end up handling IPv6 only.
Symptoms on typical IPv6-enabled but only IPv4-connected hosts are
that the daemons appear to be running fine but can't be reached.
netstat -a will show a protocol type of tcp6 instead of the expected
tcp46.
Two ports I know that are victim to this are
net/rsync (rsync --daemon)
www/apache2
There are probably more.
--
Christian "naddy" Weisgerber naddy@mips.inka.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ai17el$2as1$1>