Hello everybody, I’ve been searching for a solution a longer time now and hope you can help me. In our environment we have VM’s with two interfaces, each with several ip addresses and what I’d like to do is to get the interface-name by searching an ip address, just using the ansible-facts. My tes…

[Shakes tiny head] I had forgotten how horrid this could be in Ansible 2.9, but I was able to find an old box around here that has 2.9.18 on it, and got it working there. Not only does it require lots of extra |list terms, but also some |map('list') terms, and their order matters. Here’s the complet…

In your ansible facts (You can do a ansible -m setup localhost) and see there should also be a list of all IP addresses called ansible_all_ipv4_addresses and ansible_all_ipv6_addresses "ansible_facts": { "ansible_all_ipv4_addresses": [ "10.195.117.91" ], "ans…

Thanks for your reply. I was looking for a combination of an ip address and the interface name, so I think the ansible_ens192 for example is the only place to find it.

This is as close as I’ve been able to get. It works for me, but I’ve only defined one interface with a single secondary ipv4 address. - name: Get interface for ip '192.168.254.102' ansible.builtin.debug: msg: | {% set ivals = [] %} {% for ifval in ansible_inter…

Would something like this work? --- - hosts: all tasks: - name: Find the interface with IP 192.168.86.46 set_fact: interface_with_ip: "{{ item.key }}" when: "(item.value.ipv4 | selectattr('address', 'equalto', '192.168.86.46') | list) | length > 0" with_dict: "{{ ans…

Using {% … %} always feels like cheating, so I thought I’d give it another go sticking with pure filters. And by “pure” I don’t mean “sinless”, as what I came up with is abominable. But I really don’t see how else to attack such a problem given the handicap Jinja2 puts on coders. It’s like it can’t …

Thank you very much for your replies, I will try it out and give a response :grinning:

Trying your code I get this error message: msg: with_dict expects a dict

You’re right, I’m also surprised how complicated it is to do what I want while it’s really simple to see as a human looking at the dictionary. Honestly I don’t understand every detail of your code, but your approach looks good to me. When I’ve tried it in my playbook, I get this error message: it…

I used to get that a lot. Newer Ansibles do the Right Thing in most of those cases, and I’ve been pleasantly spoiled. If your Ansible is old enough to throw that error, toss in a | list | in front of items2dict.

yes, unfortunately I will not get a newer version in the near future :neutral_face: I still get the same error: msg: |- Unexpected templating type error occurred on ({{ ( ansible_interfaces | zip( ansible_interfaces | map('regex_replace', '^', 'ansibl…

Facts: Get the name of an interface for a given IP

Get Help

mariit (Martin) September 21, 2023, 9:02am 14

That looks really crazy and is functioning now for me. Thank you really, really much

Rename Network Interface

Topic		Replies	Views
differnet network interface names Ansible Project	3	19	August 2, 2013
how to rewrite this the proper way? Ansible Project	1	12	June 25, 2021
ansible_facts showing interface eth0_1 Ansible Project	5	66	January 18, 2023
How to access ansible_$interface where $interface is a registered value? Ansible Project	3	22	June 26, 2014
how to get all the details Ansible Project	8	46	November 30, 2017

Facts: Get the name of an interface for a given IP

Related topics