AR-750S Ver. 3.101 drops 5G Wifi

Johnex · 2020-03-23T20:11:14.552Z

It is very easy to copy logs. Follow the guide to log into the router using SSH from here:

docs.gl-inet.com

SSH to the Router - GL.iNet Docs

Documentation for GL.iNet Productions

Then you just have to run:
logread
and
dmesg

You can paste the logs here.

wellnw · 2020-03-24T06:55:44.016Z

Hi,
Thank you for the log you provided, I saw the abnormal information, I updated the wifi driver, you can use the following version to confirm the problem, I guess the 3.100 version of the firmware will take a long time to cause problems
http://download.gl-inet.com/firmware/ar750s/snapshots/

mrschwarz · 2020-03-24T13:37:16.060Z

I updated using the ‘openwrt-ar750s-3.104-0324.tar’ image. Hopefully, I will have nothing to report after a few days.

wellnw · 2020-03-25T03:12:06.028Z

@mrschwarz
I hope so, and look forward to your feedback, I will also test the new version of the firmware here

mrschwarz · 2020-03-30T13:47:28.025Z

This morning, everything was working on the 5G band. After a few minutes, I was unable to download anything. I tried to access the admin web page, but nothing happened. I connected to the 2.4G band and then reconnected to the 5G band it seemed to start working again. I followed the instructions above for copying the logs.

Here is a link to the folder that contains the logs: https://drive.google.com/drive/folders/1EAaBfQu41Ni2gpk8VBSDR3BdgJcZo7Xt?usp=sharing

wellnw · 2020-03-31T07:19:32.002Z

mrschwarz:

I am not sure if this is posted in the right category. I have been using the Slate since I got it about 2 months ago without a problem. I have a couple of devices connected to the 2.4G band and the rest of the wireless devices (5) connected to the 5G band.

About a week or so ago, I auto updated to version 3.101. The next morning, the devices connected to the 5G band lost the connection. During the time I could access the admin page, the status of it would show that it was on (but it wasn’t). The only way to restore it was either turning it off, then on again or power cycling the router.

This happened at least once each day. One day, shutting off 5G and turning it back on resulted in it turning itself off after the countdown on the slider. Another couple of times, I was unable to access the admin page at all until I power cycled.

I performed a factory revert (reset). I lost the 5G band overnight and could not access the admin page from the 2.4G band. I reverted the router back to ver. 3.100 yesterday. 34 hour later, the 5G band is still working. Most likely, in this case it is related to the 3.101 update.

@mrschwarz
From the log, I can’t see the exception, but only see that your terminal is 10.192.45.207. This device is requesting an IP address, then the connection is disconnected, and then you see that you switched back to 5G after switching to 2.4G. If possible, I Want to log in remotely to your routing background to see, you can contact me via email, guilin.wang@gl-inet.com

mrschwarz · 2020-03-31T14:04:44.918Z

It happened again this morning. Refer to the shared folder above for the new log files.

wellnw · 2020-04-03T04:56:37.485Z

@mrschwarz
I have sent the firmware version 3.104 via email. You can upgrade and test it. I am currently testing this issue here. I look forward to your feedback. Thanks again

viajeros · 2020-04-09T01:47:38.492Z

Is there any update?

wellnw · 2020-04-09T03:15:49.513Z

@viajeros
You can send email (guilin.wang@gl-inet.com)to me ,and I will send the lastest firmware to you.

Finlander · 2020-05-27T17:09:45.666Z

I’m seeing the same problem with 3.104… in the repeater mode the 5G network provided by the Slate disappears randomly. The 2.4G network remains. The only way to get the 5G back appears to be to power cycle the router.

I couldn’t attach the full logs (“New users are not allowed to upload attachments”), but below is a segment of the end of the syslog. The “daemon.err hostapd: Failed to set beacon parameters” error is probably of interest:

