Hexcode in place of source/destination IP address in Audit logs

Unsub Shafiq <[email protected]>
Newsgroups gmane.comp.apache.mod-security.user
Message-ID <[email protected]>
Hi,

I recently installed ModSecurity on Ubuntu 18.04.4 LTS following the 
usual instruction available at the following links; however this time 
around I have noticed that ModSecurity Audit Logs are printing out some 
kind of hexcode instead of the source and destination IP addresses in 
Section-A of the log file. What could be the cause of this? The hex does 
not seem to be valid IPv4 addresses either.

https://github.com/SpiderLabs/ModSecurity/tree/v3/master

https://github.com/SpiderLabs/ModSecurity/wiki/Compilation-recipes-for-v3.x#ubuntu-1504

Sample:

[28/Apr/2020:02:04:59 +0500] 1588021499 0x55a9de249950 49272 
0x55a9c93bb0d0 443
[28/Apr/2020:02:05:00 +0500] 1588021500 0x55a9ec102e50 49272 
0x55a9ec20a4b0 443
[28/Apr/2020:02:05:01 +0500] 1588021501 0x55a9d36b63e0 49272 
0x55a9ed0e6ee0 443
[28/Apr/2020:02:05:01 +0500] 1588021501 0x55a9bcb8cb00 49272 
0x55a9bd55f780 443

-- 
*Unsub Shafiq*

_______________________________________________
mod-security-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mod-security-users
Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs:
http://www.modsecurity.org/projects/commercial/rules/
http://www.modsecurity.org/projects/commercial/support/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.