From 6f75d5460b12d6f57b3671d71d889747da0074cc Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Thu, 7 Aug 2008 09:07:27 +0200 Subject: bugfix: IPv6 addresses could not be specified in forwarding action New syntax @[addr]:port introduced to enable that. Root problem was IPv6 addresses contain colons. (backport from 3.21.3) --- doc/rsyslog_conf.html | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'doc/rsyslog_conf.html') diff --git a/doc/rsyslog_conf.html b/doc/rsyslog_conf.html index bf878e82..25298d33 100644 --- a/doc/rsyslog_conf.html +++ b/doc/rsyslog_conf.html @@ -535,6 +535,15 @@ framing and maximum compression to the host 192.168.0.1 at port 1470.

In the example above, messages are forwarded via UDP to the machine 192.168.0.1, the destination port defaults to 514. Messages will not be compressed.

+

Note that IPv6 addresses contain colons. So if an IPv6 address is specified +in the hostname part, rsyslogd could not detect where the IP address ends +and where the port starts. There is a syntax extension to support this: +put squary brackets around the address (e.g. "[2001::1]"). Square +brackets also work with real host names and IPv4 addresses, too. +

A valid sample to send messages to the IPv6 host 2001::1 at port 515 +is as follows: +

*.* @[2001::1]:515 +

This works with TCP, too.

Note to sysklogd users: sysklogd does not support RFC 3164 format, which is the default forwarding template in rsyslog. As such, you will experience duplicate hostnames if rsyslog is the sender and sysklogd is the -- cgit