The wifiwave2 package beta offers an alternative configuration menu for wireless interfaces, as well as new features. Installing it disables other means of configuring wireless interfaces, including CAPsMAN.
Note: Before trying the wifiwave2 package, make sure to back up any wireless and CAPsMAN configuration you may want to restore afterwards.
The wifiwave2 package is compatible with IPQ4019 and AR9884 wireless interfaces and is only available for ARM builds of RouterOS v7. It also requires 10MB of free space and at least 256MB of RAM.
As of the release of RouterOS 7.1beta3, this means it is compatible with 3 devices:
*Please note that the wifiwave2 package is not compatible with CAPsMAN.
**Note that the 2.4GHz wireless interface on the RB4011iGS+5HacQ2HnD is not compatible with the wifiwave2 package. It will not be usable with the package installed.
Wifiwave2 interfaces can be configured through the CLI in the '/interface/wifiwave2' menu. Configuration through GUIs of WinBox or WebFig is not currently supported.
Following is a non-exhaustive list of wifiwave2 interface properties.
band ( 2ghz-g | 2ghz-n | 2ghz-ax | 5ghz-a | 5ghz-ac | 5ghz-an | 5ghz-ax )
|Supported frequency band and wireless standard. Defaults to newest supported standard. Note that band support is limited by radio capabilities.|
channel-width ( 20mhz | 20/40mhz | 20/40mhz-Ce | 20/40mhz-eC | 20/40/80mhz | 20/40/80+80mhz 20/40/80/160mhz )
|Width of radio channel. Defaults to widest supported .|
|configuration.chains (list of integer [0..7])||Radio chains to use for receiving signals. Defaults to all available chains.|
|configuration.tx-chains (list of integer [0..7])||Radio chains to use for transmitting signals. Defaults to all available chains.|
|configuration.country (name of a country)||Determines, which regulatory domain restrictions are applied to an interface. Defaults to "United States", prohibiting use of frequencies 2467-2472 in the 2.4GHz band.|
|configuration.hide-ssid (yes | no)|
|disabled ( no | yes )||Whether interface is disabled or not. Interfaces are disabled by default.|
|frequency ( list of integer )|
Frequencies to use for control channel when operating as AP or frequencies to scan for APs on when operating as a station (client).Defaults to all supported channels in the given frequency band.
Note: unlike the standard wireless package wifiwave2 does not support operating on non-standard radio channels (channels without an official number e.g. 5200/ac/Ceee).
|master ( name of an interface )||Master interface for virtual interfaces.|
|mode ( ap | station )||Operating mode for the interface. Defaults to 'ap'. |
|secondary-frequency ( list of integer | disabled )||Frequencies to use for the second part of a split 80+80MHz channel.|
|security.authentication-types ( list of owe, wpa-eap, wpa-psk, wpa2-eap, wpa2-psk, wpa3-eap, wpa3-psk )||Authentication types to enable on the interface. Defaults to an empty list (open AP) if security.passphrase is unset or 'wpa2-psk', if it is.|
|security.passphrase ( string 0..63 chars )||Passphrase to use for PSK authentication types. Defaults to "". WPA-PSK and WPA2-PSK authentication requires a minimum of 8 chars, while WPA3-PSK does not have minimum passphrase length.|
|security.management-protection ( allowed | disabled | required )||Whether to use 802.11w management frame protection (incompatible with management frame protection in standard wireless package). Defaults to 'allowed' when PSK authentication is used.|
|security.owe-transition-interface (name of interface)||Name of an interface whose MAC address and SSID to advertise as the matching AP for OWE transition mode. This is required for setting up open APs that offer OWE, but also work with older devices that don't support the standard. See configuration example below.|
|ssid (string)||SSID (service set identifier) is a name that identifies wireless network. Default: None.|
Opportunistic wireless encryption (OWE) allows wireless clients to enjoy encryption and management protection without requiring knowledge of a passphrase to connect. It is an improvement on open AP operating mode.
However, the OWE standard does not permit connections from devices that don't support it to prevent downgrade attacks. So to provide an open AP both for clients that don't support OWE and those that do, the following basic configuration is required.
You can reset the configuration of a wifiwave2 interface by removing it (e.g. /interface/wifiwave2/remove wifi1) and rebooting the device.
Information about the capabilities of each radio can be gained by running the `/interface/wifiwave2/radio print detail` command. The parameter names are self-explanatory and the `radio-mac` property can be used to determine, which wireless interface the radio corresponds to.
The registration table contains entries of associated wireless devices (both APs and stations) and provides information about their signal levels, data rates and other parameters when using the additional `/interface/wifiwave2/registration-table/print stats` parameter.