
294
V6100 and V7122 User Guide
Secret Tables
A table is defined as a secret table if it contains at least a single secret data field or if it
depends on another secret table. A secret data field is a field that mustn’t be revealed to the
user. For example, in the IPSec application, IPSec tables are defined as secret tables as the
IKE table contains a pre-shared key that must be concealed. Therefore, the SPD table that
depends on the IKE table is defined as a secret table as well.
There are two major differences between tables and secret tables:
The secret field itself cannot be viewed via SNMP, Web or any other application.
ini
file behavior: Secret tables are never displayed in an uploaded
ini
file (e.g., when
performing a 'Get
ini
File from Web' operation). Instead, there is a commented title that
states that the secret table is present at the gateway and is not to be revealed.
Secret tables are always kept in the gateway’s non-volatile memory and can be over-
written by new tables that are provided in a new
ini
file. If a secret table appears in an
ini
file, it replaces the current table regardless of its content. To delete a secret table from
the gateway, provide an empty table of the same type (with no data lines) as part of a
new
ini
file; the empty table replaces the previous table in the gateway.
Using the ini File to Configure Parameter Tables
You can use the
ini
file to add / modify parameter tables. When using tables, Read-Only
parameters are not loaded, as they cause an error when trying to reload the loaded file.
Therefore, Read-Only parameters mustn’t be included in tables in the
ini
file. Consequently,
tables are loaded with all parameters having at least one of the following permissions: Write,
Create or Maintenance Write.
Parameter tables (in an uploaded
ini
file) are grouped according to the applications they
configure (e.g., NFS, IPSec). When loading an
ini
file to the gateway, the recommended
policy is to include only tables that belong to applications that are to be configured (Dynamic
tables of other applications are empty, but static tables are not).
The
ini
file includes a Format line that defines the columns of the table to be modified (this
may vary from
ini
file to
ini
file for the same table). The Format line must only include
columns that can be modified (parameters that are not specified as Read-Only).
An exception is Index-fields that are always mandatory. In the example provided in
Table 64
,
all fields except for the ‘Time Connected’ field are loaded.
Summary of Contents for V6100
Page 28: ...28 V6100 and V7122 User Guide Reader s Notes...
Page 48: ...48 V6100 and V7122 User Guide Reader s Notes...
Page 72: ...72 V6100 and V7122 User Guide Reader s Notes...
Page 80: ...80 V6100 and V7122 User Guide Reader s Notes...
Page 152: ...152 V6100 and V7122 User Guide Reader s Notes...
Page 262: ...262 V6100 and V7122 User Guide Reader s Notes...
Page 284: ...284 V6100 and V7122 User Guide Reader s Notes...
Page 291: ...V6100 and V7122 User Guide 291 Figure 95 V7122 Startup Process...
Page 324: ...324 V6100 and V7122 User Guide Reader s Notes...
Page 354: ...354 V6100 and V7122 User Guide Reader s Notes...
Page 374: ...374 V6100 and V7122 User Guide Reader s Notes...
Page 382: ...382 V6100 and V7122 User Guide Figure 130 Example of a User Information File Reader s Notes...
Page 392: ...392 V6100 and V7122 User Guide Reader s Notes...
Page 409: ...V6100 and V7122 User Guide 409 Reader s Notes...
Page 413: ...V6100 and V7122 User Guide 413 Reader s Notes...
Page 425: ...V6100 and V7122 User Guide 425 Figure 145 UDP2File Utility Reader s Notes...
Page 431: ...V6100 and V7122 User Guide 431 Reader s Notes...
Page 447: ...V6100 and V7122 User Guide 447 Reader s Notes...
Page 483: ...V6100 and V7122 User Guide 483 Reader s Notes...