# IP address not recognized as valid by geocoding processor **URL:** \ **Category:** Elasticsearch\ **Created:** [March 9, 2018, 8:47pm UTC](https://discuss.elastic.co/t/ip-address-not-recognized-as-valid-by-geocoding-processor/123344 "2018-03-09T20:47:56Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![David9](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/david9/32/42150_2.png) [@David9](https://discuss.elastic.co/u/David9)\ **Post date:** [March 9, 2018, 8:47pm UTC](https://discuss.elastic.co/t/ip-address-not-recognized-as-valid-by-geocoding-processor/123344/1 "2018-03-09T20:47:56Z")
This page [IP field type | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/ip.html) appears to confirm that a netmask on the end of an IP address is allowable when geocoding IP addresses, e.g. 192.168.0.0/16, however we are getting this error when geocoding: > "java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: '96.231.138.0/24' is not an IP string literal.") ---
**Author:** ![shanec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shanec/32/4004_2.png) [@shanec](https://discuss.elastic.co/u/shanec)\ **Post date:** [March 9, 2018, 9:53pm UTC](https://discuss.elastic.co/t/ip-address-not-recognized-as-valid-by-geocoding-processor/123344/2 "2018-03-09T21:53:39Z")
Can you confirm what version of Elasticsearch you're using and where you're trying to provide the CIDR (e.g. an example `PUT`, `GET`, etc that show what you're running into)? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 6, 2018, 10:07pm UTC](https://discuss.elastic.co/t/ip-address-not-recognized-as-valid-by-geocoding-processor/123344/3 "2018-04-06T22:07:56Z")
Closed on April 6, 2018, 10:07pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.