From 95f726e913a416b0b922d8c9e5c0278aa94cb318 Mon Sep 17 00:00:00 2001 From: A Holt Date: Mon, 1 Jan 2018 11:45:19 -0500 Subject: [PATCH] Context Explained: WiFi-as-gateway detection logic --- roles/network/tasks/main.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/roles/network/tasks/main.yml b/roles/network/tasks/main.yml index 2f59960c3..98dc85c29 100644 --- a/roles/network/tasks/main.yml +++ b/roles/network/tasks/main.yml @@ -3,7 +3,7 @@ tags: - network #REMOVE SUCH LINES (BELOW TOO) AS WE'RE IN "network" ? - network-discover - + - name: IF WIFI IS PRIMARY GATEWAY, PLEASE RUN 'iiab-hotspot-on' MANUALLY set_fact: hostapd_enabled: False # used in (1) hostapd.yml, (2) rpi_debian.yml + @@ -11,6 +11,9 @@ 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. #- name: RPi - reboot to AP post install - installed via wifi so the services are ready # set_fact: