CISCO-LWAPP-WLAN-SECURITY-MIB

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies to enable or disable layer-2 security using WPA1 or WPA2. When this object is set to 'true' layer-2 security is enabled. When this object is set to 'false' layer-2 security is disabled. When layer-2 security is enabled, the following objects are only applied to environment and can be set. cLWSecDot11EssCckmWpa1Security cLWSecDot11EssCckmWpa1EncType cLWSecDot11EssCckmWpa2Security cLWSecDot11EssCckmWpa2EncType cLWSecDot11EssCckmKeyMgmtMode cLWSecDot11EssCckmGtkRandomize cLWSecDot11EssWpa3Security.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether cckmwpa1 security is enabled or not. A value of 'true' indicates that WPA1 security is enabled on the controller. A value of 'false' indicates that WPA1 security is disabled on the controller.

CLSecEncryptTypeThis textual convention defines the type of encryption to be applied to a WLAN. The semantics are as follows: tkip - This value indicates that TKIP encryption is configured for data protection. aes - This value indicates that AES encryption is configured for data protection. · BITS

This object specifies the type of WPA1 encryption configured on this WLAN. The value populated by this object is applicable only when cLWSecDot11EssCckmWpa1Security populates a value of 'true'.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether cckmwpa2 security is enabled or not. A value of 'true' indicates that WPA2 security is enabled on the controller. A value of 'false' indicates that WPA2 security is disabled on the controller.

CLSecEncryptTypeThis textual convention defines the type of encryption to be applied to a WLAN. The semantics are as follows: tkip - This value indicates that TKIP encryption is configured for data protection. aes - This value indicates that AES encryption is configured for data protection. · BITS

This object specifies the type of WPA2 encryption configured on this WLAN. The value populated by this object is applicable only when cLWSecDot11EssCckmWpa2Security populates a value of 'true'.

BITS

This object specifies the type of authentication key management that is applicable only when cLWSecDot11EssCckmWpaSupport is set to a value of 'true'. The following are the possible key management configurations allowed and accepted by the system. dot1x + CCKM dot1x only CCKM only PSK only FT fast transition dot1x only FT PSK only FT PSK + PSK FT SAE + SAE FT SAE-EXT-KEY + SAE-EXT-KEY FT dot1x + dot1x FT dot1x + dot1x + CCKM dot1x + CCKM +11w dot1x + 11w CCKM + 11w PSK + 11wPsk

CLSecKeyFormat1 = default2 = hex3 = asciiThis textual convention defines the type of the key configured for encryption. · Integer32

This object specifies the type of the authentication preshared key configured through the object cLWSecDot11EssCckmPsk. Note that the key configuration is applicable only when psk is configured as the key management mechanism through the cLWSecDot11EssCckmKeyMgmtMode object.

OCTET STRING SIZE (8..64)

This object specifies the authentication pre-shared key in the hex format that is applicable only when the 'psk' bit is specified in the cLWSecDot11EssCckmKeyMgmtMode object. The length of the key that can be specified for the cLWSecDot11EssPsk object depends on the value of the cLWSecDot11EssPskFmt object as follows. 'ascii' 8-63 octets 'hex' 32 octets.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object represents the Group Temporal Key(GTK) used for multicast and broadcast packet encryption in wpa1 and wpa2 clients. This object indicates the Group Temporal Key (GTK) configured on this WLAN that is applicable only when cLWSecDot11EssCckmWpaSupport is set to a value of 'true'. A value of 'true' indicates that Group Temporal Key (GTK) Randomization is enabled for a WLAN. A value of 'false' indicates that Group Temporal Key (GTK) Randomization is disabled for a WLAN.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether fast transition is enabled for particular WLAN. A value of 'true' means that fast transition is enabled and A value of 'false' means that fast transition is disabled.

Unsigned32

This object specifies the fast transition re-association time.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether fast transition over distributed system is enabled. A 'true' value means that fast transition over the distributed system is enabled. A 'false' value means fast transition over the distributed system is disabled.

INTEGER0 = disabled1 = optional2 = required · Integer32

This object specifies the 802.11w PFM status for a particular WLAN.

Unsigned32 · milliseconds

This object specifies the 802.11w Security Association(SA) query retry timeout.

Unsigned32

This object specifies the 802.11w association comeback time.

INTEGER0 = disabled1 = enabled2 = adaptive · Integer32

This object indicates the 11r status for a wlan cLWSecDot11EssFtMode is set to a value of 'adaptive'.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether wpa3 security is enabled or not. A value of 'true' indicates that WPA3 security is enabled on the controller. A value of 'false' indicates that WPA3 security is disabled on the controller.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether Multi-PSK security feature is enabled or not. True: indicates Multi-PSK security feature is enabled. False: indicates Multi-PSK security feature is disabled.

Unsigned32 (0..3000)

This object specifies the threshold for number of SAE open sessions beyond which Anti Clogging shall be enforced for future associations.

Unsigned32 (1..10000) · milliseconds

This object specifies the SAE Retransmission Timeout value.

Integer32 (1..10)

