# No IPV6 Range Aggregation bucket?

**URL:** <https://discuss.elastic.co/t/no-ipv6-range-aggregation-bucket/144928>\
**Category:** Kibana\
**Created:** [August 17, 2018, 4:01pm UTC](https://discuss.elastic.co/t/no-ipv6-range-aggregation-bucket/144928 "2018-08-17T16:01:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Phrozyn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phrozyn/32/5207_2.png) [@Phrozyn](https://discuss.elastic.co/u/Phrozyn)\
**Post date:** [August 17, 2018, 4:01pm UTC](https://discuss.elastic.co/t/no-ipv6-range-aggregation-bucket/144928/1 "2018-08-17T16:01:45Z")

</div>

With 5.x ipv6 is supported in the IP type field now. However, it seems Kibana did not keep up.

If I remove my string fields and rely only on the ip type field in my ES mapping, and try to aggregate on it using Kibana, I can only aggregate on the ipv4 range type, and any other aggregations remove any ip fields from available terms.

Is it the same in 6.x too? Why is this not mentioned in any of the documentation?  
If it is in the documentation, it must be extremely buried because I can find no mention of "We support IPv6 in ES but not in Kibana visualizations"

edit: I played with this a bit more, and seems I can aggregate using "terms" but not "significant terms"

---

<div class="post-metadata">

**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\
**Post date:** [August 21, 2018, 9:54pm UTC](https://discuss.elastic.co/t/no-ipv6-range-aggregation-bucket/144928/2 "2018-08-21T21:54:46Z")

</div>

Yes, it appears you're right. Would you mind [opening a feature request](https://github.com/elastic/kibana/issues/new?template=Feature_request.md)? Thanks!

---

<div class="post-metadata">

**Author:** ![Phrozyn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/phrozyn/32/5207_2.png) [@Phrozyn](https://discuss.elastic.co/u/Phrozyn)\
**Post date:** [August 30, 2018, 3:43pm UTC](https://discuss.elastic.co/t/no-ipv6-range-aggregation-bucket/144928/3 "2018-08-30T15:43:18Z")

</div>

Feature Request made 🙂 Ty!

> <https://github.com/elastic/kibana/issues/22555>

Having something like this could greatly reduce the number of fields in a mapping needed, and prevents loss of functionality that exploding the mapping creates.

---

<div class="post-metadata">

**Author:** ![jonsmiteeww](https://avatars.discourse-cdn.com/v4/letter/j/c4cdca/32.png) [@jonsmiteeww](https://discuss.elastic.co/u/jonsmiteeww)\
**Post date:** [September 2, 2018, 6:14am UTC](https://discuss.elastic.co/t/no-ipv6-range-aggregation-bucket/144928/4 "2018-09-02T06:14:08Z")

</div>

I searched the forum but haven't found an answer.

I just changed my index template to set IP addresses to type:ip but now I get parser failed because not a valid ipv4 address for all ipv6. Is there a way to use this for all ipv4 and another type for ipv6?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 30, 2018, 6:21am UTC](https://discuss.elastic.co/t/no-ipv6-range-aggregation-bucket/144928/5 "2018-09-30T06:21:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.