Overview
ClassVR headsets connect using WEP, WPA or WPA2 Personal on every model. WPA2 Enterprise (802.1x) works on the CVR-255 and later. WPA3, Wi-Fi 6E (6 GHz) and fast roaming (802.11r/k/v) are not supported on any model.
Applies to: CVR-155 / 155-A / 155-A1 · CVR-255 / CVR-255-64 · CVR-355-128 (Xplorer) · CVR-655-128 (Xcelerate)
Whatever your network setup, the headsets only need two things:
- Internal LAN access so headsets and the ClassVR Portal computer can see each other (same subnet or VLAN).
- External internet access for firmware and client updates, content and playlist syncing, and streamed or 3D resources.
WPA3 is not supported on any of our current devices; this will also be the case for many legacy devices which is why most environments will be compatible and still continue to support WPA2. From the QuickStart page you should see an option for all WiFi protocols supported. https://portal.classvr.com/classvr/quickstart-qrkeys.cfm
Quick reference by headset
The original CVR-155 is 2.4 GHz only. Every later model supports both 2.4 and 5 GHz, and the CVR-255 and later also support Wi-Fi 6.
| CVR-155 | CVR-155-A / A1 | CVR-255 / 255-64 / 355 Xplorer | CVR-655 Xcelerate | |
|---|---|---|---|---|
| Bands | 2.4 GHz only | 2.4 + 5 GHz | 2.4 + 5 GHz | 2.4 + 5 GHz |
| Wi-Fi 4 (802.11n) and older b/g | Yes | Yes | Yes | Yes |
| Wi-Fi 5 (802.11ac) | No | Yes | Yes | Yes |
| Wi-Fi 6 (802.11ax) | No | No | Yes (with 802.1x or WPA2-EAP) | Yes |
| Wi-Fi 6E (6 GHz) | No | No | No | No |
| Fast roaming (802.11r/k/v) | No | No | No | TBC |
| WEP / WPA / WPA2 Personal | Yes | Yes | Yes | TBC |
| WPA2 Enterprise (802.1x) | No | No | Yes | TBC |
| WPA3 Personal / Enterprise | No | No | No (use WPA2) | TBC |
Wi-Fi 6 networks: Wi-Fi 6 access points are backwards compatible, so older headsets still connect, using Wi-Fi 4 or 5. On the CVR-255 family, Wi-Fi 6 is listed as supported when using 802.1x or WPA2-EAP.
Security and authentication
Find your network type below to see which headsets support it and where to set it up. There are three setup routes: a QR code from the Portal QuickStart page, an Access Point profile in the Portal, or manually in the headset's Device Settings.
| Network type | CVR-155 range | CVR-255 / 355 | Set up via | Notes |
|---|---|---|---|---|
| WPA2 Personal (PSK) | Yes | Yes | QR code, Device Settings, or Portal Access Point (select WPA (PSK)) | Recommended for most schools. |
| WPA Personal | Yes | Yes | QR code, Device Settings, Portal Access Point | Legacy; use WPA2 where possible. |
| WEP | Yes | Yes | QR code, Device Settings, Portal Access Point | Insecure; not recommended. |
| PEAP (username + password) | See notes | Yes | QR code or Device Settings | For simple enterprise setups (Active Directory, RADIUS, cloud). MSCHAPv2 is applied automatically. |
| 802.1x EAP | No | Yes | Device Settings only | Not available by QR code or Portal Access Point. |
| EAP-TLS (certificate) | No | Yes | Portal Access Point or Device Settings | Not available by QR code. Needs TLS 1.0 enabled on the RADIUS server. |
| WPA3 Personal / Enterprise | No | No | – | Provide a WPA2 SSID for the headsets. |
Generate connection QR codes from the ClassVR Portal QuickStart page. A static IP can also be applied through a QR code; contact Support to set this up. The Xcelerate (CVR-655) is not yet covered by this table.
Manual 802.1x setup: We recommend your IT team does this. Scan the OS settings QR code to open Android settings on the headset, then add the network as above. Plugging a USB keyboard into the headset (USB-A to USB-C adapter) makes typing the SSID and credentials much easier.
Device OS settings QR code.
Key points to consider
- Same subnet / VLAN. Headsets and the Portal computer must see each other on the LAN, including UDP broadcast. If not, headsets show as offline in the Portal.
- Prefer 5 GHz, but keep 2.4 GHz if you using dual-band. 5 GHz gives better speed and stability.
- No 6 GHz-only SSIDs. No headset supports Wi-Fi 6E, so broadcast the SSID on 2.4Ghz and/or 5GHz too.
- WPA3 is not supported. Give headsets a WPA2 SSID.
- Enterprise Wi-Fi needs a CVR-255 or later. The CVR-155 range cannot use 802.1x or EAP-TLS.
- Fast roaming (802.11r/k/v) is not supported. If it's enabled on the headset SSID, headsets may fail to connect or drop when moving between access points. Disable it on that SSID if you see this.
- Client isolation. (or AP isolation) Disable it or if a 'Guest WiFi' where it's a requirement; whitelist the headsets to enable local visibility on the SSID, or the Portal cannot reach the headsets across the LAN.
- Access point placement and load. If running dual-band make sure sufficient SNR (Signal to Noise Ratio) settings are in place to AP's don't capture and isolate devices.
- Firewall and filtering. Headsets need outbound internet access for updates and content. See the ClassVR Connectivity Guide for domains and ports.
- MAC filtering / IP binding. Device MAC addresses are listed in the Portal device list, or on the headset itself.
Troubleshooting
Start with the headset's Information screen: it checks Wi-Fi, internet, Portal connection, UDP broadcast and gateway, and shows which one fails.
| Symptom | Likely cause | What to do |
|---|---|---|
| CVR-155 can't see the network | SSID is 5 GHz only | Broadcast the SSID on 2.4 GHz as well. |
| No headset can see the network | 6 GHz-only SSID, or a hidden SSID | Broadcast on 2.4/5 GHz; add hidden SSIDs manually in Device Settings. |
| Wi-Fi saves but the connection is refused | WPA3 security, or enterprise Wi-Fi on a CVR-155 | Use a WPA2 SSID; enterprise Wi-Fi needs a CVR-255 or later. |
| EAP-TLS gives error 400 or 269, or "do not possess a common algorithm" | TLS 1.0 disabled on the RADIUS server | Enable TLS 1.0, even briefly to confirm the cause, then contact Support. |
| No 802.1x or EAP-TLS option in the QR generator | Expected | Use Device Settings (802.1x) or a Portal Access Point (EAP-TLS). |
| No MSCHAPv2 option when setting up PEAP | Expected | It is applied automatically. |
| Drops when moving between rooms or APs | Fast roaming (802.11r/k/v) enabled | Disable 802.11r on the headset SSID. |
| Connected to Wi-Fi but offline in the Portal | Different subnet/VLAN, client isolation, or UDP blocked | Put headsets and the Portal PC on the same subnet; turn off isolation. |
| Connected but no updates or content | Firewall, proxy or filtering | Allow ClassVR domains; see the Connectivity Guide. |
| Slow or dropping connection | 2.4 GHz congestion, AP placement, heavy load | Move to 5 GHz, reposition the AP, pre-download content. |
Still stuck? Send Support a screenshot of the Information screen and your network type (from the Security table above). [ support@classvr.com ]
What is Wi-Fi 6?
First introduced in 2018, Wi-Fi 6 (802.11ax) is the latest wireless connection protocol. Many devices support Wi-Fi 6, such as phones, laptops and the latest smart televisions. Wi-Fi 6 is the evolution of wireless network connections, improving on the existing Wi-Fi 5 (802.11ac).
In order to use Wi-Fi 6, you will need to upgrade your current router and other relevant network equipment, as this is reliant on hardware rather than software. Not all devices currently available are Wi-Fi 6 compatible. However Wi-Fi 6 technology is completely backwards compatible with older wireless connections and will also support devices using Wi-Fi 2 to Wi-Fi 5 (802.11a/g/n/ac).
In 2020, another improvement to Wi-Fi 6 was introduced. Known as Wi-Fi 6e, which has been designed to work on a different frequency band. Previous Wi-Fi protocols used either 2.4GHz or 5GHz frequencies, but Wi-Fi 6e uses 6GHz frequency which is not currently used by any other wireless connections. This allows for a much faster and reliable connection which cuts down on issues such as latency and interference.
At present, ClassVR devices support Wi-Fi 6 but do not support Wi-Fi 6e. The authentication method 802.1x is also possible but must be added manually to the devices via the device settings rather than our standard QR code creation method.
Setting up the ClassVR devices on a Wi-Fi 6 network
NOTE: We recommend getting your IT associate to go through this process
Setup needs to be done on the headsets. In order to access the required network settings, scan this QR code:
You should then see the following menu on the headset:
Select Network & Internet > Wi-Fi > Add network.
Enter the SSID of your network (Note - to make this easier, you can plug a computer keyboard into your headset using a USB-A to USB-C connector) Then select Security. In the menu that comes up, select 802.1x EAP.
Fill in the rest of the details on this screen according to your network setup.
Once this is entered, select Save. You should now be able to select the network connection from the list of Wi-Fi connections available.
Related articles: ClassVR Connectivity Guide · Checking Connectivity · Portal Network Diagnostics · Troubleshooting Content Download Speeds