_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
_/                                                                _/
_/   LARA web form interface documentation                        _/
_/   based on firmware version 03.02.01                           _/
_/                                                                _/
_/   ATTENTION: this document and the interfaces it describes     _/ 
_/              are subject to change without notice!!!           _/
_/                                                                _/
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

This document describes all forms recognized by the 
LARA web interface. 

How to read this document
--------------------------
All parameters should be sent via POST request except a view
forms that need GET parameters. In this case it will be explicitely 
mentioned.

Each parameter will be descriped using a list of tags.
The tags have the following meaning:

  Parameter:       name of the formular parameter
  Summary:         short description of the parameter's meaning
  acl_object:      permission to change a parameter depends on this permission
  flags(optional): special parameter properties, see below
  validate_regex:  regular expression for parameter validation (see below)
  validate_min:    minimum required length
  validate_max:    maximum required length

The regular expression tags will expand to the following 
actual regular expressions. In case the regular expression 
matches to given parameter, the parameter is assumed to be 
valid.

  ERIC_REGEX_NONE:                  <no regex check>
  ERIC_REGEX_IP:                    "^[0-9]{1,3}(\\.[0-9]{1,3}){3}$"
  ERIC_REGEX_MAC:                   "^[0-9A-Fa-f]{2}(:[0-9A-Fa-f]{2}){5}$"
  ERIC_REGEX_ENCODING:              "^(normal|compressed|auto)$"
  ERIC_REGEX_COMPRESS_RATE:         "^[0-9]$"
  ERIC_REGEX_HEX_BYTE:              "^[0-9A-Fa-f]{1,2}$"
  ERIC_REGEX_NONCTRL_STRING:        "^[^[:cntrl:]]*$"
  ERIC_REGEX_NUMBER:                "^[0-9]*$"
  ERIC_REGEX_PHONENUMBER:           "^[+]?[0-9]*$"
  ERIC_REGEX_KBD_MODEL:             "^(101pc|104pc|mac)$"
  ERIC_REGEX_MOUSE_MODEL:           "^(iipps2|iipwheel)$"
  ERIC_REGEX_IPFW_POLICY:           "^(ACCEPT|DROP)$"
  ERIC_REGEX_CERT_COUNTRY:          "^[A-Z]{2}$"
  ERIC_REGEX_CERT_KEY_LENGTH:       "^(1024|2048)$"
  ERIC_REGEX_TIME:                  "^([01]?[0-9]|2[0-3]):[0-5][0-9]$"
  ERIC_REGEX_DYNDNS_CHECK_INTERVAL: "^(24|12|6|3|2)h$"
  ERIC_REGEX_FLOAT:                 "^-?[0-9]+(\\.[0-9]+)?$"
  ERIC_REGEX_CUSTOM_VIDEO_MODE :    "^(off|use|force)$"
  ERIC_REGEX_RC_TYPE:               "^(default|sun|activex)$"
  ERIC_REGEX_NONCTRL_NOSPACE_STRING:"^[^[:cntrl:] ]*$"
  ERIC_REGEX_IPFW_IP_MASK:
               "^[0-9]{1,3}(\\.[0-9]{1,3}){3}/([12]?[0-9]|3[012])$"
  ERIC_REGEX_HOSTNAME: 
               "^[[:alnum:]][[:alnum:]-]*(\\.[[:alnum:]][[:alnum:]-]*)*$"

The flag tag may be present for a parameter and define some 
special properties. The possible values have the following meaning:

  FV_FLAG_MULTI_VALUE:
    The parameter is actually an array parameter, that means its name 
    must be prepended by an array index. So for instance 'p_objects'
    becomes 'p_objects_0, p_objects_1, ...' and an additional 
    parameter called 'p_objects_cnt' that defines the size of the 
    array.

  FV_FLAG_DONT_TRIM:
    Usually all string input will be trimmed before further processing.
    This flag indicates that won't be done for the according parameter.

  FV_FLAG_ALLOW_EMPTY
    Indicates that the parameter may be left empty, i.e. doesn't need
    to contain a value.

Web Formular documentation
---------------------------