# How do you handle commands that affect network connectivity?

**URL:** <https://forum.ansible.com/t/how-do-you-handle-commands-that-affect-network-connectivity/14027>\
**Category:** Ansible Project\
**Created:** [November 28, 2013, 7:11pm UTC](https://forum.ansible.com/t/how-do-you-handle-commands-that-affect-network-connectivity/14027 "2013-11-28T19:11:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![eric2](https://avatars.discourse-cdn.com/v4/letter/e/8c91f0/32.png) [@eric2](https://forum.ansible.com/u/eric2)\
**Post date:** [November 28, 2013, 7:11pm UTC](https://forum.ansible.com/t/how-do-you-handle-commands-that-affect-network-connectivity/14027/1 "2013-11-28T19:11:39Z")

</div>

Hi folks,

my playbooks have tasks that may affect the network connectivity, for example by reloading firewall rules, and when those tasks are executed the playbook “hangs” waiting forever (or until a timeout, which is error anyway).

How do you guys handle tasks like this? Is there some way to instruct ansible that it shouldn’t wait for the return on a particular tasks (kind of like a fire-and-forget)?

Regards,

Eric

---

<div class="post-metadata">

**Author:** ![Michel\_Blanc1](https://avatars.discourse-cdn.com/v4/letter/m/fbc32d/32.png) [@Michel\_Blanc1](https://forum.ansible.com/u/Michel_Blanc1)\
**Post date:** [November 28, 2013, 7:13pm UTC](https://forum.ansible.com/t/how-do-you-handle-commands-that-affect-network-connectivity/14027/2 "2013-11-28T19:13:48Z")

</div>

Yes. Use :  
poll: 0

Sée [http://www.ansibleworks.com/docs/playbooks\_async.html](http://www.ansibleworks.com/docs/playbooks_async.html)

Chers,

M

---

<div class="post-metadata">

**Author:** ![eric2](https://avatars.discourse-cdn.com/v4/letter/e/8c91f0/32.png) [@eric2](https://forum.ansible.com/u/eric2)\
**Post date:** [November 28, 2013, 7:25pm UTC](https://forum.ansible.com/t/how-do-you-handle-commands-that-affect-network-connectivity/14027/3 "2013-11-28T19:25:40Z")

</div>

Thanks!