User's Manual

Table Of Contents
Fortress ES-Series CLI Guide: Networking and Radio Configuration
68
radiusperiod (RadiusRetryInterval) specifies the
number of seconds (
0—2147483647) between retries of
the primary authentication server. The default is
0
(zero), which disables the function: If the primary Wi-Fi
authentication server cannot be reached on the initial
attempt, it is not retried until all configured network
servers (secondary, tertiary, etc.) have been tried in turn
and also failed.
strictrekey (
GtkStrictRekey
) - enter
y
or
n
to indicate
whether to automatically rekey whenever a STA leaves
the BSS.
reauthperiod - to ensure that a peer whose certificate
has been revoked is not allowed to remain associated,
you can establish a reauthentication period. Any peer
with a certificate that is no longer valid will be dropped.
Specify an interval in whole seconds between
0
and
2147483647,
inclusive. The default is
3600
. See Section
4.2.2.3 for additional information on Certificate
Revocation.
preauth - to facilitate roaming between network access
points, enabling preauthentication on the BSS permits
approaching WPA2 wireless clients to authenticate on
the Mesh Point while still connected to another network
access point, while wireless clients moving away from
the Mesh Point can remain connected while they
authenticate on the next network AP. By default,
preauth is set to
n
(disabled).
For WPA-PSK (pre-shared key), WPA2-PSK and WPA-
Mixed-PSK (
wpapsk
,
wpa2psk
,
wpa2mixedpsk
) you can set
the interval, in seconds, between key exchanges
(
rekeyperiod). The default is zero (
0
), which value
disables key exchange; the same key will be used for the
entire session. You must also specify whether the pre-
shared key will be an
ascii
plaintext passphrase of 8–63
characters or a 64-digit
hex
adecimal string and then enter
the key itself:
You can use the same switches with the
update command to
edit BSS settings.
You can delete a specified BSS or all configured BSSs with the
del command:
# del bss -all|-name
<name>
You must be logged on to an
administrator
-level account to
change configuration settings (refer to Section 2.2).