Do you mean these two? Thanks~~
I donāt think it Iptables-nft is becuase GUI is based on openwrt 21.02 and Luci is 22.03
You should just need the sqm-scripts
I also installed Luci-app-sqm to actually us the package
Just now you need to update uboot otherwise might be a issue.
1 Like
Has anyone noticed slower wifi 5.ghz speed with the new 4.x version? i was having better wifi speed with 3.x and now with 4.x the wifi speed cut in half.
latest 3.x = 400-500 download
latest 4.x = 100-200ās?? download
How are you testing?
Are you testing in the same location?
Personally I have a spot with a x marked on it I test from.
alzhao did mention something about the power turned down but I thought its was the GL-AXT1800 Slate AX because of DFS channels or something.
speedtest windows app and fast.com (same server location and closest to me)
i stand next to the router to see difference.
disregard my other post
I will get some test on the Flint that needs to update from 3.x to 4.x
My Report on Upgrading from 3.124 to 4.1.0 on Flint (GL-AX1800)
- @K3rn3l_Ku5hās instruction is extremely helpful. Thanks!
- UBoot upgraded without issue
- New Firmware (4.1.0) flashed without issue
-
luci-app-sqmandsqm-scriptsinstalled without issue
- Restore configuration from backup was NOT successful. It will break wireless.
- Unable to restore VPN Configs, VPN Policies, WAN Block Lists (That I know of)
- Ended up manually restoring settings by ssh-ing into the router and carefully inspect each and every file in
/etc/configand update as needed - Updated Wireless (WiFi) settings via GUI
Speed is more or less the same (306 kbps before update to 273 kbps after update), tested with WireGuard on.
Time consumed: around 2 hrs.
Ahhhā¦ To infer displeasure or being obnoxious from a log post is a bit of a stretch. Neither is true. I am posting concerning a beta issue that would be good to fix. There is nothing else going on.
This is a FLINT (NEW) running 4.1 B6 and tethering with the Wuawei 3372 has been problematic on all devices with most 4.1 beta code. I have tried Slate AX as well. The interface may come up but eventually says no access to internet and does not route packets.
1 Like
Upgraded to 4.1.0 release6 but IPTV with igmproxy+VLC doesnāt work with flint. Occasionally there is some stuttering sound and sometimes even a still image. With Archer C7 and ZyXEL NBG6617 + OpenWRT 22.03.2 I can actually watch TV. After two years ipq6xxx support is still a nightmare. I love my Creta AR750 and I have high expectations for my two Brume2 MT2500 that were handed over to FedEx today.
Can you try this firmware again? Thank.
Hi Jerry, Last time I upgraded a GliNet device with firmware from the forum, it bricked my Flint and I had to acquire a new one. I would like to fix the issue but would prefer to remain in the official beta code land.
We need help to verify if it is compatible with Huawei E3372. If you can help that is great!
But if you donāt want to risk, that is fine.
The appropriate process for loading the firmware appears not to be the āUPGRADEā feature on the UI. Firmware uploads successfully thenā¦ RED WARNING āTesting the firmware with sysupgrade failedā. Point me to the loafing process and I will give it a go.
This guy did it in a Slate AXT1800 ā¦ GL-AXT1800 with e3372h in stick mode. No comgt-ncm package - #16 by JerryZhao ā¦ Iām waiting for my E3372 and for my wife to bring my Router back ā¦ in the meantime flash away 
openwrt-ipq807x-glinet_axt1800-squashfs-sysupgrade loaded on a SLATE AX successfully enables tethering with a Wuawei 3372h. It WORKS!!!.
I am writing this via an āUPGRADEDā SLATE that only has access to the internet via a Wuawei 3372h. If you could port this functionality to FLINT and SLATE AX firmware (and BLUME while you are at it)
1 Like
Awesome; is your E3372h in āHilinkā mode (which I read somewhere has worked before in plain Tethering (vs Modem) mode) or have you flashed it to āStick Modeā (which I understand uses NCM; whatever that is).
btw love the phonetic usage of the W in Wuawei. The real device does start with an H though; unless youāre purposely trying to circumvent some web-crawlers ā¦
The Tethering interface was set as a backup / failover to a primary ethernet link. I am looking to have the flint work a little like the cheap boxes Optus use in Australia to provide NBN access. The NBN presents an ethernet connection in the home and the Optus boxes have a SIM slot for mobile failover. NBN is down frequently and so am I unless I can get the flint to failover to something like a 3372.
The 3372 is āroutingā and presents the 192.168.8.0/24 network to the Slate. I have not played with flashing it
The LOG for the FLINT (still running 4.1b6) is shown below in a more readable format.
The interface comes up but then reports āThe interface is connected, but the Internet canāt be accessed with IPv4 protocolā and does not appear to route packets.
:
Tue Nov 29 18:31:17 2022 daemon.notice netifd: Interface ātetheringā is enabled
Tue Nov 29 18:31:17 2022 daemon.notice netifd: Network device āeth5ā link is up
Tue Nov 29 18:31:17 2022 daemon.notice netifd: Interface ātetheringā has link connectivity
Tue Nov 29 18:31:17 2022 daemon.notice netifd: Interface ātetheringā is setting up now
Tue Nov 29 18:31:17 2022 kern.err kernel: [55858.931034] cdc_ether 1-1:1.0 eth5: kevent 12 may have been dropped
Tue Nov 29 18:31:17 2022 kern.err kernel: [55858.931076] cdc_ether 1-1:1.0 eth5: kevent 12 may have been dropped
Tue Nov 29 18:31:17 2022 daemon.notice netifd: tethering (24604): udhcpc: started, v1.33.2
Tue Nov 29 18:31:17 2022 daemon.notice netifd: tethering (24604): udhcpc: sending discover
Tue Nov 29 18:31:17 2022 daemon.notice netifd: tethering (24604): udhcpc: sending select for 192.168.8.147
Tue Nov 29 18:31:17 2022 daemon.notice netifd: tethering (24604): udhcpc: lease of 192.168.8.147 obtained, lease time 86400
Tue Nov 29 18:31:17 2022 daemon.info avahi-daemon[3901]: Joining mDNS multicast group on interface eth5.IPv4 with address 192.168.8.147.
Tue Nov 29 18:31:17 2022 daemon.info avahi-daemon[3901]: New relevant interface eth5.IPv4 for mDNS.
Tue Nov 29 18:31:17 2022 daemon.info avahi-daemon[3901]: Registering new address record for 192.168.8.147 on eth5.IPv4.
Tue Nov 29 18:31:17 2022 daemon.notice netifd: Interface ātetheringā is now up
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: reading /tmp/resolv.conf.d/resolv.conf.auto
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using only locally-known addresses for domain test
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using only locally-known addresses for domain onion
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using only locally-known addresses for domain localhost
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using only locally-known addresses for domain local
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using only locally-known addresses for domain invalid
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using only locally-known addresses for domain bind
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using only locally-known addresses for domain lan
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using nameserver 198.142.152.164#53
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using nameserver 198.142.152.165#53
Tue Nov 29 18:31:17 2022 daemon.info dnsmasq[7062]: using nameserver 192.168.8.1#53
Tue Nov 29 18:31:17 2022 user.notice mwan3[24624]: Execute ifup event on interface tethering (eth5)
Tue Nov 29 18:31:18 2022 user.notice mwan3[24624]: Starting tracker on interface tethering (eth5)
Tue Nov 29 18:31:18 2022 daemon.info avahi-daemon[3901]: Joining mDNS multicast group on interface eth5.IPv6 with address fe80::21e:10ff:fe1f:0.
Tue Nov 29 18:31:18 2022 daemon.info avahi-daemon[3901]: New relevant interface eth5.IPv6 for mDNS.
Tue Nov 29 18:31:18 2022 daemon.info avahi-daemon[3901]: Registering new address record for fe80::21e:10ff:fe1f:0 on eth5.*.
Tue Nov 29 18:31:20 2022 user.info mwan3rtmon[3816]: Detect rtchange event.
Tue Nov 29 18:31:20 2022 user.notice firewall: Reloading firewall due to ifup of tethering (eth5)