From 236580eff6c372bc54217710e8ccb895b18df7d8 Mon Sep 17 00:00:00 2001 From: A Holt Date: Thu, 11 Jan 2018 09:02:24 -0500 Subject: [PATCH] Clarify how hostapd_enabled is RECORDED into /etc/iiab/iiab.ini --- roles/network/tasks/main.yml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/roles/network/tasks/main.yml b/roles/network/tasks/main.yml index 98dc85c29..1735dcc91 100644 --- a/roles/network/tasks/main.yml +++ b/roles/network/tasks/main.yml @@ -11,9 +11,13 @@ no_net_restart: True # used below in (1) sysd-netd-debian.yml, # (2) debian.yml, (3) rpi_debian.yml when: discovered_wireless_iface == iiab_wan_iface and not reboot_to_AP -# Idea, Not Without Risks: should WiFi-as-gateway detection logic -# be encapsulated into roles/network/tasks/hostapd.yml in future? -# Today "./runtags hostapd" doesn't exist & "./runtags AP" is at yr own risk. +# EITHER WAY: hostapd_enabled's state is RECORDED into /etc/iiab/iiab.ini +# (by computed_ntetwork.yml below) for later use by... +# /usr/libexec/iiab-startup.sh, iiab-hotspot-off & iiab-hotspot-on +# +# Separate Idea, Not Without Risks: should WiFi-as-gateway detection logic +# be encapsulated into roles/network/tasks/hostapd.yml in future? Whereas +# today "./runtags hostapd" doesn't exist & "./runtags AP" is UNSUPPORTED! #- name: RPi - reboot to AP post install - installed via wifi so the services are ready # set_fact: