Release 1.1 - AWX - UndefinedVariable about ansible-ipsec HOT 6 CLOSED

Change line in ipsec-tools.conf to look like:
{% for ipv in ( 'ansible_default_ipv4' ) %}
instead of:
{% for ipv in ( 'ansible_default_ipv4', 'ansible_default_ipv6' ) %}
The ipv6 part is poorly handled and fails.

This should be fixed by #4

from ansible-ipsec.

@piotron IPv6 parts should be only enabled if there's a routable IPv6 address on the host , as determined by ansible_default_ipv6 structure, and only then ansible_default_ipv6.address is accessed. Do you have fact caching enabled? Are you using ipsec_forward: yes?

from ansible-ipsec.

@kravietz I'm not using fact caching, I'm using setup on beginning of each playbook.

- hosts: all
  pre_tasks:
    - setup:
  tasks:
    - import_role:
        name: kravietz.ipsec
      vars:
        ipsec_secret: "{{ IPSEC_SECRET | mandatory }}"
        ipsec_policy: use
        ipsec_open_icmp: yes
        ipsec_open_ssh: yes
        ipsec_forward: yes
      become: true
      become_user: root

from ansible-ipsec.

Change line in ipsec-tools.conf to look like:
{% for ipv in ( 'ansible_default_ipv4' ) %}
instead of:
{% for ipv in ( 'ansible_default_ipv4', 'ansible_default_ipv6' ) %}
The ipv6 part is poorly handled and fails.

from ansible-ipsec.

Sorry for the delay everyone. I'm in the process in rewriting these templates to make sure they are triggered only when needed.

from ansible-ipsec.

Unfortunately ipsec_forward is a hell of complexity to implement. I have added it for the use with Docker primarily, but getting traffic into IPSec tunnel mode from virtual interfaces may require slightly different approach, so please use with caution.

from ansible-ipsec.