Slate AX firmware 4.1.0 beta 2 is out

alannts425 · 2022-09-16T23:06:36.334Z

Screenshot_20220917-065941_Google Play Store1600×1220 63.7 KB

Hi, may i know why the android app for gl.inet yet to be updates to 1.3.1 because currently am unable support the latest beta version of 4.1.0 on both router Flint and Slate AX as well. Thanks!

K3rn3l_Ku5h · 2022-09-16T23:35:25.669Z

Thats a crumpet warmer . We will be needing the official branded Gl.iNet ROG areoactive cooler 6 in Slate black.

What did it cool it down to before it turned off, if it turned off? How loud was it.

alzhao · 2022-09-17T00:35:56.732Z

For some reason Google play update slow. Can you download apk directly?

alannts425 · 2022-09-17T00:58:52.481Z

Screenshot_20220917-085737_Samsung Internet Beta1080×2400 151 KB

The apk version also 1.3.0?

Leo · 2022-09-17T04:28:45.605Z

I just upload the apk of 1.3.1(119). Check here.
Compared to 1.3.0(118), 1.3.1(119) only fixes a bug that GL-B2200 fail to add a sub mesh node in certain case.
The app is still under development for features related to firmware 4.1.

alannts425 · 2022-09-17T04:42:11.474Z

Screenshot_20220917-124127_Samsung Internet Beta1080×2400 166 KB

Download from where 1.3.1?

limbot · 2022-09-17T04:52:44.238Z

@Leo

My Flint (4.0.1 B2) is still not showing clients in cloud management mode even with new app version

Screenshot_2022-09-17-14-50-22-842_xyz.goodcloud.glinet1080×2340 126 KB

Leo · 2022-09-17T05:02:47.866Z

alannts425:

Hi, may i know why the android app for gl.inet yet to be updates to 1.3.1 because currently am unable support the latest beta version of 4.1.0 on both router Flint and Slate AX as well. Thanks!

Google Play still in review the version 1.3.1(119), don’t know why they take a very long time to review recently.

The app 1.3.0(118) & 1.3.1(119) support most of the features of firmware 4.1, except some new features, like Multi-WAN, Drop-in Gateway Mode. Still working on it.

alannts425 · 2022-09-17T05:17:00.871Z

I have trying to open up the glinet app after upgrade to latest firmware of 4.1.0, but unfortunately the app is not open up on both router flint and slate ax as well after upgraded.

Leo · 2022-09-17T05:17:22.528Z

limbot:

My Flint (4.0.1 B2) is still not showing clients in cloud management mode even with new app version

It is a firmware bug, exist in firmware 4.1 too.
I will forward to firmware team, thank you!

Leo · 2022-09-17T05:43:50.563Z

It works well in my phone. Could you give me more info about the app issue in your end? Screenshot or screenrecorder. Thanks.

YouTube

app 1.3.1 + GL-AX1800 4.1

cafebug · 2022-09-17T05:59:00.819Z

GL-inet Android App 1.3.1 is now available to download.

Screenshot_20220917-1356211440×3040 216 KB

alannts425 · 2022-09-17T06:22:05.745Z

Screenshot_20220917-142056_glinet1080×2400 90.2 KB

Blank?

alannts425 · 2022-09-17T06:25:50.567Z

Screenshot_20220917-142352_glinet1080×1420 111 KB

After upgrade from google play for 1.3.1 version, finally the gl.inet app able to open up.

gfondeur · 2022-09-17T14:33:32.724Z

I found two bugs, first the VPN it’s leaking my DNS no matter what, second the fan goes back to the 75C setting as soon I close the screen

Max3 · 2022-09-18T11:51:19.665Z

Ok, this latest firmware is not stable at all with my setup. Wireguard randomly disconnects end reconnect very often (REKEY-TIMEOUT):

Sun Sep 18 12:24:26 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Sun Sep 18 12:24:26 2022 daemon.notice netifd: Interface 'wgclient' has lost the connection
Sun Sep 18 12:24:26 2022 daemon.notice netifd: Network device 'wgclient' link is down
Sun Sep 18 12:24:27 2022 daemon.info dnsmasq[8230]: exiting on receipt of SIGTERM
Sun Sep 18 12:24:27 2022 daemon.notice netifd: wgclient (8476): udhcpc: started, v1.33.2
Sun Sep 18 12:24:27 2022 daemon.notice netifd: wgclient (8476): udhcpc: sending discover
Sun Sep 18 12:24:30 2022 daemon.notice netifd: wgclient (8476): udhcpc: no lease, failing
Sun Sep 18 12:24:30 2022 daemon.notice netifd: wgclient (8476): udhcpc: started, v1.33.2
Sun Sep 18 12:24:30 2022 daemon.notice netifd: wgclient (8476): udhcpc: sending discover
Sun Sep 18 12:24:31 2022 daemon.notice netifd: Interface 'wgclient' is now down
Sun Sep 18 12:24:31 2022 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Sep 18 12:24:32 2022 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=KEYPAIR-CREATED SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Sun Sep 18 12:24:32 2022 daemon.notice netifd: Interface 'wgclient' is now up
Sun Sep 18 12:24:32 2022 daemon.notice netifd: Network device 'wgclient' link is up

And Also repeater randomly disconnect/reconnect and I have a lot of this on my log:

Sun Sep 18 09:19:29 2022 daemon.notice wpa_supplicant[2797]: wlan-sta0: Unknown event 62
Sun Sep 18 09:19:32 2022 daemon.notice wpa_supplicant[2797]: wlan-sta0: Unknown event 62

elpmeh · 2022-09-20T11:49:36.717Z

I think its your webrtc thats leaking? ive just tried dns leak testing via my nas and im getting the correct DNS, try a non browser based DNS + IP leak tool online tht goes through the torrent client and not your web browser

Thomasinaz · 2023-05-13T15:24:05.314Z

Still same problem with x3000 not respecting failover priority order of connections when using wireguard.

alzhao · 2023-05-24T14:13:29.774Z

Wireguard, once connected, will keep using the same interface, unless it is broken.
So if you have two connection, cable and 5G NR. If cable connection is broken the wireguard will reconnect using the 5G NR connection. But if calbe connection come back the wireguard will not reconnect using the cable connection, it will keep using the 5G NR connection,

Thomasinaz · 2023-05-24T14:37:48.627Z

Failover is not working correctly even without any VPN connected. With Ethernet and 5g cell connected and failover set to prioritize cellular before Ethernet, all data still taken from Ethernet even after reboot