Flint firmware 4.1.0 release6 is out

Flint Tethering with Huawei 3372 almost works. Connects or appears to sometimes but won’t route packets. Log here:

Mon Nov 28 20:41:44 2022 daemon.notice netifd: tethering (3953): udhcpc: received SIGTERM Mon Nov 28 20:41:44 2022 daemon.notice netifd: tethering (3953): udhcpc: unicasting a release of 192.168.8.144 to 192.168.8.1 Mon Nov 28 20:41:44 2022 daemon.notice netifd: tethering (3953): udhcpc: sending release Mon Nov 28 20:41:44 2022 daemon.notice netifd: tethering (3953): udhcpc: entering released state Mon Nov 28 20:41:44 2022 daemon.notice netifd: tethering (3953): Command failed: Permission denied Mon Nov 28 20:41:44 2022 daemon.notice netifd: Interface ‘tethering’ is now down Mon Nov 28 20:41:44 2022 daemon.info avahi-daemon[3911]: Withdrawing address record for 192.168.8.144 on eth5. Mon Nov 28 20:41:44 2022 daemon.info avahi-daemon[3911]: Leaving mDNS multicast group on interface eth5.IPv4 with address 192.168.8.144. Mon Nov 28 20:41:44 2022 daemon.notice netifd: Interface ‘tethering’ is disabled Mon Nov 28 20:41:44 2022 daemon.info avahi-daemon[3911]: Interface eth5.IPv4 no longer relevant for mDNS. Mon Nov 28 20:41:44 2022 daemon.notice netifd: Interface ‘tethering’ has link connectivity loss Mon Nov 28 20:41:44 2022 daemon.info avahi-daemon[3911]: Interface eth5.IPv6 no longer relevant for mDNS. Mon Nov 28 20:41:44 2022 daemon.info avahi-daemon[3911]: Leaving mDNS multicast group on interface eth5.IPv6 with address fe80::21e:10ff:fe1f:0. Mon Nov 28 20:41:44 2022 daemon.info avahi-daemon[3911]: Withdrawing address record for fe80::21e:10ff:fe1f:0 on eth5. Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: reading /tmp/resolv.conf.d/resolv.conf.auto Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain test Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain onion Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain localhost Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain local Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain invalid Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain bind Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain lan Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: using nameserver 198.142.152.164#53 Mon Nov 28 20:41:44 2022 daemon.info dnsmasq[7102]: using nameserver 198.142.152.165#53 Mon Nov 28 20:41:44 2022 user.notice mwan3[21259]: Execute ifdown event on interface tethering (unknown) Mon Nov 28 20:41:45 2022 user.info mwan3track[8198]: Detect ifdown event on interface tethering (eth5) Mon Nov 28 20:41:45 2022 user.notice mwan3track[8198]: Stopping mwan3track for interface “tethering” Mon Nov 28 20:41:51 2022 kern.err kernel: [63692.978993] cdc_ether 1-1:1.0 eth5: kevent 12 may have been dropped Mon Nov 28 20:41:51 2022 kern.err kernel: [63692.979073] cdc_ether 1-1:1.0 eth5: kevent 12 may have been dropped Mon Nov 28 20:41:51 2022 kern.err kernel: [63692.984110] cdc_ether 1-1:1.0 eth5: kevent 12 may have been dropped Mon Nov 28 20:41:51 2022 daemon.notice netifd: Interface ‘tethering’ is enabled Mon Nov 28 20:41:51 2022 daemon.notice netifd: Network device ‘eth5’ link is up Mon Nov 28 20:41:51 2022 daemon.notice netifd: Interface ‘tethering’ has link connectivity Mon Nov 28 20:41:51 2022 daemon.notice netifd: Interface ‘tethering’ is setting up now Mon Nov 28 20:41:51 2022 daemon.notice netifd: tethering (22175): udhcpc: started, v1.33.2 Mon Nov 28 20:41:51 2022 daemon.notice netifd: tethering (22175): udhcpc: sending discover Mon Nov 28 20:41:51 2022 daemon.notice netifd: tethering (22175): udhcpc: sending select for 192.168.8.145 Mon Nov 28 20:41:51 2022 daemon.notice netifd: tethering (22175): udhcpc: lease of 192.168.8.145 obtained, lease time 86400 Mon Nov 28 20:41:51 2022 daemon.info avahi-daemon[3911]: Joining mDNS multicast group on interface eth5.IPv4 with address 192.168.8.145. Mon Nov 28 20:41:51 2022 daemon.info avahi-daemon[3911]: New relevant interface eth5.IPv4 for mDNS. Mon Nov 28 20:41:51 2022 daemon.info avahi-daemon[3911]: Registering new address record for 192.168.8.145 on eth5.IPv4. Mon Nov 28 20:41:51 2022 daemon.notice netifd: Interface ‘tethering’ is now up Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: reading /tmp/resolv.conf.d/resolv.conf.auto Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain test Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain onion Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain localhost Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain local Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain invalid Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain bind Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using only locally-known addresses for domain lan Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using nameserver 198.142.152.164#53 Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using nameserver 198.142.152.165#53 Mon Nov 28 20:41:51 2022 daemon.info dnsmasq[7102]: using nameserver 192.168.8.1#53 Mon Nov 28 20:41:52 2022 user.notice mwan3[22226]: Execute ifup event on interface tethering (eth5) Mon Nov 28 20:41:52 2022 daemon.info avahi-daemon[3911]: Joining mDNS multicast group on interface eth5.IPv6 with address fe80::21e:10ff:fe1f:0. Mon Nov 28 20:41:52 2022 daemon.info avahi-daemon[3911]: New relevant interface eth5.IPv6 for mDNS. Mon Nov 28 20:41:52 2022 daemon.info avahi-daemon[3911]: Registering new address record for fe80::21e:10ff:fe1f:0 on eth5.*. Mon Nov 28 20:41:52 2022 user.notice mwan3[22226]: Starting tracker on interface tethering (eth5) Mon Nov 28 20:41:54 2022 user.info mwan3rtmon[3799]: Detect rtchange event. Mon Nov 28 20:41:55 2022 user.notice firewall: Reloading firewall due to ifup of tethering (eth5) Mon Nov 28 20:42:01 2022 daemon.warn dnsmasq[7102]: nameserver 198.142.152.165 refused to do a recursive query Mon Nov 28 20:42:11 2022 daemon.warn dnsmasq[7102]: nameserver 192.168.8.1 refused to do a recursive query

Copyright © 2022 GL.iNet. All Rights Reserved

That is unfortunate that it does not work, but you don’t need to show your displeasure by posting the log in the most obnoxious way possible( I know you just copied and pasted, maybe use notepad or wordpad next time or download the log). It makes it really difficult to follow the timeline

Is there something else to it like a vpn running or adguardhome. It seems that its having a issue with ipv4 switching to ipv6.

mwan3 also seems to be doing something, is it set-up to load-balance or for fail-over?

1 Like

Anyone know if it’s normal for upgrading via Local Upgrade? I don’t see a new version under “Online Upgrade” So I downloaded the .img from the Download Centre

I got an error where the Version Number is unknown…

.img is meant for Uboot .tar is for local upgrade

When I use .tar, it throws error
“ERROR: Incorrect firmware format!”

I see you are talking to cafebug to.

The latest stable firmware for version 3.x is 3.214 this was based on chaos calmer 15.05 a deprecated version of openwrt

4.x is the newest firmware and GL.iNet User Interface is based on openwrt 21.02 and LuCi 22.03

You will need to use uboot to upgrade past 3.214 to 4.10.0

Also will want to update uboot before

hansome

Oct 20

That’s a uboot bug, the fixed version can be downloaded here .
Upgrade uboot by the following steps:

  1. connect LAN and PC by ethernet, the PC’s ip should be 192.168.1.x
  2. push the reset button and power it on, about 10 seconds later release the button, until the wifi led stops flashing and the white led turns on.
  3. access http://192.168.1.1/uboot.html to flash uboot.

Thanks a lot. I guess I’ll just hang on 3.214 until I have the motivation to reconfigure my router, haha :joy:

Thanks~~

So you can save a config file in LuCi upgrade to 4.x install the SQM package in LuCi and then load the Config file. It seems to have worked with no issue. The key is installing the sqm package becuase it writes a rudimentary ipv4 to ipv6 iptable NFtable swap.

1 Like

You could also install iptables-nft (assuming that’s in the gli repo) which does a full translation between iptables and nftables. This is the easiest way to get various non-nftables aware software working right now.

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-sqm and sqm-scripts installed 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/config and 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.