# long standing regression: IPv4/IPv6 filter broken in ansible 2.x (works with 1.9.x) #14829

**URL:** <https://forum.ansible.com/t/long-standing-regression-ipv4-ipv6-filter-broken-in-ansible-2-x-works-with-1-9-x-14829/24700>\
**Category:** Ansible Developer\
**Created:** [June 12, 2017, 3:57pm UTC](https://forum.ansible.com/t/long-standing-regression-ipv4-ipv6-filter-broken-in-ansible-2-x-works-with-1-9-x-14829/24700 "2017-06-12T15:57:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nusenu](https://avatars.discourse-cdn.com/v4/letter/n/4da419/32.png) [@nusenu](https://forum.ansible.com/u/nusenu)\
**Post date:** [June 12, 2017, 3:57pm UTC](https://forum.ansible.com/t/long-standing-regression-ipv4-ipv6-filter-broken-in-ansible-2-x-works-with-1-9-x-14829/24700/1 "2017-06-12T15:57:00Z")

</div>

Hi,

a regression [1] in the IP filter has been reported on 2016-03-06 and  
hasn't seen much progress since then.

Would it help if this github issue would loose the "in progress" tag to  
attract some attention? (so it does not get lost?)

If so:  
Could someone with the necessary permission remove the  
"in progress" and  
"affects\_2.0" tags  
and add a "affects\_2.4" tag?

thanks,  
nusenu

[1] [https://github.com/ansible/ansible/issues/14829](https://github.com/ansible/ansible/issues/14829)