
Fortress Bridge: Command-Line Interface
93
6.4.5.4 Access ID in the CLI
The Access ID is a 16-digit hexadecimal ID that provides
network authentication for the Fortress Security System.
All of the Bridge’s Secure Clients must be configured to use the
same Access ID as the Bridge. For information on setting
encryption algorithms on Secure Clients, refer to your Fortress
Secure Client user guide.
CAUTION: For se-
curity reasons, the
Access ID in effect on
the Bridge cannot be
displayed. Make a note of
the new Access ID: you
will need it to configure
the Bridge’s Secure Cli-
ents, as well as to
change the Access ID on
the Bridge.
Use set accessid to change the Access ID, as follows:
[GW]>
set accessid {
<16digithexid>
|default}
The default Access ID is represented by16 zeros.
The show accessid and set accessid commands are valid
only in GW (gateway) mode (refer to Section 6.1.1 for more
detail).
6.4.5.5 Operating Mode in the CLI
The Fortress Bridge can be operated in either of two modes:
Normal (the default) or FIPS.
You can view the current operating mode on the Bridge with
show fips:
[GW]>
show fips
On
Change operating modes with the set fips command. To set
the operating mode to FIPS:
[GW]>
set fips on
Return the Fortress Bridge to Normal operating mode (the
default) with:
[GW]>
set fips off
The show fips and set fips commands are valid only in GW
(gateway) mode (refer to Section 6.1.1 for more detail).
6.4.5.6 WAN Port Encryption in the CLI
By default, the Bridge’s WAN port is in the encrypted zone of
the Bridge-secured network. It can be configured to be in the
network’s unencrypted zone.
You can view the current WAN port setting with show wanport:
[GW]>
show wanport
Encrypted
Reconfigure the WAN port’s encrypted/unencrypted zone
status with the set wanport command. To place the W AN port
in the unencrypted network zone:
[GW]>
set wanport –encrypt n
Return the WAN port to the encrypted zone with:
[GW]>
set wanport –encrypt y
The show wanport and set wanport commands are valid only
in GW (gateway) mode (refer to Section 6.1.1 for more detail).