INSYS MoRoS Manual de usuario
Add-On Manual
MoRoS / MLR
Reference Manual ASCII Configuration File
Nov-10
Copyright © November 10 INSYS MICROELECTRONICS GmbH
Any duplication of this manual is prohibited. All rights on this documentation and the
devices are with INSYS MICROELECTRONICS GmbH Regensburg.
Trademarks
The use of a trademark not shown below is not an indication that it is freely available for
use.
MNP is a registered trademark of Microcom Inc.
IBM PC, AT, XT are registered trademarks of International Business Machine Corporation.
INSYS ® is a registered trademark of INSYS MICROELECTRONICS GmbH.
Windows™ is a registered trademark of Microsoft Corporation.
Linux is a registered trademark of Linus Torvalds.
Publisher:
INSYS MICROELECTRONICS GmbH
Waffnergasse 8
D-93047 Regensburg, Germany
Phone: +49 (0)941/56 00 61
Fax: +49 (0)941/56 34 71
E-mail: [email protected]
Internet: http://www.insys-tec.de
Date: Nov-10
Item: 31-22-03.165
Version: 1.1
Language: EN
Contents
1General Information ........................................................................................... 5
2Version History.................................................................................................... 6
3ASCII Configuration File ...................................................................................... 7
3.1 Set-Up of the Configuration File ........................................................................................7
3.1.1 Comments............................................................................................................................7
3.1.2 Formatting ...........................................................................................................................8
3.1.3 Strings ...................................................................................................................................8
3.1.4 Endless Lists.........................................................................................................................8
3.1.5 Missing or Double Sections / Objects...........................................................................9
3.1.6 Mutually Exclusive Settings ............................................................................................9
3.1.7 Restart at the End of the Configuration.................................................................... 10
3.1.8 Reloading the Old Configuration after Configuration Aborts............................. 10
3.1.9 Including Files .................................................................................................................. 11
4Log File .............................................................................................................. 12
5Configuration Using ASCII Configuration File.................................................. 13
6Reference for the ASCII Configuration File....................................................... 14
4Nov-10
MoRoS / MLR General Information
1General Information
This add-on manual serves as reference for the configuration file of the MoRoS / MLR in
ASCII format and may only be used together with the operator manual of the respective
router. Safety instructions, technical data, and functional descriptions must be taken
from the operator manual.
This add-on manual is valid for all routers of the models MoRoS and MLR of INSYS MI-
CROELECTRONICS GmbH with a firmware version of 2.4.x or higher.
This reference describes all configuration options of the different variants of the router.
The individual variants do not contain all described settings. The actual scope depends
on firmware and variant.
5
Version History MoRoS / MLR
2Version History
Version Description
1.0 Release
1.1 Update for FW 2.5.x
6
MoRoS / MLR ASCII Configuration File
3ASCII Configuration File
The router allows to export the configuration as ASCII text file. This text file can be modi-
fied accordingly and uploaded again to the router to configure it in a convenient way.
Moreover, an "empty" configuration file (ASCII template) can be downloaded from the
router, i.e. a configuration file that contains no settings, but all setting options available
on the respective device.
A detailed description of the function for downloading and uploading configuration files
can be found in the operator manual of the router.
3.1 Set-Up of the Configuration File
The ASCII configuration file is structured in several sections. The section and object sort-
ing is based on the web interface. Each section starts with the name of the section in
square brackets "[ section ]" followed by further lines with the individual objects of
this section. Within the objects, object name and object value are separated by an equals
sign "object name = object value". Each line is finished with a carriage return. The end
of a section is defined by the start of a new section or the file end.
The configuration file is case sensitive, i.e. capitalisation is considered.
The following excerpt of an ASCII configuration file shows the section "textconfig" with
the two objects "reboot" and "abort_on_error" as well as the section "webinterface"
with further objects:
[ textconfig ]
reboot = 0
abort_on_error = 0
[ webinterface ]
local_http = 1
remote_http = 1
remote_https = 1
http_port = 80
https_port = 8888
location = 'Location' #This value has to be enclosed in single quotes
3.1.1 Comments
Comments can be introduced by a hash sign " # " at the beginning or also within a line.
A semicolon " ; " can only introduce a comment at the beginning of a line (also follow-
ing leading blanks or tabs). All other characters in the line will be ignored.
7
ASCII Configuration File MoRoS / MLR
3.1.2 Formatting
Blank lines can be inserted between any lines.
Blanks and tabs can be inserted
at the beginning of a line
at the end of a line
between square brackets and section names
between object name and " = "
between " = " and object value
between object name and " ; " for endless list entries
between " ; " and object value for endless list entries
3.1.3 Strings
Strings that are used to enter passwords or user names for example must be placed be-
tween single quotes " ’ " (a comment indicates the use of single quotes in each such
entry). The strings may also contain single quotes because only the first and last single
quote is searched for. Basically, the characters 0x20 through 0x7E are permissible, i.e. 0
through 9, a through z, A through Z, and the special characters! " # $ % & ' ( ) * + , - . / ; < =
> ? @ [ ] \ ^ _ { } | ~, as well as the blank. The colon is not permissible. The following ex-
ample shows the entry of strings:
dialnumber = '*99***1#' #This value has to be enclosed in single quotes
3.1.4 Endless Lists
Some objects can form endless lists (e.g. routes). If further objects are passed with an
object (e.g. the source address, net mask, data direction, etc. in case of a firewall rule),
these are written into the same line, but separated from each other using a semicolon
"; ". The object "list" defines, whether the endless list contained in this section that is
already stored on the router is to be deleted "list = d" (d for delete) before the new ob-
jects are entered, or the new objects are appended to the list "list = a" (a for append). If
the object "list" is missing, the objects are appended to the list. Generally, there is no
more than one endless list per section. The following example shows such an endless list:
....list = d
new_entry = common_name = cname1 ; vpn_ip = 10.1.0.9
new_entry = common_name = cname2 ; vpn_ip = 10.1.0.13
8
MoRoS / MLR ASCII Configuration File
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 "dns" will be
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.
9
ASCII Configuration File MoRoS / MLR
3.1.7 Restart at the End of the Configuration
The section "textconfig" of the ASCII configuration file contains the object "reboot" to
define whether a restart of the router is to be made following the configuration (0 = no
restart; 1 = restart). A restart can be used to ensure that all services are started with the
new settings (VPN settings are only used following a new dial-out for example). A restart
will be made at the end of the configuration in the following example:
[ textconfig ]
reboot = 1
abort_on_error = 0
3.1.8 Reloading the Old Configuration after Configuration Aborts
The section "textconfig" of the ASCII configuration file contains the object
"abort_on_error" to define whether the old configuration is to be reloaded in case the
configuration aborts due to an error (0 = no reload of the old configuration; 1 = reload of
the old configuration). The configuration aborts in case of severely faulty configurations
that would result a red warning message in the web interface. This function can be used
for example to secure "critical" configurations (e.g. the dial-up connection that is cur-
rently used for remote configuration), by activating this function before the "critical" sec-
tion and deactivating it again behind it, i.e. the old configuration will only be reloaded, if
the abort happens in the "critical" section. The old configuration will be reloaded after an
abort in the following example:
[ textconfig ]
reboot = 0
abort_on_error = 1
10
Otros manuales para MoRoS
3
Este manual sirve para los siguientes modelos
1
Tabla de contenidos
Otros manuales de Enrutador de red de INSYS
Manuales populares de Enrutador de red de otras marcas
NETGEAR
NETGEAR FS526T - Switch Manual de usuario
Korenix
Korenix JetNet 5710G Series Manual de usuario
Automated Logic
Automated Logic ZN551 Manual del propietario
Cisco
Cisco ASR 1000 Series Manual del operador
EnGenius
EnGenius ESR-9710 Manual de usuario
Cisco
Cisco 805 Series Instrucciones de funcionamiento y seguridad