# IPv6 filter broken in ansible 2.x - light at the end of the tunnel?

**URL:** <https://forum.ansible.com/t/ipv6-filter-broken-in-ansible-2-x-light-at-the-end-of-the-tunnel/21746>\
**Category:** Ansible Developer\
**Tags:** galaxy-ng\
**Created:** [June 12, 2016, 1:11pm UTC](https://forum.ansible.com/t/ipv6-filter-broken-in-ansible-2-x-light-at-the-end-of-the-tunnel/21746 "2016-06-12T13:11:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nusenu1](https://avatars.discourse-cdn.com/v4/letter/n/db5fbb/32.png) [@Nusenu1](https://forum.ansible.com/u/Nusenu1)\
**Post date:** [June 12, 2016, 1:11pm UTC](https://forum.ansible.com/t/ipv6-filter-broken-in-ansible-2-x-light-at-the-end-of-the-tunnel/21746/1 "2016-06-12T13:11:25Z")

</div>

Hi,

a bit over 3 months ago I reported a regression in ansible 2.x [1]  
that prevents me from migrating my role [2] to ansible 2.x.

On 2016-03-17 James Cammarata labeled the issue 'in progress', but since  
then nothing happened anymore.

Is there light at the end of the tunnel? 🙂

(how long will ansible 1.9 remain supported?)

thanks,  
nusenu

[1] [https://github.com/ansible/ansible/issues/14829](https://github.com/ansible/ansible/issues/14829)  
[2] [https://galaxy.ansible.com/nusenu/relayor/](https://galaxy.ansible.com/nusenu/relayor/)