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
