Geoip not able to use IPv6 address with zone ID

[jsoriano]

IP grok pattern correctly parses IPv6 addresses with zone ids, but if these addresses are used with the geoip processor it fails with errors like '::1%0' is not an IP string literal..

To avoid confusion I think that geoip module should accept zone ids, even if they are not relevant in this case and ignored.

Seen in elastic/beats#9836

[elasticmachine]

Pinging @elastic/es-core-features

@jsoriano I would love to start on this issue , but I'm newbie to this.. how can I contribute?

[jsoriano]

Hi @Asitha26, this is great 🙂

To start please take a look to the contributing guidelines.

You can find the code of the geoip module using these addresses in modules/ingest-geoip/src/main/java/org/elasticsearch/ingest/geoip/GeoIpProcessor.java and the code parsing the address in server/src/main/java/org/elasticsearch/common/network/InetAddresses.java.

I have been taking a quick look and the java class for IPV6 addresses (https://docs.oracle.com/javase/10/docs/api/java/net/Inet6Address.html) supports zone ids (as scope ids), we could add support for that on InetAddresses when parsing the address and when instantiating the InetAddress.

thanks, I'll have a look

[jakelandis]

Also please note that this change should constrained to the geo-ip plugin and not a generic change to Elasticsearch. (see #22400 (comment))