Peter06/14/2022, 11:00 AM
for a connection where the
is recorded as
seph06/14/2022, 1:43 PM
Peter06/14/2022, 6:56 PM
seph06/14/2022, 7:03 PM
. It don’t see a reverse form.
select inet_aton("22.214.171.124") as ipInt ipInt = 16777477
and then convert it. But it would be some kinda grotty work.
Peter06/15/2022, 11:22 AM
, this only supports a single address family, whereas the replacements
(reverse) support multiple address families - currently, IPv4 and IPv6. I'll have a look into what may be required in order to canonicalise this data at query time, as logs for network connections shipped off-box would otherwise require upstream processing to ensure that the same "encoding" is used for IPv4 connections. Otherwise, if I bucket the data, I'll have one bucket for
and another for
despite them being the same address.
seph07/05/2022, 1:38 PM
, but at some level they seem reasonable to add as SQL functions along side the existing