Tue May 26 22:43:52 2020 daemon.notice netifd: wwan (3821): udhcpc: sending discover
Tue May 26 22:43:53 2020 daemon.notice netifd: wwan (3821): udhcpc: sending select for 192.168.1.188
Tue May 26 22:43:53 2020 daemon.notice netifd: wwan (3821): udhcpc: lease of 192.168.1.188 obtained, lease time 86400
Tue May 26 22:43:53 2020 daemon.notice netifd: Interface 'wwan' is now up
Tue May 26 22:43:56 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:41:25 2020 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta)
Wed May 27 11:41:29 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:41:35 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:41:41 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:41:47 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:41:53 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:41:59 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:05 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:11 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:17 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:23 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:25 2020 daemon.info hostapd: wlan1: STA 84:fd:d1:fd:2f:eb IEEE 802.11: authenticated
Wed May 27 11:42:25 2020 daemon.info hostapd: wlan1: STA 84:fd:d1:fd:2f:eb IEEE 802.11: associated (aid 1)
Wed May 27 11:42:25 2020 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 84:fd:d1:fd:2f:eb
Wed May 27 11:42:25 2020 daemon.info hostapd: wlan1: STA 84:fd:d1:fd:2f:eb RADIUS: starting accounting session 853FC65C6306F073
Wed May 27 11:42:25 2020 daemon.info hostapd: wlan1: STA 84:fd:d1:fd:2f:eb WPA: pairwise key handshake completed (RSN)
Wed May 27 11:42:25 2020 daemon.info dnsmasq-dhcp[2870]: DHCPDISCOVER(br-lan) 84:fd:d1:fd:2f:eb
Wed May 27 11:42:25 2020 daemon.info dnsmasq-dhcp[2870]: DHCPOFFER(br-lan) 172.20.20.100 84:fd:d1:fd:2f:eb
Wed May 27 11:42:25 2020 daemon.info dnsmasq-dhcp[2870]: DHCPREQUEST(br-lan) 172.20.20.100 84:fd:d1:fd:2f:eb
Wed May 27 11:42:25 2020 daemon.info dnsmasq-dhcp[2870]: DHCPACK(br-lan) 172.20.20.100 84:fd:d1:fd:2f:eb Starpad
Wed May 27 11:42:29 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:35 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:41 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:47 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:53 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:42:59 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:05 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:11 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:17 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:23 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:29 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:35 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:41 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:47 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:53 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:43:59 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:05 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:11 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:17 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:23 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:29 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:35 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:41 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:47 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:53 2020 daemon.err hostapd: Failed to set beacon parameters
Wed May 27 11:44:59 2020 daemon.err hostapd: Failed to set beacon parameters

wellnw · 2020-05-28T03:35:53.230Z

Hi
You can log in to luci interface and export systemlog and kernellog

Finlander · 2020-05-28T06:29:23.428Z

That’s the command line log access described earlier in this thread?

Bapho · 2020-05-28T21:26:58.855Z

Hello, AR-750S indeed drops the 5G WiFi connection when I am tethering, that is, when I do have my Android phone connected to the router via USB cable, utilizing EasyTether ipk. 5G SSID would disappear and PC that is connected witlessly would disconnect from the internet.

I don’t recall AR-750 did drop the 5G WiFi connection when I utilized it as a repeater, connected wireless to a wireless Asus router, and AR-750 was running VPN.

I will add into the post more details about AR-750 and the log files when I do get a chance.

Edit:

Firmware current version 3.101

The logs don’t begin 14 hours before, where WiFi drop was happening. I will post the logs when I notice the WiFI 5G channels drops, and collect the logs from the router.

Thanx,
Hareth Albustani

alzhao · 2020-05-29T08:00:54.776Z

Are you repeating on wifi that has many AP with the same SSID? Like public wifi

or only one AP, like in your home?

Do you have the wifi channel information?

Finlander · 2020-05-29T18:07:14.531Z

I just checked, and we were talking about the same logs. I emailed them to you yesterday because I couldn’t attach them here (lacking privileges to do so).

Finlander · 2020-05-29T18:11:31.664Z

I’m repeating currently on a home WiFi (single AP, different SSID).

Here’s the wireless info from luci (this is while the 5G network has disappeared).

slate_debugging

Note that I’m currently in NYC so there are a lot of wireless networks around (in case that makes a difference). In other words, the channel space is probably quite congested.

alzhao · 2020-05-30T03:48:37.170Z

Just want to make sure repeater is connected and you are able to access internet?

During connection process the WiFi may disable it for a short period.

Finlander · 2020-06-04T19:59:26.173Z

Yes, of course it has been connected. It works initially fine, until at some point the 5G network goes missing and connectivity to it no longer works until the router has been restarted. the non-5G network remains, so the above diagnostic information has been retrieved from the router via it while the 5G network has been MIA.

gentry44 · 2021-05-03T20:18:36.126Z

Hello - I posted in a different thread, but doing some research this is exactly what is happening to me. The logs look the same as does the dashboard showing that radio0 is not transmitting. Has a fix been identified?