We cannot afford to defer things to a handler when reconfiguring the network: we need to know as soon as possible when our playbook has gone up in flames and left a remote out-of-reach, so we can know what broke when we have to go and directly service the unit. I've hard-set the timeout here to 70 to handle the full one-minute DFS CAC timeout, but please, for the love of God, don't run mesh on UNII-2A. You do not want to be waiting that full minute for the device to come back. |
||
---|---|---|
.. | ||
main.yml |