For anyone else having Wi-Fi connectivity issues with the SDS-1104X-E ...
When I tried to:
the scope would connect/disconnect/connect/disconnect endlessly. It just couldn't stick a connection.
TL;DR:UniFi has a master setting that activates a handful of advanced features. I have this enabled on my network.
That setting (and the features it enables, which are scattered all around) has a general disclaimer that stuff may break or become unstable. Go figure
Most of the features work just fine. But there's one in particular that causes an issue with the Siglent scope.
This feature affects the 2.4 GHz band by default - the band used by the scope:
Enable 2G Data Rate ControlIt's intended to maintain a baseline network performance by enforcing minimums - namely a bandwidth floor - and disassociating devices that don't meet them. Good for enterprise networks. Bad for home labs.
Simply disabling this feature brought my scope online for good. Goodbye, ethernet!
Gory DetailsAt first I blamed Wi-Fi driver implementation in the Linux OS (my scope is rooted and "software-modified"). It didn't instill confidence to find that browser-based network settings (DHCP, subnet mask, etc) only affect the ethernet interface. They don't seem to touch the Wi-Fi interface at all. So I telnet'd in via ethernet and poked around.
I tried to connect the scope to Wi-Fi manually.
wpa_supplicant -dd -K -D wext -i wlan0 -c /usr/bin/siglent/usr/wifi/wpa.conf
My buddy and I found the following in the output:
...
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
wlan0: Event DISASSOC (1) received
wlan0: Disassociation notification
wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=0
wlan0: Auto connect enabled: try to reconnect (wps=0 wpa_state=9)
...
Turns out my AP was kicking the scope off the network.
So much for that blame game
Edit: clarity