* Betr.: " Bug#639184: tryton-server: Does not listen on IPv4 if "net.ipv6.bindv6only = 1"" (Mon, 12 Sep 2011 12:28:25 +0200):
Hi Michael,
> What I meant was that with "net.ipv6.bindv6only = 1" it is not possible to
> have tryton-server listen on both IPv4 and IPv6 sockets at the same time.
> This is a bit of a show-stopper for dual-stack networks.
Citing from /etc/sysctl.d/bindv6only.conf:
# When disabled, IPv6 sockets will also be able to send and receive IPv4
# traffic with addresses in the form ::ffff:192.0.2.1 and daemons listening
# on IPv6 sockets will also accept IPv4 connections.
# When IPV6_V6ONLY is enabled, daemons interested in both IPv4 and IPv6
# connections must open two listening sockets.
# This is the default behaviour of almost all modern operating systems
It seems not to be very logical for me to require a daemon to listen on both
sockets instead of accepting IPv4 connections on the IPv6 socket (by unsetting
net.ipv6.bindv6only). But it is easily possible, that I am missing a point.
Could you explain to me, why you want to enforce the net.ipv6.bindv6only
setting, while you are interested in accepting IPv4 connections to trytond?
--
Mathias Behrle
MBSolutions
Gilgenmatten 10 A
D-79114 Freiburg
Tel: +49(761)471023
Fax: +49(761)4770816
http://m9s.biz
UStIdNr: DE 142009020
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6
signature.asc
Description: PGP signature
