blocks|key|423355|text|{{+ansible_env['SSH_CLIENT'].split()+%7C+first+}}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|423356|工作，但您必须从默认用户收集有关连接变量的事实，所以八：|unstyled|423357|423358|Set«gather_facts:+yes»and+not«task+:+yes»on+playbook+level|unordered-list-item|423359|More+reliable:+run«setup»task(不使用«task:+yes»以及在此«ansible_env»usage之前-+better+on«pre_tasks»部分)。|423360|423361|如果你使用«变成»运行«gather/setup»，你将会得到«一个或多个未定义的变量：'dict+object‘没有属性'SSH_CLIENT'»(这是因为sudoed«setup»只能捕获一小部分变量)。|423362|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$]]|$1|K|3|L|5|J|7|V|8|@]|9|@]|A|$]]|$1|M|3|-4|5|F|7|W|8|@]|9|@]|A|$]]|$1|N|3|O|5|F|7|X|8|@]|9|@]|A|$]]|$1|P|3|-4|5|F|7|Y|8|@]|9|@]|A|$]]]|Q|$]]

<pre><code>{{ ansible_env['SSH_CLIENT'].split() | first }}
</code></pre>

works, but you have to gather facts about connection variables from default user, so eighter:

<ul>
<li>Set «gather_facts: yes» and not «become: yes» on playbook level</li>
<li>More reliable: run «setup» task (without «become: yes» and before this «ansible_env» usage — better on «pre_tasks» section).</li>
</ul>

If you run «gather/setup» with «become», you will later get «One or more undefined variables: 'dict object' has no attribute 'SSH_CLIENT'» (this is becase sudoed «setup» can catch only small set of variables).

blocks|key|5543613|text|最简单的方法是在本地添加连接|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5543614|---
+-+name:+get+my+public+IP
+++ipify_facts:+api_url=http://api.ipify.org
+++connection:+local

+-+firewalld:+rich_rule='rule+family=ipv4+source+address={{+ipify_public_ip+}}+accept'+permanent=no+state=enabled+timeout=300
+++become:+true|code-block|syntax|javascript|5543615|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The easiset way is to add connection local

<pre><code>---
 - name: get my public IP
 ipify_facts: api_url=http://api.ipify.org
 connection: local

 - firewalld: rich_rule='rule family=ipv4 source address={{ ipify_public_ip }} accept' permanent=no state=enabled timeout=300
 become: true
</code></pre>

blocks|key|420408|text|我刚刚破解了这个解决方案，它起作用了。这是你要找的东西吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|420409|-+debug+var="{{hostvars[inventory_hostname]['ansible_env']['SSH_CLIENT'].split('+')[0]}}"|code-block|syntax|javascript|420410|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I just hacked this solution and it worked. Is this something you are looking for?

<pre><code>- debug var="{{hostvars[inventory_hostname]['ansible_env']['SSH_CLIENT'].split(' ')[0]}}"
</code></pre>

blocks|key|5543714|text|在不同的答案中描述的"ipify_facts“方法在以下情况下应该有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5543715|5543716|您的控制主机只有一个接口，或者如果它有多个接口，并且用于访问ipify+api_url的接口与访问远程主机的接口相同，则-|ordered-list-item|5543717|您的控制主机有一个公共IP+(根本不使用NAT+)，或者您的控制主机在NAT内但远程主机在外部。|5543718|5543719|5543720|如果不满足上述任一条件(即，如果您的控制主机具有多个接口，并且/或者您的控制主机和您的远程主机都位于NAT之后并使用专用地址)，则另一种(尽管稍微复杂一些)方法是在Ansible中复制以下内容：|5543721|$+ip+route+get+203.0.113.4
203.0.113.4+via+172.26.232.1+dev+enp0s3++src+172.26.232.125
++++++++++++++++++cache
$|code-block|syntax|javascript|5543722|这将显示用于到达特定目的地(203.0.113.4)的接口和源地址(172.26.232.125)。|5543723|在Ansible中实现这一点的一种方法是：|5543724|---
-+name:+Obtain+local+IP+address
++local_action:+shell+ip+route+get+{{+inventory_hostname+}}+%7C+awk+'{+for+(x=1;x<=NF;x%2B%2B)+if+($x=="src")+print+$(x%2B1)+}'
++register:+local_address
++changed_when:+false

-+name:+Print+my+local+address
++debug:+msg="Source+address+towards+{{+inventory_hostname+}}+is+{{+local_address.stdout+}}"|5543725|输出：|5543726|$+ansible-playbook+test.yml++-i+inventory.txt

PLAY+[test]+********************************************************************

TASK+[Obtain+local+IP+address]+*************************************************
ok:+[203.0.113.4+->+localhost]