This object specifies the SAE maximum number of retry count

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether Hotspot 2.0 OSEN security feature is enabled or not. True: indicates OSEN security feature is enabled. False: indicates OSEN security feature is disabled.

Unsigned32

This object shall be used to configure OWE Transition mode support on the corresponding WLANs. Range: 0-4096. It enables OWE Transition mode on the corresponding WLANs. If it is 0, the transition mode is not enabled.

BITS

This object specifies the type of WPA3 encryption configured on this WLAN. The value populated by this object is applicable only when cLWSecDot11EssWpa3Security populates a value of 'true'.

INTEGER0 = clear1 = aes · Integer32

This object indicates the type of storage used to store PSK. clear: indicate PSK is stored as clear text'. aes : indicate the PSK is stored encrypted using AES.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether Easy PSK security feature is enabled or not. True: indicates Easy PSK security feature is enabled. False: indicates Easy PSK security feature is disabled.

INTEGER0 = hnp1 = h2e2 = h2e-hnp · Integer32

This object specifies SAE Password Element Mode 0: Hunting And Pecking Only, disables Hash To Element 1: Hash To Element Only, disables Hunting and Pecking 2: Both Hash to element, Hunting and pecking support.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether Transition Disable feature is enabled or not. True: indicates Transition Disable feature is enabled. False: indicates Transition Disable feature is disabled.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether Beacon Protection feature is enabled or not. True: indicates Beacon Protection feature is enabled. False: indicates Beacon Protection feature is disabled.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable to disable layer-2 CKIP as security policy for this WLAN. When this object is set to 'true', layer-2 CKIP security is enabled. When this object is set to 'false', layer-2 CKIP security is disabled.

Unsigned32 (0..4)

This object specifies the key index corresponding to the key being configured. A value of 0 indicates that the CKIP key hasn't been configured.

INTEGER1 = none2 = len403 = len104 · Integer32

This object specifies the length of CKIP key in bits that is applicable only when cLWSecDot11EssCkipSecurity is set as 'true'.

CLSecKeyFormat1 = default2 = hex3 = asciiThis textual convention defines the type of the key configured for encryption. · Integer32

This object specifies the type of the key configured through the object cLWSecDot11EssCkipKey.

OCTET STRING SIZE (5..26)

This object specifies the CKIP key that is applicable only when cLWSecDot11EssCkipSecurity is set as 'true'. The number of characters to be configured depends on the key length and the key type configured through the objects cLWSecDot11EssCkipKeyLength and cLWSecDot11EssCkipKeyFmt respectively. The combinations are as follows. Key Type Number of characters hex 10/26 hex characters for 40/104 bits ascii 5/13 ascii characters for 40/104 bits. When cLWSecDot11EssCkipKeyFmt is set to 'hex', cLWSecDot11EssCkipKey can only be set to hexadecimal characters. To ensure consistency the following objects must be set together. cLWSecDot11EssCkipKeyFmt cLWSecDot11EssCkipKeyIndex cLWSecDot11EssCkipKeyLength cLWSecDot11EssCkipKey.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable or disable MMH MIC mode for the CKIP for this WLAN. 'true' - MMH MIC mode is enabled 'false' - MMH MIC mode is disabled.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether CKIP is enabled. A value of 'true' indicates that the encryption keys will be generated by permuting the static CKIP key configured through cLWSecDot11EssCkipKey. A value of 'false' indicates that CKIP is disabled.

Unsigned32 (1..256)

This object specifies the priority for Multi-PSK value

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

The status of this conceptual row: To create a row in cLWSecMPskKeysTable table, set this object to either createAndGo(4) or createAndWait(5) and set cLWSecMPskPriority, cLWSecMPskKey and cLWSecMPskKeyFormat objects in the row to appropriate values.

CLSecKeyFormat1 = default2 = hex3 = asciiThis textual convention defines the type of the key configured for encryption. · Integer32

This object specifies the type of the authentication pre-shared key configured through the object cLWSecMPskKey. This configuration is applicable only when cLWSecDot11EssMPskEnable is enabled.

OCTET STRING SIZE (8..64)

This object specifies the authentication pre-shared key that is applicable only when cLWSecDot11EssMPskEnable is enabled. The length of this attribute depends on the value of the cLWSecMPskKeyFormat: 'ascii': 8-63 octets 'hex' : 32 octets.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable or disable conditional redirect. When this attribute is 'true', it signifies that conditional redirect is enabled and redirection of the client is done based on the url-redirect attribute provided by radius server. When this attribute is 'false', it signifies that conditional redirect is disabled and redirection of the client is not done, even if the url-redirect attribute is provided by the radius server. This attribute can be enabled only when 802.1x has been configured as layer-2 security the wlan and web policy is enabled on the wlan.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable or disable splash page web redirect. When this attribute is 'true', it signifies that splash page redirect is enabled and redirection of the client is done based on the url-redirect attribute provided by radius server. The redirect function works only for HTTP traffic. HTTPS redirect is not supported for any of the Web Policies. When this attribute is 'false', it signifies that splash page redirect is disabled and redirection of the client is not done. This attribute can be enabled only when 802.1x or WPA1+WPA2 has been configured as layer-2 security on the wlan.