Category: Blog

323a Sesión de Tesos en Wi-Fi: Installing Dual Orb Sensors on WLANPi

323a Sesión de Tesos en Wi-Fi: Installing Dual Orb Sensors on WLANPi

In this session we learn how to install dual Orbs in a WLANPi. One reports on the Ethernet connection and the second reports on the Wi-Fi connection. Simultaneously.

Conclusion: This would not have been possible without the valuable input and expertise from Mr. Keith Parsons, Josh and Daniel from Orb, Adrián from Intuitibits, Ben and his son Dylan from nOversight and many others in the community. I put together a .deb file with all the necessary modifications. Well, let me clarify what I mean when I say, “I put together a .deb file”, I interacted with AI for hours and hours, burned countless images, found errors, fed them back to the AI, and repeated the process until I finally found the file containing everything necessary to accomplish dual orbs on the wlanpi.

Here are the instructions to install dual Orb on a WLANPi.

File needed: https://tinyurl.com/33azpchr

I used it on R4 and Pro and it works seamlessly on both. The WLANPi R4 has two Panda Wireless Model AXE3000 with MediaTek mt7921u chipset [Wi-Fi 6E NICs]. Download this file to your downloads, open the terminal, and navigate there, then:

# 1. Copy the file to the WLANPi [change IP to your WLANPi’s]
scp wlanpi-dual-orb_1.0.2_all.deb wlanpi@192.168.128.112:~

# 2. SSH to the Pi and Install — this prompts for the SSID and password and sets everything up
sudo apt install ./wlanpi-dual-orb_1.0.2_all.deb

# 3. Reboot — orb-install.service runs on boot, installs Orb, starts both sensors
sudo reboot

That is it! I noticed issues with cloned images on the network. The newly created images would hold the orbIDs and names from the original image. If you clone the image and multiple WLANPi’s use the same image, run sudo orb-reset-identity to delete old orbIDs and hostnames. This creates new orbIDs and names using the wlanpi hostname. The Orb dashboard can now detect a new Orb.

# 4. Clear old orbIDs and hostnames
sudo orb-reset-identity

# 5. Reconfigure SSID, password, encryption
sudo orb-wifi-configure

Here are some useful commands I compiled during the process:
sudo systemctl status orb.service # Status of Ethernet Orb
sudo systemctl status orb-wifi-sensor.service # Status of Wi-Fi Orb
sudo journalctl -fu orb # Live Ethernet Orb logs
sudo journalctl -fu orb-wifi-sensor # Live Wi-Fi Orb logs
sudo orb-wifi-configure # Change Wi-Fi credentials
sudo systemctl daemon-reload # Reloads systemd configurations
sudo systemctl restart orb.service # Restarts the Ethernet Orb service
sudo systemctl restart orb-wifi-sensor.service # Restarts the Wi-Fi Orb service
sudo orb-reset-identity # Deletes old orbIDs on cloned images [new OrbID]
sudo orb-reset-identity –dry-run # shows what would be deleted, no changes made

Aruba 635 & iPad Pro Wi-Fi 6E

Aruba 635 & iPad Pro Wi-Fi 6E

If you haven’t read Jiri Brajcha’s blogs showing test results with iPad Pro and Cisco 9136 AP, I highly recommend you do so at https://www.jiribrejcha.net He does an excellent job at testing iPad’s band preferences based on channel width and transmit power levels. In this blog, I will share my findings on other tests using an iPad Pro with Wi-Fi 6E and an Aruba AP 635.

Lab Config

