gnarlymarley Posted April 4, 2020 Share Posted April 4, 2020 The IPv6 ranges returned from the lacnic whois is being properly detected. It appears that most of the whois servers return inet6num, but lacnic seems to be returning inetnum. For documentation, the IPv4 seems to be coming back as NetRange for all whois. It would appear that lacnic is going to stay with this as they have used this since they started on IPv6. Can we have the code in the whois section be able to pick up lacnic's IPv6 range? The tracking URL that was fixed by the deputies on 24 Feb but have screenshot of before fix: https://www.spamcop.net/sc?id=z6618132220z787713e4d45691f5d7d62752a3a7f109z Forum post from 2013: http://forum.spamcop.net/topic/13290-gmail-spam-from-ipv6/ Forum post from 2018: http://forum.spamcop.net/topic/30227-cannot-find-ip-range-in-whois-outputno-reporting-addresses-found-for-200112f0601a902000150/ Whois refresh page: Quote Link to comment Share on other sites More sharing options...
gnarlymarley Posted July 9, 2020 Author Share Posted July 9, 2020 On 4/4/2020 at 7:51 AM, gnarlymarley said: most of the whois servers return inet6num, but lacnic seems to be returning inetnum one possible option would be to do a regex swap when the whois is pulled into the cache such as: s/inetnum/inet6num/ Quote Link to comment Share on other sites More sharing options...
gnarlymarley Posted November 3, 2020 Author Share Posted November 3, 2020 Or in perl speak: $whoisoutput =~ s/inetnum/inet6num/ if $whoisoutput =~ m/inetnum:.*?::/; The if is so IPv4 is ignored. Would be better to have full IPv6 address detection in place of the "::". Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.