TASK+[Print+my+local+address]+**************************************************
ok:+[203.0.113.4]+=>+{
++++"msg":+"Source+address+towards+203.0.113.4+is+172.26.232.125"
}|5543727|如果您有多个可通过不同接口访问的远程主机，这也应该有效。|5543728|如果您的inventory_hostname是DNS主机名而不是数字IP地址，则需要在“外壳”操作中执行额外的步骤。|5543729|entityMap^0|0|0|1|1|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|18|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|19|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1C|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1D|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1E|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1F|8|@]|9|@]|A|$]]|$1|U|3|V|5|N|7|1G|8|@]|9|@]|A|$O|P]]|$1|W|3|X|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|N|7|1I|8|@]|9|@]|A|$O|P]]|$1|10|3|11|5|6|7|1J|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1K|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|15|$]]

The "ipify_facts" method described in a different answer should work if:

<ol>
<li>Your control host has only one interface, or if it has multiple interfaces and the interface used for reaching towards the ipify api_url is the same as for reaching towards your remote host, -and-</li>
<li>Your control host has a public IP (no NAT used at all), or your control host is inside NAT but the remote host is outside.</li>
</ol>

If either of the above conditions is not met (that is, if your control host has multiple interfaces and/or your control host as well as your remote host are both behind NAT and using private addresses), then a different (albeit slightly more complex) way is to replicate the following in Ansible:

<pre><code>$ ip route get 203.0.113.4
203.0.113.4 via 172.26.232.1 dev enp0s3 src 172.26.232.125
 cache
$
</code></pre>

This will show you the interface and the source address (172.26.232.125) to be used for reaching towards a specific destination (203.0.113.4).

One way to implement this in Ansible would be:

<pre><code>---
- name: Obtain local IP address
 local_action: shell ip route get {{ inventory_hostname }} | awk '{ for (x=1;x&lt;=NF;x++) if ($x=="src") print $(x+1) }'
 register: local_address
 changed_when: false

- name: Print my local address
 debug: msg="Source address towards {{ inventory_hostname }} is {{ local_address.stdout }}"
</code></pre>

Output:

<pre><code>$ ansible-playbook test.yml -i inventory.txt

PLAY [test] ********************************************************************

TASK [Obtain local IP address] *************************************************
ok: [203.0.113.4 -&gt; localhost]

TASK [Print my local address] **************************************************
ok: [203.0.113.4] =&gt; {
 "msg": "Source address towards 203.0.113.4 is 172.26.232.125"
}
</code></pre>

This should also work if you have multiple remote hosts reachable via different interfaces.

An additional step in the "shell" action would be needed if your inventory_hostname was a DNS hostname as opposed to a numerical IP address.

blocks|key|5543583|text|{{+ansible_env['SSH_CLIENT'].split()[0]+}}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|5543584|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>{{ ansible_env['SSH_CLIENT'].split()[0] }}
</code></pre>

blocks|key|5543586|text|{{+ansible_env['SSH_CLIENT'].split()+%7C+first+}}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|5543587|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>{{ ansible_env['SSH_CLIENT'].split() | first }}
</code></pre>

I am using Ansible and <code>ufw</code> to setup a firewall on my servers. As part of the <code>ufw</code> rules I would like to allow SSH from the Ansible control machine, but not from anywhere else. My question is - what is the best way to get the IP address of the control machine itself so I can put it into the rule?

I'm aware that I can use <a href="http://docs.ansible.com/ansible/playbooks_variables.html#accessing-complex-variable-data" rel="noreferrer">facts</a> to get the IP address of the machine I am running the playbook on, but I don't see any easy way to get it automatically for the machine that is running ansible.

I'd like to avoid adding a new variable to represent this if possible since it would be nice if it was automatically discoverable, though if that's the only known best way to do it then I will just do that.

EDIT: I found <a href="https://stackoverflow.com/questions/33956453/use-ansible-control-masters-ip-address-in-jinja-template">this duplicate question</a> which is the same as mine, however it also is unanswered so will leave this open for a bit.

Best way to get the IP address of the Ansible control machine

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在使用Ansible和ufw在我的服务器上设置防火墙。作为ufw规则的一部分，我希望允许来自Ansible控制机的SSH，但不允许来自其他任何地方。我的问题是-获得控制机器本身的IP地址的最佳方法是什么，以便我可以将其放入规则中？我知道我可以使用获取运行攻略的机器的IP地址，但我没有看到任何简单的方法来自动获取运行ansible的机器的IP地址。如果可能的话，我希望避免添加新的变量来表示它，因

问获取Ansible控制机IP地址的最佳方法
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问获取Ansible控制机IP地址的最佳方法EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问获取Ansible控制机IP地址的最佳方法
EN