From 177e4b85a565d7674cab06671f4619d2e06f65d2 Mon Sep 17 00:00:00 2001 From: bluewavenet Date: Sun, 7 Jan 2018 08:51:04 +0000 Subject: [PATCH] nodogsplash2: fix startup failure Signed-off-by: Rob White This change will fix a problem where NoDogSplash2 Fails to start if the device it binds to is not ready. --- nodogsplash2/files/nodogsplash.config | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nodogsplash2/files/nodogsplash.config b/nodogsplash2/files/nodogsplash.config index 889aac9..b6ca368 100644 --- a/nodogsplash2/files/nodogsplash.config +++ b/nodogsplash2/files/nodogsplash.config @@ -12,14 +12,14 @@ config nodogsplash # Use plain configuration file #option config '/etc/nodogsplash/nodogsplash.conf' - # Set the network interface the users are connected to + # Use this option to set the network interface the users are connected to # Must not be used with option gatewayinterface # This option automatically identifies the active lan device for nodogsplash to bind to # This option may fail if the device configured for this interface is not up when nodogsplash starts at boot time # You may change this to any valid virtual lan interface that has been defined, eg lan, lan2, public_lan wlan2 etc # option network 'lan' - # Set the device nogogsplash will bind to + # Use this option to set the device nogogsplash will bind to # Must not be used with option network # The nodogsplash init script will wait for this device to be up before loading the nodogsplash service # You may change this to any valid lan device eg br-lan, wlan0, eth0.1 etc