New Openspot 4 Pro disconnects from wifi

pcdavis

Updates in italics.

My OS4 Pro will not stay connected to wifi. Sometimes as little as 5 minutes and sometimes as long as 90, the unit will disconnect from wifi and flash blue LED. I have 2 ssid's saved but it will not connect to either primary or backup. When the disconnect happens, the wifi portion of the radio is inoperative. The only way to resume operation is to power cycle. This happens mostly during traffic on a connected TG. I'm using DMR with Brandmeister. I've done a factory reset, reloaded the factory firmware and tried multiple settings changes with no improvement. The wifi locks up and will not respond until power cycled. Has anyone else had this issue? Does Norbert respond timely? I'm still waiting for his response.
I've been testing every since the first post. What I've found is that my main router, a Linksys WRT1900AC, seems to be causing the OS4 to have wifi issues. I've connected an older Netgear WNDR3700 router to my network and used that to connect the OS4. When I do this, I have no wifi issues with the OS4. I then went back to testing with the Linksys. I changed advanced wifi settings but none helped. What did help was changing the wifi mode to 'legacy'. After that, I had no more wifi issues with the OS4. Problem is, that drops the connection speed to half of what it is using 'N'. This causes traffic throughput issues with other devices on my wifi network. For now, I plan to keep the Netgear on my network to use only with the OS4. Hopefully, Norbert is monitoring this forum. I think the OS4 is a fantastic device and love all its wonderful capabilities. I will be glad to help troubleshoot what is going on with the interfacing of the hardware. I have many years of electronics background and understand troubleshooting techniques. If I'm having this issue, many others will too and I want to see the OS4 be a successful product in the radio world.

pcdavis

I've updated the original post with new information in italics.

HA2NON

Thank you for the information. We don't know what causes the incompatibility with your main router. Try looking at the device log over the USB serial console to find out what's exactly happening.

pcdavis

HA2NON Thanks for the reply. I sent you a log a few days ago. The only thing I see is a beacon timeout, then the disconnect.
The incompatibility concerns me but not nearly as much as the inability of the OS4 to connect to my other router that is in my ssid list in the network settings. I can't imagine how the disconnect from my main router can cause a total crash of the wifi of the OS4. It takes a manual power off and then back on to bring the OS4 back to operational. Do you have any thoughts on this?

mucflyer

It seems I have same issue with Draytek router. I did factory reset, but issue still persists.

connecting to slot #0 ssid Nautilus key xxxxxxxxxxxx
net-wifi: disconnected from Nautilus 00:00:00:00:00:00 (no ap found)

And eventually connects:

net-wifi: connected to Nautilus 14:49:bc:2a:77:48 ch 6 authmode wpa1/2
net-wifi: got ip4 addr 10.36.92.100 gw 10.36.92.1 netmask 255.255.255.0 (static: 0), changed: 1

And after some time drops....

modem-djq: emptied, closing
net-wifi: disconnected from Nautilus 14:49:bc:2a:77:48 (beacon timeout)

Router log:

Message
 2024-02-12 10:40:20	 [WLAN] WPA: recieve Msg4 of 4-way (7C-DF-A1-E4-EF-A4)
 2024-02-12 10:40:20	 WLAN_DBG - Warning: drop EAPOL packet
 2024-02-12 10:40:20	 WLAN_DBG - EAPoL_handler, from 7c:df:a1:e4:ef:a4
 2024-02-12 10:40:20	 [WLAN] WPA: send Msg3 of 4-way
 2024-02-12 10:40:20	 [WLAN] WPA: recieve Msg2 of 4-way (7C-DF-A1-E4-EF-A4)
 2024-02-12 10:40:20	 WLAN_DBG - Warning: drop EAPOL packet
 2024-02-12 10:40:20	 WLAN_DBG - EAPoL_handler, from 7c:df:a1:e4:ef:a4
 2024-02-12 10:40:20	 [WLAN] WPA: send Msg1 of 4-way
 2024-02-12 10:40:20	 WLAN_DBG - Nautilus: STA 7c:df:a1:e4:ef:a4 Mixed(WPA+WPA2)/PSK: [2.4G] MLME Associate.
 2024-02-12 10:39:42	 [WLAN] [BandSteering] 2.4G client (7c:df:a1:e4:ef:a4) wait 4 seconds to connect 2.4G.
 2024-02-12 10:39:42	 [WLAN] [BandSteering] 2.4G client (7c:df:a1:e4:ef:a4) wait 4 seconds to connect 2.4G.
 2024-02-12 10:39:42	 [WLAN] [BandSteering] 2.4G client (7c:df:a1:e4:ef:a4) wait 5 seconds to connect 2.4G.
 2024-02-12 10:39:42	 [WLAN] [BandSteering] 2.4G client (7c:df:a1:e4:ef:a4) wait 5 seconds to connect 2.4G.
----------- cut log here ---------------
 2024-02-12 10:40:28	 WLAN_DBG - Dot1x_session_stop
 2024-02-12 10:40:28	 WLAN_DBG - Nautilus: STA 7c:df:a1:e4:ef:a4 Mixed(WPA+WPA2)/PSK: [2.4G] MLME Disassoc.

pcdavis

It seems your issue is slightly different than the one I had. Your unit will eventually reconnect. Mine could not. The wifi portion of the OS4 was totally dead until I power cycled. I was using an older model Linksys router that I had tried 2 different firmware systems on but neither one would work consistently with the OS4. I replaced the router with a new Asus and haven't had any issues since.