Skip to content

Conversation

@holta
Copy link
Member

@holta holta commented Oct 9, 2018

Building on @jvonau's PR #1202. Please see his original 2 commits and their descriptions:

bb6b3c2

Explicitly disable dnsmasq when in Appliance mode
otherwise dnsmasq will become active upon reboot because enable_services.yml
would still be acting upon local_vars.yml where dnsmasq_enabled is set to True
while there is not LAN interface available to bind the service to.

9d616cf

explicitly identify which primary dhcp server is being disabled
dhcp_service2 is used in restart.yml when not in Appliance mode

(Needs further testing...)

jvonau and others added 6 commits October 9, 2018 11:50
otherwise dnsmasq will become active upon reboot because enable_services.yml
would still be acting upon local_vars.yml where dnsmasq_enabled is set to True
while there is not LAN interface available to bind the service to.
dhcp_service2 is used in restart.yml when not in Appliance mode
sync from jvonau/iiab:dhcp2
@holta holta added this to the 6.7 milestone Oct 9, 2018
@holta
Copy link
Member Author

holta commented Oct 9, 2018

Basic smoke testing comlpeted using ./iiab-network on Ubuntu 18.04, Debian 9.5 & Raspian Lite.

@jvonau
Copy link
Contributor

jvonau commented Oct 10, 2018

squid and friends' state are already recorded in enable_services.yml under the respective services.

@tim-moody
Copy link
Contributor

Don't see the need for dhcp_service and dhcp_service2 and prefer not to overload variables. dhcp_service2 is sometimes the name of the service and sometimes a boolean. If it is a working variable lets keep it out of the whole default/local vars system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants