User Guide: AWC plug-in version 3.15.0 for VST-APL

# Overview

## AWC-CB (AWC-Channel Blanket)

AWC-CB (AWC-Channel Blanket) is a single-channel architecture. This means that multiple wireless APs use the same channel and form a single large virtual AP to provide network access to clients. The main difference between single-channel and multi-channel architectures is the use of the Wi-Fi channels. Multi-channel uses all available channels which are carefully managed to avoid interference, whereas single-channel uses one wireless channel to create a single "blanket" of wireless coverage, thereby eliminating interference.
◼ Multi-channel Wireless Networks
In a conventional multi-channel wireless network, multiple wireless APs are configured to use different channels to cover a wider area than a single AP can cover.
With this configuration, there are complexities in channel planning, and problems such as packet loss, caused by inter-AP roaming, and slow traffic, caused by sticky clients. Sticky clients maintain their association with the AP that they are initially connected to, even once that AP is at a distance.
◼ Blanket Wireless Network
On the other hand, in a channel blanket (or blanket) wireless network, multiple wireless APs use the same channel and form a single large virtual AP to provide network access to clients. In this configuration, communications can be more stable, without roaming causing packet loss and sticky clients, because only a single channel is used. This also removes the need for complex channel planning.
However, because all clients send and receive traffic on the same channel, only a single AP can transmit at a given moment, therefore downlink throughput will decrease.
AWC-CB uses patented "Multi-Communication Technology" to let multiple clients on a blanket network send/receive data simultaneously using separate APs, as long as they do not interfere with each other.
The following table shows the differences between multi-channel and blanket wireless networks.

Table 1: Comparison between Multi-channel and Blanket Wireless Networks
| Multi-channel (Conventional) | Blanket
--- | --- | ---
Roaming | POOR... Depending on clients | GOOD Zero Time
Easy Deployment | NOT GOOD... Complex channel planning is required | GOOD Because of using a single channel, channel planning is not required
Throughput | OKAY By limiting the number of clients per cell high throughput can be achieved. | POOR... Because of using a single channel, throughput decreases with more clients

◼ Hybrid Wireless System
With AWC-CB, it is possible to easily build a hybrid wireless network, which combines the strengths of both multi-channel and blanket networks. Multi-channel and blanket networks can be configured on a single AP, where the multi-channel networks are defined as ordinary VAPs in an AP Profile and the blanket networks are defined as VAPs in a CB Profile.
For example, by assigning static, high-throughput stations such as PCs to multi-channel VAPs and putting mobile, low-throughput devices in blanket VAPs, your network as a whole can be utilized and managed more efficiently.

> Note

> > Because a channel blanket controls multiple APs as a single large virtual AP, individual APs in the channel blanket transmit beacon signals in turn. Some clients may appear to have unstable signal strength, due to receiving beacon signals from wireless APs other than the wireless AP that they are connected to. This does not cause any problems with network traffic quality.

## Required Licenses

The following licenses are required to use AWC-CB functions with the AWC Plug-in:

- Vista Manager EX License
- Wireless LAN Controller License (10 APs)
- Wireless Channel Blanket License (10 APs)

For the Wireless Channel Blanket license, you might need more than one license, depending on how many APs you want to operate in AWC-CB (AWC-Channel Blanket) mode. A single Wireless Channel Blanket license lets you operate 10 APs in AWC-CB mode. Adding more licenses increases the number of APs which can operate in AWC-CB mode.
For example, the following licenses are needed when you run 40 APs in a multi-channel wireless network and 25 APs in a channel blanket network.

Table 2: An example of required licenses
| Multi-channel | AWC-CB | Total
--- | --- | --- | ---
Number of APs | 40 | 25 | 65
Vista Manager EX License | 1 | 1
Wireless LAN Controller License (10 APs) | 4 (Max 40) | 3 (Max 30) | 7
Wireless Channel Blanket License (10 APs) | - | 3 (Max 30) | 3

## Supported Wireless APs

The following AP models support AWC-CB.

- TQ series
  - AT-TQ7403
    Firmware Version 10.0.4-2.1 or later
  - AT-TQ6403 GEN2
    Firmware Version 9.0.4-3.1 or later
  - AT-TQ6702e GEN2
    Firmware Version 9.0.4-2.1 or later
  - TQ6602 GEN2, TQ6702 GEN2
    Firmware Version 8.0.2-0.1 or later
  - TQ6602
    Firmware Version 7.0.1-0.1 or later
  - TQ5403, TQ5403e
    Firmware Version 5.3.x or later

> Note

> > Model groups, TQ5403 and TQ5403e; TQ6403 GEN2; TQ6602; TQ6602 GEN2, TQ6702 GEN2, and TQ6702e GEN2; and TQ7403 cannot be mixed.
> > Only the following model combinations can be mixed on the same Channel Blanket.
> > - Combination of TQ5403 and TQ5403e
> > - Any combination of TQ6602 GEN2 firmware version 8.0.5-0.1, TQ6702 GEN2 firmware version 8.0.5-0.1, or TQ6702e GEN2 firmware version 9.0.5-0.1
> >   (Cannot be used in conjunction with firmware older than the above versions.)

> Note

> > The firmware version of wireless APs used in a channel blanket environment must be the same. Operation with mixed firmware versions is not supported.
> > When using TQ6702 GEN2 / TQ6602 GEN2 together with TQ6702e GEN2, apply the following firmware versions:
> > - TQ6702 GEN2 / TQ6602 GEN2: Firmware version 8.0.5-0.1
> > - TQ6702e GEN2: Firmware version 9.0.5-0.1

## Support Limits

The number of CB Profiles, channel blankets, APs per channel blanket, VAPs per channel blanket, and wireless clients that can be supported are:

- CB Profile
  100
- Channel blankets
  20
- APs per channel blanket
  100
- VAPs per channel blanket
  - AT-TQ7403
    21 VAPs (7 for each of 2.4GHz, 5GHz W52, and 6GHz)
  - AT-TQ6403 GEN2
    14 VAPs (7 for each of 2.4GHz and 5GHz W52)

    > Note

    > > TQ6403 GEN2 Radio 3 cannot be used for AWC-CB.

  - AT-TQ6702e GEN2
    14 VAPs (7 for each of 2.4GHz and 5GHz W52)
  - TQ6602 GEN2 and TQ6702 GEN2
    14 VAPs (7 for each of 2.4GHz and 5GHz W52)
  - TQ6602
    20 VAPs (10 for each of 2.4GHz and 5GHz)

    > Note

    > > If you use TQ6602 firmware version 7.0.1-0.x or earlier, you actually be able to use up to 6 VAPs in total, 3 VAPs each for 2.4GHz/5GHz.

  - TQ5403 and TQ5403e
    6 VAPs (3 for each of 2.4GHz and 5GHz)

    > Note

    > > TQ5403 and TQ5403e Radio 3 cannot be used for AWC-CB.

    > Note

    > > When running TQ5403 or TQ5403e with firmware version 6.0.1-1.x or older, the number of supported VAPs per Channel Blanket is up to 4; 2 for each 2.4GHz and 5GHz.

- Wireless clients
  - AT-TQ7403
    - Radio 1/2
      500 per radio band
    - Radio 3
      256 per radio band
  - AT-TQ6403 GEN2
    500 per radio band
  - AT-TQ6702e GEN2
    500 per radio band
  - TQ6602 GEN2 and TQ6702 GEN2
    500 per radio band
  - TQ6602
    320 per radio band

    > Note

    > > This number was measured in our test environment, however we cannot guarantee this will apply in other situations. The actual maximum number of clients depends on your network configuration, applications, and environment. The maximum number of clients do not depend on the number of VAPs (i.e. it is the same if only a single blanket VAP is used or several multi-channel and blanket VAPs are used).

  - TQ5403, TQ5403e
    500 per radio band

    > Note

    > > This number was measured in our test environment, however we cannot guarantee this will apply in other situations. The actual maximum number of clients depends on your network configuration, applications, and environment. The maximum number of clients do not depend on the number of VAPs (i.e. it is the same if only a single blanket VAP is used or several multi-channel and blanket VAPs are used). Multi-channel VAPs can support only 200 clients per radio band.

  > Note

  > > The number of wireless clients shown above indicates the maximum number that can be connected and does not guarantee communication quality.
  > > To ensure communication quality, design by taking into account the usage environment and bandwidth used.

> Note

> > To maintain the channel blanket, the load on each AP increases proportionally with the following factors.
> > If an AP determines that the load exceeds acceptable limits, it may reboot in order to maintain the channel blanket.
> > 1. Number of APs in the channel blanket
> > 2. Number of VAPs used in the channel blanket
> > 3. Number of wireless clients connected to the channel blanket
> > 4. Number of wireless clients concentrated on a single AP within the channel blanket

## Steps to Create a Hybrid Wireless System

To build a hybrid wireless system, follow the steps below.
◼ Build from scratch (with new wireless APs)

1. Physically install the APs.
2. Add the APs to the AWC Plug-in's management database.
   Add them on the AP Settings page.
3. Place the APs on floor maps.
   Create floor maps and place APs on them on the Floor Map page.
   If you select APs from a list of APs in a Management Group at step 6, you do not need to create floor maps. However, it is recommended that you create floor maps if you will have a lot of APs in a single Management Group.
4. Next, create the AP Profiles.
   Create an AP Profile on the AP Profile page. Then configure general, system, wired network, wireless network and multi-channel VAPs.
5. Create a CB Profile, which bundles together the common settings for a blanket network.
   Create a CB Profile on the CB Profile page. Then configure CB VAPs (VAPs for blanket networks) in addition to the profile name and management group.
6. Create a channel blanket to which you want to apply the CB Profile.
   Create a channel blanket on the CB Profile page and select member APs.
   Member APs can be selected visually on floor maps, or can be selected on a list of APs in a Management Group.
   Refer to Create Channel Blanket for more details.
7. Apply the AP Profile to the APs.
   The APs remain unmanaged until you apply an AP Profile to them.
   Once the AP Profile is applied to the APs on the AP Settings page, the APs' status changes to "Managed" and both multi-channel and blanket networks are made operational.

◼Re-configure existing APs

1. Create a CB Profile, which bundles together the common settings for a blanket network.
   Create a CB Profile on the CB Profile page. Then configure CB VAPs (VAPs for blanket networks) in addition to the profile name and management group.
2. Create a channel blanket to which you want to apply the CB Profile.
   Create a channel blanket on the CB Profile page and select member APs.
   Member APs can be selected visually on floor maps, or can be selected on a list of APs in a Management Group.
   Refer to Create Channel Blanket for more details.
3. Apply changes to the APs.
   Once the CB Profile is applied to the APs on the CB Profile page, the blanket network becomes operational in addition to the existing multi-channel networks.
   Refer to Apply CB Profile for more details.

## Notes

Please note the following items when you are configuring VAPs:
◼ Notes

- While AP Profiles are numbered sequentially from 1, a CB Profile can have an arbitrary unique number in the same range as the AP Profile.
  If you specify the same number for a CB Profile as the existing AP Profile, the CB VAP is used for the number (the AP Profile's VAP with the number is not used because it's overriden by the CB VAP with the same number).
- The AP Profile and CB Profile have some similar options (such as Channel and Tx Power per radio band). The settings on the CB Profile take precedence.
  For setting items that are only found in either AP Profile or CB Profile, they are applied to the wireless AP as they are.
- If an AP belonging to a channel blanket goes down, it may take several minutes to restore communication for the wireless clients that were communicating with that AP.
  Wireless clients communicating with other APs are not affected.

◼ Per Network
When using the channel blanket feature, please note the following for switches on the subnet where the wireless AP is located.

- Disable "MAC address thrashing protection" function in the channel blanket network.

◼ Per Management Group
When using the channel blanket function, please note the following in the management groups to which the relevant APs belong

- The AT-TQ5403/5403e/6602 has limitations on Neighbor Managed AP Detection when using the Channel Blanket feature.
  - AT-TQ5403/5403e
    Disable Neighbor Managed AP Detection of AWC Settings on the management group which the APs for the Channel Blanket belong to.
  - TQ6602
    Neighbor Managed AP Detection does not work on AWC-CB enabled radio band.

◼ Per AP
When using the channel blanket function, please note the following in the AP profiles and individual settings that apply to the relevant APs.

- AP Profile
  - There is no setting item for a Virtual IP Address for Captive Portal in the CB profile. The Virtual IP Address for Captive Portal set under "Basic Configuration" in the AP Profile will be applied.
  - Channel Blanket cannot be used with Band Steering.
    When configuring an AP profile, disable Band Steering in the "Radio Configuration" section.
  - Emergency Mode cannot be used with channel blanket.
    When configuring an AP profile, do not set "Condition" to "Emergency mode only" on the radio used for channel blanket.
    Also do not set "VAP Status" to "Emergency" for the VAP whose number is the same as the CB VAP (VAP for channel blanket).
  - For TQ5403/5403e/6602, Channel blanket cannot be used with Dynamic VLAN in WPA Enterprise.
  - Channel blanket cannot be used with AMF Application Proxy feature in MAC Access Control.
  - In TQ5403/5403e/6602 GEN2/6702 GEN2, Wireless Client Isolation per VAP is not supported when using channel blanket. Per-AP "Wireless Client Isolation" Setting by "Radio Configuration" in the AP Profile are valid, but "Wireless Client Isolation" in the "VAP (Multiple SSID) Settings" should be left as default in the AP Profile.
    "Wireless Client Isolation" in "VAP (multiple SSID) setting" in the CB Profile works as specified.
  - Channel Blanket cannot be used with the OpenFlow feature.
- Change Setting Per AP
  - If you change AP-specific configuration settings that are also available in the channel blanket configuration, the settings in the channel blanket configuration are used.
    However, if you change the Tx Power in the AP-specific configuration settings, the AP-specific setting is used.
  - Channel Blanket cannot be used with WDS.
- On TQ6602 GEN2 and TQ6702 GEN2, mixed usage of AWC-SC and AWC-CB is not supported.
  If an attempt is made to apply a configuration with both CB Profile and SC Profile enabled, the relevant wireless AP will leave the management of the AWC Plug-in. In this case, disable either or both of the AWC-CB or AWC-SC function and re-register the wireless AP.
- When using TQ6602 GEN2/6702 GEN2, if the configuration of the wireless AP is switched from one of cellular VAP (non-CB/SC VAP) only; AWC-CB only or AWC-CB/cellular combination; or AWC-SC/cellular combination; to a different configuration (e.g. cellular VAP only to/from AWC-CB/cellular combination), the wireless AP will restart after the configuration is applied.

◼ Per Radio
When using the channel blanket function, please note the following points in the applicable AP profiles and CB profiles for the radio bands (Radio 1/Radio 2/Radio 3) that use channel blanket.

- Channel Blanket cannot be used with Air Time Fairness.
  When configuring an AP profile, disable Air Time Fairness on the radio band used for channel blanket in the "Radio Configuration" section.
- Changing the RTS threshold is not supported with channel blanket.
  When configuring an AP profile, leave "RTS Threshold" untouched at the default value of 2347 in the "Radio Configuration" section.
- Combined use of the Channel Blanket function and Neighbor AP Detection is supported, but a configuration item for this function is not provided in the CB Profile.
  The function setting in the Wireless Configuration of the AP Profile will be applied to enable/disable the function.
- On TQ6602, channel blanket cannot be used with MU-MIMO.
- On TQ6602, channel blanket cannot be used with OFDMA.
- When applying the same CB profile to wireless APs configured with different AP profiles, the following radio settings for each AP profile must be the same settings for the radio band where the channel blanket is to be created.
  - Mode
  - Bandwidth
  - Maximum Wireless Clients
  - Fixed Tx Rate
- AWC is not supported on the radio band used for Channel Blanket.
- Because the APs in a Channel Blanket use the same channel, interference may occur on a multi-channel VAP configured on the same radio band as the blanket VAP. Make sure you test thoroughly before using CB VAPs and multi-channel VAPs on the same radio band.

◼ Per CB VAP
When using the channel blanket feature, please note the following in the CB profiles to be applied.

- WPA3 on CB VAP is not supported on TQ5403 and TQ5403e.
- On CB VAP, TKIP cannot be specified as the encryption protocol in WPA Personal / WPA Enterprise.
- Changing the Broadcast Key Refresh Interval is not supported with channel blanket. Do not change its value from the default of "0".
- RADIUS accounting is not supported on CB VAPs. Do not enable it.
- RADIUS Session-Timeout attribute is not supported on CB VAPs. This attribute is ignored by the APs in a channel blanket.
- Pre-Authentication is not supported on CB VAPs.
- Changing the Session Key Refresh Rate and Session Key Refresh Action is not supported with channel blanket.
- For TQ5403/5403e/6602, Dynamic VLAN is not supported on CB VAPs.
- Captive Portal is not supported on TQ5403 and TQ5403e with channel blanket.
- When using MAC Access Control with "External RADIUS" on CB VAP, the following firmware must be applied to the AP:
  - TQ5403 and TQ5403e firmware version 6.0.1-2.x or later
  - TQ6602 firmware version 7.0.1-0.1 or later
  - Other models
    Available with firmware versions listed under "Supported Wireless APs" above
    .
- For TQ5403/5403e/6602, Fast Roaming is not supported on CB VAPs. Do not enable it.
- Combination with Inactivity Timer is not supported on CB VAPs. Use the default setting.
- On CB VAPs for TQ5403 and TQ5403e, changing the setting of Duplicate AUTH received is only supported with firmware version 6.0.1-6.1 or later. For earlier firmware, please use the default setting.
  Duplicate AUTH received is not supported on CB VAPs for the other models. Regardless of the setting, it works the same as when set to "Ignore".
- Using the same VLAN ID for both a channel blanket's Control VLAN and an AP's management VLAN is not supported.
  It is also not supported to use the same VLAN ID for both a channel blanket's Control VLAN and a user VLAN for any VAP.

## Supported Functions on CB VAP per AP Model

CB VAPs (VAPs for a channel blanket) are configured in a CB Profile.
CB VAPs and multi-channel VAPs (ordinary VAPs) have different supported functions, as shown below.

Table 3: Supported functions on Multi-channel and Blanket VAPs
Item Name | TQ | Comment
--- | --- | ---
5403/5403e | 6602 | 6602 GEN2 6702 GEN2 6702e GEN2 | 6403 GEN2 | 7403
Multi-channel VAP | Blanket (CB) VAP | Multi-channel VAP | Blanket (CB) VAP | Multi-channel VAP | Blanket (CB) VAP | Multi-channel VAP | Blanket (CB) VAP | Multi-channel VAP | Blanket (CB) VAP
Radio | N | Y | N | Y | N | Y | N | Y | N | Y |
VAP | N | Y | N | Y | N | Y | N | Y | N | Y | This item refers to the VAP number that is overwritten by the CB VAP.
Channel | N | Y | N | Y | N | Y | N | Y | N | Y |
VAP Status | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
VLAN ID | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
SSID | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
| Broadcast SSID | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
Security | None | Y | Y | Y | Y | Y | Y | Y* | Y* | Y* | Y* | This item will not be displayed if you select Radio 3 for TQ7403.
Static WEP | Y | Y | Y | N | Y | N | N | N | N | N | This can be configured only on VAP1 of each radio. Do not use a mode that contains IEEE 802.11n in the AP Profile of APs using channel blanket.
| Key Length | 64bit | Y | Y | Y | N | Y | N | N | N | N | N
128bit | Y | Y | Y | N | Y | N | N | N | N | N
Key Type | ASCII | Y | Y | Y | N | Y | N | N | N | N | N
Hexadecimal | Y | Y | Y | N | Y | N | N | N | N | N
Key Index | Y | Y | Y | N | Y | N | N | N | N | N
Security Key (WEP Key) | Y | Y | Y | N | Y | N | N | N | N | N
WEP Authentication Method | Open System | Y | Y | Y | N | Y | N | N | N | N | N
Shared Key | Y | Y | Y | N | Y | N | N | N | N | N
Enhanced Open | N | N | N | N | N | N | Y | Y | Y | Y |
| OWE | N | N | N | N | N | N | Y | Y | Y | Y |
Management Frame Protection (MFP) | N | N | N | N | N | N | Y | Y | Y | Y |
WPA Personal | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
| Security Key (WPA-PSK) | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
WPA Versions | WPA3 | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
WPA2 | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
WPA | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
Encryption Protocol | CCMP | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
TKIP | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
Management Frame Protection (MFP) | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
Broadcast Key Refresh Rate | Y | N | Y | N | Y | N | Y | N | Y | N | TQ5403, TQ5403e and TQ6602 have the setting item, but are not supported.
WPA Enterprise | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
| RADIUS Server Primary IP Address | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Primary Secret | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Secondary IP Address | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Secondary Secret | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Port Number | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
Pre-authentication | Y | N | Y | N | Y | N | Y | N | Y | N | Pre-Authentication is not supported on CB VAPs.
WPA Versions | WPA3 | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
WPA2 | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
WPA | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
Encryption Protocol | GCMP | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
CCMP | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
TKIP | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
Management Frame Protection (MFP) | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
Broadcast Key Refresh Rate | Y | N | Y | N | Y | N | Y | N | Y | N | TQ5403, TQ5403e and TQ6602 have the setting item, but are not supported.
RADIUS Accounting | Y | N | Y | N | Y | N | Y | N | Y | N | TQ5403, TQ5403e and TQ6602 have the setting item, but are not supported.
RADIUS Accounting Port Number | Y | N | Y | N | Y | N | Y | N | Y | N | TQ5403, TQ5403e and TQ6602 have the setting item, but are not supported.
Dynamic VLAN | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
Captive Portal | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
| External RADIUS | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
| Authentication Page Proxy | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Primary IP Address | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Primary Secret | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Secondary IP Address | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Secondary Secret | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Port Number | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Accounting | Y | N | Y | N | Y | N | Y | N | Y | N |
| RADIUS Accounting Port Number | Y | N | Y | N | Y | N | Y | N | Y | N |
Redirect type (after user is authenticated) | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
Walled Garden | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
DNS Proxy for Walled Garden | N | N | N | N | Y* | Y* | N | N | N | N | TQ6702e GEN2 does not support this feature.
Virtual IP Address for Captive Portal | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y* | TQ5403/5403e will be supported with firmware version 6.0.2-0.1. For any of TQ5403, TQ5403e, TQ6403 GEN2, TQ6602, TQ6602 GEN2, TQ6702 GEN2, TQ6702e GEN2, and TQ7403 the CB Profile do not have a individual setting item. The Virtual IP Address for Captive Portal set in the AP Profile will be applied.
Session Timeout | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
Session Timeout Action | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
Click-through | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
| Authentication Page Proxy | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
Redirect type (after user is authenticated) | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
Walled Garden | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
DNS Proxy for Walled Garden | N | N | N | N | Y* | Y* | N | N | N | N | TQ6702e GEN2 does not support this feature.
Virtual IP Address for Captive Portal | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y* | TQ5403/5403e will be supported with firmware version 6.0.2-0.1. For any of TQ5403, TQ5403e, TQ6403 GEN2, TQ6602, TQ6602 GEN2, TQ6702 GEN2, TQ6702e GEN2, and TQ7403 the CB Profile do not have a individual setting item. The Virtual IP Address for Captive Portal set in the AP Profile will be applied.
Session Timeout | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
Session Timeout Action | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
External Page Redirect | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
| External Page URL | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Primary IP Address | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Primary Secret | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Secondary IP Address | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Secondary Secret | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Server Port Number | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
RADIUS Accounting | Y | N | Y | N | Y | N | Y | N | Y | N |
| RADIUS Accounting Port Number | Y | N | Y | N | Y | N | Y | N | Y | N |
Redirect type (after user is authenticated) | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
Walled Garden | Y | N | Y | Y | Y | Y | Y | Y | Y | Y |
DNS Proxy for Walled Garden | N | N | N | N | Y* | Y* | N | N | N | N | TQ6702e GEN2 does not support this feature.
Virtual IP Address for Captive Portal | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y* | TQ5403/5403e will be supported with firmware version 6.0.2-0.1. For any of TQ5403, TQ5403e, TQ6602, TQ6602 GEN2 and TQ6702 GEN2, the CB Profile do not have a individual setting item. The Virtual IP Address for Captive Portal set in the AP Profile will be applied.
Session Timeout | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
Session Timeout Action | Y | N | Y | N | Y | Y | Y | Y | Y | Y |
MAC Access Control | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
| MAC Address List | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
| Selected List | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y* | * This item is not displayed on the CB VAP configuration page. The MAC Address List that is selected for the AP Profile is applied to CB VAPs.
External RADIUS | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y* | TQ5403, TQ5403e firmware version 6.0.1-2.x or later; TQ6602 firmware version 7.0.1-0.1 or later; TQ6602 GEN2, TQ6702 GEN2 firmware version 8.0.2-1.1 or later is required.
| RADIUS Server Primary IP Address | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y*
RADIUS Server Primary Secret | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y*
RADIUS Server Secondary IP Address | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y*
RADIUS Server Secondary Secret | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y*
RADIUS Server Port Number | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y*
User-Name Format Separator | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y*
User-Name Format Letter Case | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y*
User-Password Format | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y*
User-Password Format Password | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y*
Fast Roaming | Y | N | Y | N | Y | N | Y | N | Y | N | TQ5403, TQ5403e and TQ6602 have the setting item, but are not supported.
| 802.11r FT | Y | N | Y | N | Y | N | Y | N | Y | N
FT over DS | Y | N | Y | N | Y | N | Y | N | Y | N
Mobility Domain | Y | N | Y | N | Y | N | Y | N | Y | N
R0 key Lifetime | Y | N | Y | N | Y | N | Y | N | Y | N
AES Key | Y | N | Y | N | Y | N | Y | N | Y | N
802.11k RRM | Y | N | Y | N | Y | N | Y | N | Y | N
802.11v WNM | Y | N | Y | N | Y | N | Y | N | Y | N
Wireless Client Isolation | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | * For multi-channel VAPs, this is configured in the "Radio Configuration" section of an AP profile. For CB VAPs, the setting for the CB VAP is preferred. The setting in the AP profile is ignored.
Inactivity Timer | Y | N | Y | N | Y | N | Y | N | Y | N |
Duplicate AUTH received | Y | Y* | N | N | Y | Y* | Y | Y* | Y | Y* | TQ5403/5403e firmware version 6.0.1-6.1 or later is required to change the settings for this item in the CB VAP. On CB profile for TQ6602 GEN2/TQ6702 GEN2, this item is fixed to "Ignore".
Association Advertisement | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
DTIM Period | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | * For multi-channel VAPs, this is configured in the "Radio Configuration" section of an AP profile.
RSSI Threshold | N | Y | N | Y | N | Y | N | Y | N | Y |
Tx Power | Y* | Y | Y* | Y | Y* | Y | Y* | Y | Y* | Y | * For multi-channel VAPs, this is configured on the AP-specific configuration page. If the Tx Power is changed in the per-AP setting when using channel blanket, the per-AP setting takes precedence to CB Profile setting.
Proxy ARP | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y |
Force Power Save Disabled | N | Y | N | Y | N | Y | N | Y | N | Y |

10 Nov 2025 11:47