Slate AX firmware 4.1.0 beta 2 is out

The it is a bug. It should be as described

Finally, I saw my Slate AX fan is running :slight_smile:

image

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!

Thats a crumpet warmer :laughing:. 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.

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

The apk version also 1.3.0?

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.


Download from where 1.3.1?

@Leo

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

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.

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.

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

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

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

1 Like


Blank?

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

1 Like

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

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

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

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