Source: ejabberd
Version: 18.01-2
Severity: important
Tags: ipv6

ejabberd 18.01 fails hard when one of the SQL or LDAP hosts does not
have an A record and is IPv6 only. Providing an IPv6 address directly in
the configuration also fails. It looks like ejabberd does simply not
support AF_INET6 for its client sockets.

With IPv4 addresses running out on our infrastructure, we wanted to drop
IPv4 from all hosts not used directly from outside, and ejabberd turned
out to be a showstopper there because it cannot use our databases
anymore that way.

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Reply via email to