Difuse/routing
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

nodogsplash2: fix startup failure

Browse source 
Signed-off-by: Rob White <rob@blue-wave.net> 
This change will fix a problem where NoDogSplash2 Fails to start if the device it binds to is not ready.
This commit is contained in:
bluewavenet 2018-01-07 08:51:04 +00:00 committed by GitHub
parent ee4452cb37
commit 177e4b85a5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
nodogsplash2/files/nodogsplash.config
View file

@ -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