[syslog-ng] IPvANY patterndb challendge

Evan Rempel erempel at uvic.ca
Fri Oct 31 21:20:40 CET 2014

I now see this in all of the specifications, but alas my legacy application is not spart enough to
deal with an IPv6 address with a port number any different than an IPv4 address with a port number.

Oh how I love the consistency of vendor logs :-)

Thanks for your time.


On 10/31/2014 01:03 PM, Balazs Scheidler wrote:
> For the same reason the ipv6 address is enclosed in square brackets. Is that not the case?
> On Oct 31, 2014 4:24 PM, "Evan Rempel" <erempel at uvic.ca <mailto:erempel at uvic.ca>> wrote:
>     There are a number of occurrences in log lines that are of the form {address}:{port}
>     This is fine for IPv4 addresses <> which can be matched with @IPv4@:@NUMBER@
>     If the address is a complete IPv6 address with port 2607:f8f0:c10:fff:200:5efe:ce57:5330:123 the
>     same pattern can be used to match it @IPvAny@:@NUMBER@
>     If the IP address is a shortform IPv6 address such as ::ffff: and adding the port number
>     ::ffff: <>  this fails to be matched by @IPvAny@:@NUMBER@
>     Has anyone else seen bumped into this issue?
>     For anyone taking a stab at this, this page looks interesting
>     http://rosettacode.org/wiki/Parse_an_IP_Address

More information about the syslog-ng mailing list