For better readability and also domain stats, the way innreport gathers domains should be improved.
The current code only removes the first component of the domain, which is not enough in some cases like ec2-13-236-155-204.ap-southeast-2.compute.amazonaws.com and ec2-18-184-57-186.eu-central-1.compute.amazonaws.com which would end up in several lines gathered by AWS datacenters whereas we would just want a report of AWS connections from *.compute.amazonaws.com.
Same thing for other cases. Below a current example:
To improve the report, we'll just keep up to the last 3 components of the hostname. (Some country code top-level domains have 2 components, like .co.uk so we need a minimum of 3 components, which looks fine during my testings.)
The unknown domain ? corresponds to an unresolved IPv6 address. I see that innreport currently has code only for IPv4 addresses. It should also be fixed while improving these statistics.
For better readability and also domain stats, the way innreport gathers domains should be improved. The current code only removes the first component of the domain, which is not enough in some cases like
ec2-13-236-155-204.ap-southeast-2.compute.amazonaws.com
andec2-18-184-57-186.eu-central-1.compute.amazonaws.com
which would end up in several lines gathered by AWS datacenters whereas we would just want a report of AWS connections from*.compute.amazonaws.com
. Same thing for other cases. Below a current example:To improve the report, we'll just keep up to the last 3 components of the hostname. (Some country code top-level domains have 2 components, like
.co.uk
so we need a minimum of 3 components, which looks fine during my testings.)The unknown domain
?
corresponds to an unresolved IPv6 address. I see that innreport currently has code only for IPv4 addresses. It should also be fixed while improving these statistics.