Hi, on Wed, Oct 12, 2005 at 12:46:05 +0100, Jamie L. Penman-Smithson wrote:
> On Wed, 2005-09-07 at 17:44 +0200, Marco Nenciarini wrote:
> > Your rule does not fit the case that the client have an ipv6 ip. Yhis
> > is the log:
> >
> > Sep 7 17:41:12 lorien pop3-login: Login: [EMAIL PROTECTED]
> > [2001:1418:13:10::1]
>
> Adjusted for next release:
>
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ (imap|pop3)-login: Login:
> [.[:alnum:[EMAIL PROTECTED] \[(::ffff:)?[:0-9.]+\]$
While the given example log entry unfortunately does not show it, an
IPv6 address does use hex digits, ie. the address of the box I'm
writing this on is 2001:1638:1810::201:2ff:fe0d:6cec, which would not
be matched by the pattern (::ffff:)?[:0-9.]+ used above (and the other
rules I didn't quote).
Thus a correct pattern to match an IPv4 or IPv6 address would be:
[0-9a-f.:]+
elmar
--
.'"`. /"\
| :' : Elmar Hoffmann <[EMAIL PROTECTED]> ASCII Ribbon Campaign \ /
`. `' GPG key available via pgp.net against HTML email X
`- & vCards / \
signature.asc
Description: Digital signature
