AR-750S Ver. 3.101 drops 5G Wifi

alzhao · 2020-03-19T09:40:54.693Z

Thanks for reporting back and we will investigate this problem.

Is there any way you can send back the logs after 5G lost?

wellnw · 2020-03-19T10:02:24.309Z

@mrschwarz
Can you export a log to me, when there is an exception, you can refer to the following methods,

System log

Kernel log

or upgrade to version 3.102 to see, this is our latest release version

exitguy · 2020-03-19T11:25:31.743Z

wellnw:

or upgrade to version 3.102 to see, this is our latest release version

There is no 3.102 either here https://dl.gl-inet.com/firmware/ar750s/release/ or here https://docs.gl-inet.com/en/3/release_notes/gl-ar750s-ext/

mrschwarz · 2020-03-19T13:40:11.203Z

As I wrote in my first post, I reverted back to 3.100 and the problem went away. I’ll upgrade to 3.101 again. If/when it fails, I’ll post the logs here.

Thx for the response.

wellnw · 2020-03-20T01:13:55.967Z

@exitguy
Sorry, my mistake, the latest release version is indeed 3.101, you can use the following link to test the firmware, version 3.103
https://dl.gl-inet.com/firmware/ar750s/snapshots/
@mrschwarz
We have changed 3.100 and 3.101 as follows,without modifying any wifi part:

Disable IPV6 by default
2.Fix tor selection country initialization failure
3.Add kmod-nf-nathelper kernel package
4.Fix openvpn rules cannot be modified
Looking forward to your feedback, if there is a disconnection, will your router work in repeater mode or normal AP mode?

mrschwarz · 2020-03-20T13:50:28.467Z

I didn’t change it to AP mode or repeater after the failure. When the admin web page was accessible, I turned the 5G band off, then on a couple of times. I clicked the ‘reboot’ button once. Other times when I couldn’t access the admin web page via the 2.4G band, I pulled the power cord and re-inserted it. I didn’t try to access the admin web page from a wired connection to it at any time.

Currently, the router has been running for a few minutes more than 24 hours and the 5G band hasn’t dropped yet. When I upgraded to 3.101, I did it the same way as before. I used the ‘Online Upgrade’ tab on the Upgrade page. I can’t recall how much time elapsed between the upgrade and the first 5G band failure.

Is there a test process or procedure you want me to perform if/when it fails again?

wellnw · 2020-03-23T01:03:10.497Z

@mrschwarz
Hi, thanks for the feedback. If the problem occurs again, please follow the above response and provide me with the log information. Thanks again.

mrschwarz · 2020-03-23T18:12:54.374Z

OK. It happened this morning. One suggestion…There was no way I could figure out how to output the logs or even copy and paste them. I had to take many screen shots to get the logs you requested. This is unacceptable. The MUST be a way to copy/paste the logs. I spend 30 minutes doing this. While I was doing it, the 5G band came back on. I am unable to upload the zip file, even though it is less than 5,000KB.

Boy, you guys don’t make diagnosis easy on us users, do you?

Here is a link to the zip file: https://drive.google.com/file/d/1WqfCmFYIbXyVc6nT8Yq7QjTLK0vw7U_g/view?usp=sharing

mrschwarz · 2020-03-23T18:21:02.329Z

I just upgraded to 3.103. I guess I’ll see what happens with this version. If it continues, I can still go back to 3.100.

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