Missing Or Double Sections / Objects; Mutually Exclusive Settings - INSYS MoRoS Additional Manual

MoRoS / MLR

3.1.5 Missing or Double Sections / Objects

If sections or objects are missing in an ASCII configuration file, the missing sections or
objects will not be uploaded to the router, i.e. the configuration of these objects remains
untouched. A single section is already a valid configuration file. Moreover, it must not
even contain an object, which can be used to restart a dial-out for example. Processing a
section in a configuration file corresponds with pressing the "OK" button on the respec-
tive page of the web interface.
If an ASCII configuration file contains an object more than once, the successive object
overwrites the previous one, because the configuration file is processed sequential. In
the following example, the second object overwrites the first, i.e. the object "
set to "2.2.2.2":
[ dns ]
dns = 1.1.1.1
dns = 2.2.2.2
Sections can also occur repeatedly and are also configured repeatedly. This can be used
for example to close a dial-up connection, configure the communication device, and set-
up the dial-up connection again within one configuration, as shown in the following ex-
ample:
[ dialout ]
start_dialout = 0
[ isdn ]
msn = 25
[ dialout ]
start_dialout = 1

3.1.6 Mutually Exclusive Settings

If settings are made in an ASCII configuration file that are mutually exclusive, for exam-
ple simultaneously activating an OpenVPN client and server, the section configured first
is valid (i.e. the one that is earlier in the configuration file). However, the associated set-
tings are taken over. A comparable behaviour is also on the web interface: a conflicting
setting cannot be made after configuring a certain setting, because it will be faded out.
ASCII Configuration File
" will be
dns
9