Aruba AP 635: FW 8.10.0.1 LSR & 8.11.0.1 SSR
2.4 GHz – channel 1, 20MHz, 8dBm, SSID: Aruba_635_2.4_8dBm
5 GHz – channel 36, 20MHz, 14dBm, SSID: Aruba_635_5_14dBm
6 GHz – channel 101 [PSC], 80MHz, 16dBm, SSID: Aruba_635_6_16dBm
SSID: Aruba_635_6_Guest
Acceltex Accelerator v2
Mikrotik hAPac2
iPad Pro 11″ 4th Gen,OS version 16.1 (20B82)
MacBook Pro M1:
Ekahau AI Pro 11.1.3 with Sidekick v2
WiFi Explorer Pro 3:
WLANPi Pro configured as remote sensor
AirTool 2:
WLANPi Pro configured as remote sensor for multi-source captures

In this lab I did not test with the same SSID across all three bands. As you can see, I had one SSID per band, with two SSIDs being advertised in 6GHz. With the initial setup, the iPad could see all SSIDs.

SSIDs on iPad

In WiFi Explorer Pro 3, I added a WLANPi Pro as a remote sensor and could see all networks without any problems.

SSIDs on WiFi Explorer Pro 3

Ekahau discovered all networks as well including the 6GHz SSID.

6GHz Ekahau

In Airtool 2, I added another WLANPi Pro as a remote sensor and in Multi-Source Capture… mode, I selected channels 36 and 101 [PSC] and performed packet captures.

Airtool 2 Multi-Source Capture

I could see the beacon in 5GHz with the Reduced Neighbor Report advertising both networks in channel 101 with their respective short SSIDs.

Short SSID Transmitted
Short SSID Guest [Non-transmitted]

On a separate capture I obtained beacons in channel 1 and 2.4 also had RNR. Beacons on channel 101 showed the Aruba_635_6_16dBm SSID with the Multiple BSSID element and the Aruba_635_6_Guest spelled out.

2.4GHz Beacon with RNR
5GHz Beacon with RNR
6GHz Beacon with Multiple SSID element

With these configurations, the iPad could successfully associate to the networks in 2.4GHz, 5GHz, and 6GHz.

I disabled the 2.4GHz and 5GHz radios in the Aruba AP 635 and now the iPad could not see the SSIDs being advertised in 6GHz. Ekahau and WiFi Explorer Pro 3 continued to see the 6GHz SSIDs. I also disabled the 2.4/5GHz radios while the iPad was associated to 6GHz and it worked until the iPad went into sleep mode, when the iPad was awaken, it could not associate anymore even if the network name and credentials were added manually.

iPad Pro 6GHz SSID not found

As Jiri mentioned in his blog, the iPad relies on the RNR announced in 2.4/5GHz to discover 6GHz networks. Note that in my test, none of the SSIDs announced in 6GHz were being advertised in either 2.4 or 5GHz. Each band had its own SSID, but because of the RNR, the 6GHz SSIDs were discovered by the iPad and the iPad was able to connect to 6GHz without any issues.

Now with 6GHz only operating in the AP, I was expecting to see Unsolicited Probe Responses and Fast Initial Link Setup [FILS] frames, but I could only see beacon frames advertised in 6GHz. With the help of Santiago Carmona from Colombia, we realized that we had Firmware 8.10.0.1 LSR running. I updated the AP to 8.11.0.1 SSR and now FILS frames were being transmitted.

6GHz Beacons and FILS

One thing that got my attention on the FILS, the Short SSID for the transmitted SSID was backwards from the originally generated hexadecimal value. Instead of being e468b379, on the FILS it was listed as 0x79b368e4. The non-transmitted SSID Aruba_635_6_Guest’s short SSID was listed as generated [0xb8af9480]

Backwards Short SSID

If you want to see the video with all the steps and miss-steps during the data collection, visit https://thewifiofthings.com/113a-sesion-de-tess-en-wi-fi-aruba-635-ipad-ekahau-acceltex-wifiexplorer-airtool-wlanpi-pro/ just be aware that it is in Spanish during our 113th Sesión de Tes@s en Wi-Fi.

I will be doing more tests with other client devices and will be posting them here.

Theme: Overlay by Kaira
Wi-Fi Brings Life!