Summary: | app-admin/syslog-ng: IPv6 does not work even with ipv6 useflag set | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aaron Jones <me> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aaron Jones
2012-07-06 22:32:52 UTC
[I] app-admin/syslog-ng Available versions: 3.2.5!t ~3.3.5!t ~3.3.5-r1!t {caps hardened ipv6 json mongodb +pcre selinux spoof-source sql ssl static tcpd} Installed versions: 3.2.5!t(10:52:29 PM 07/06/2012)(hardened ipv6 -caps -pcre -selinux -spoof-source -sql -ssl -tcpd) Homepage: http://www.balabit.com/products/syslog_ng/ Description: syslog replacement with advanced filtering features Follow-up: On the other side (the machine receiving the messages), you also use a udp() or tcp() statement, but inside a source {} block, and without arguments. For example: ---- source s_otherboxes { tcp(); }; ---- But when you start it, it uses only an IPv4 socket: abraxas ~ # lsof -nPi | grep syslog syslog-ng 16621 root 7u IPv4 6247842 0t0 TCP *:514 (LISTEN) It should use an IPv6 socket (when /proc/sys/net/ipv6/bindv6only is set to 0), or one socket for each protocol. Hum. It seems that even with IPv6 enabled, you still have to go out of your way to make it use it. You need udp6() and tcp6() instead of udp() and tcp(). Nevermind. RESOLVED INVALID. |