nodogsplash2: Fix Startup Failure (#343)
nodogsplash2: fix startup failure The underlying network_get_device() used for option network is not reliable. Use option gatewayinterface for now. Signed-off-by: Rob White <rob@blue-wave.net>
This commit is contained in:
parent
03a4dbf437
commit
c3487c6e74
1 changed files with 13 additions and 2 deletions
|
@ -12,8 +12,19 @@ config nodogsplash
|
|||
# Use plain configuration file
|
||||
#option config '/etc/nodogsplash/nodogsplash.conf'
|
||||
|
||||
# The network the users are connected to
|
||||
option network 'lan'
|
||||
# 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'
|
||||
|
||||
# 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
|
||||
option gatewayinterface 'br-lan'
|
||||
|
||||
option gatewayname 'OpenWrt Nodogsplash'
|
||||
option maxclients '250'
|
||||
#Client timeouts in minutes
|
||||
|
|
Loading…
Reference in a new issue