HI there,
thanks for the reply, muchly appreciated!
So I copied the link location for the //next-r4.6.21.rss.mtk, and used this Github downloader: Github downloader to get the files, which amounted to a zip file of approx 85mb.
After resetting to defaults and selecting the file i get this.
Is this right or wrong?
Is this the usual warning?!
If yes, which options should I tick/untick?
Thanks again.
Just download the sysupgrade file alone.
https://github.com/pesa1234/MT6000_cust_build/raw/refs/heads/main/2025-11-16_r32593-3500ccc9f3_next-r4.6.21.rss.mtk/targets/mediatek/filogic/openwrt-snapshot-r32593-3500ccc9f3-mediatek-filogic-glinet_gl-mt6000-squashfs-sysupgrade.bin
Right!
I spent about an hour looking for a sysupgrade file!
Just cail me dangerous
as in a little knowledge…!
Thanks again!!
The file names and paths are far too long to be readable on GitHub.
I’m actually facing the same issue in my ARM64 Ubuntu container in Oracle Cloud that I just spun up. My local ARM64 Debian install has no issues compiling, so I’m wondering whether Ubuntu is causing something to happen during the build..
Dear all, latest stable is 4.6.22.rss.mtk
4.7.x will be beta to check new mac80211 6.18.
Edit...
4.7.beta0 is working on my side, so if someone want to compile and test is working (it boot) 
4.7 beta compiles and booted on two devices. No errors so far. Wireless is working normally. Only difference so far is the extra information in the ipv6 network section of overview. That may be related to an update in Luci.
Update. Running without any errors in the log for 2 days.
Hi @pesa1234 ,
using your last 4.7 beta HEAD (61bc0d71848e3c9e03de1cf4e45623ad27d0a776) the nft fw4 chain is not created:
root@OpenWrt:~# nft list tables
table inet banIP
root@OpenWrt:~#
My .config has the Firewall4 enabled of course.
ciao
luigi
PS: From my last working .config I switched to tc-full instead tc-tiny.
Has anyone been seeing recent issues with wireless link degradation/instability? In my case, it presents itself regularly for several minutes at a time. The experience from a client device (STA) perspective is dropped packets and resulting latency spikes. It's quite impactful, really.
❯ ping -S 192.168.66.100 --apple-time -i0.3 192.168.66.1
PING 192.168.66.1 (192.168.66.1) from 192.168.66.100: 56 data bytes
09:22:00.226298 64 bytes from 192.168.66.1: icmp_seq=0 ttl=64 time=131.227 ms
09:22:00.489456 64 bytes from 192.168.66.1: icmp_seq=1 ttl=64 time=89.460 ms
09:22:01.007499 Request timeout for icmp_seq 2
09:22:01.017721 64 bytes from 192.168.66.1: icmp_seq=2 ttl=64 time=315.297 ms
09:22:01.349118 64 bytes from 192.168.66.1: icmp_seq=3 ttl=64 time=341.769 ms
09:22:01.920623 Request timeout for icmp_seq 5
09:22:01.932132 64 bytes from 192.168.66.1: icmp_seq=4 ttl=64 time=622.275 ms
09:22:01.932162 64 bytes from 192.168.66.1: icmp_seq=5 ttl=64 time=316.998 ms
09:22:01.932168 64 bytes from 192.168.66.1: icmp_seq=6 ttl=64 time=11.755 ms
09:22:03.135623 Request timeout for icmp_seq 9
09:22:03.386727 64 bytes from 192.168.66.1: icmp_seq=7 ttl=64 time=1161.176 ms
09:22:03.386974 64 bytes from 192.168.66.1: icmp_seq=8 ttl=64 time=859.972 ms
09:22:03.387012 64 bytes from 192.168.66.1: icmp_seq=9 ttl=64 time=556.816 ms
09:22:03.387031 64 bytes from 192.168.66.1: icmp_seq=10 ttl=64 time=251.507 ms
09:22:04.661920 Request timeout for icmp_seq 14
09:22:04.966733 Request timeout for icmp_seq 15
09:22:05.234744 64 bytes from 192.168.66.1: icmp_seq=11 ttl=64 time=1793.339 ms
09:22:05.235315 64 bytes from 192.168.66.1: icmp_seq=12 ttl=64 time=1488.472 ms
09:22:05.235746 64 bytes from 192.168.66.1: icmp_seq=13 ttl=64 time=1183.254 ms
09:22:05.235978 64 bytes from 192.168.66.1: icmp_seq=14 ttl=64 time=878.044 ms
09:22:05.236211 64 bytes from 192.168.66.1: icmp_seq=15 ttl=64 time=572.895 ms
09:22:05.236270 64 bytes from 192.168.66.1: icmp_seq=16 ttl=64 time=268.209 ms
09:22:05.389158 64 bytes from 192.168.66.1: icmp_seq=17 ttl=64 time=118.660 ms
09:22:06.301195 64 bytes from 192.168.66.1: icmp_seq=18 ttl=64 time=726.728 ms
09:22:06.301240 64 bytes from 192.168.66.1: icmp_seq=19 ttl=64 time=421.628 ms
09:22:06.301251 64 bytes from 192.168.66.1: icmp_seq=20 ttl=64 time=116.503 ms
09:22:06.525123 64 bytes from 192.168.66.1: icmp_seq=21 ttl=64 time=38.735 ms
09:22:07.257298 64 bytes from 192.168.66.1: icmp_seq=22 ttl=64 time=466.317 ms
09:22:07.257350 64 bytes from 192.168.66.1: icmp_seq=23 ttl=64 time=163.875 ms
09:22:07.849097 64 bytes from 192.168.66.1: icmp_seq=24 ttl=64 time=446.604 ms
09:22:07.849143 64 bytes from 192.168.66.1: icmp_seq=25 ttl=64 time=141.455 ms
09:22:08.013812 64 bytes from 192.168.66.1: icmp_seq=26 ttl=64 time=6.581 ms
09:22:08.352491 64 bytes from 192.168.66.1: icmp_seq=27 ttl=64 time=35.548 ms
09:22:08.810551 64 bytes from 192.168.66.1: icmp_seq=28 ttl=64 time=188.702 ms
09:22:09.058890 64 bytes from 192.168.66.1: icmp_seq=29 ttl=64 time=135.981 ms
09:22:09.265284 64 bytes from 192.168.66.1: icmp_seq=30 ttl=64 time=38.017 ms
09:22:09.606714 64 bytes from 192.168.66.1: icmp_seq=31 ttl=64 time=75.852 ms
09:22:09.939108 64 bytes from 192.168.66.1: icmp_seq=32 ttl=64 time=103.152 ms
09:22:10.163481 64 bytes from 192.168.66.1: icmp_seq=33 ttl=64 time=25.663 ms
09:22:10.598951 64 bytes from 192.168.66.1: icmp_seq=34 ttl=64 time=155.884 ms
09:22:10.768807 64 bytes from 192.168.66.1: icmp_seq=35 ttl=64 time=20.428 ms
09:22:11.067578 64 bytes from 192.168.66.1: icmp_seq=36 ttl=64 time=14.133 ms
09:22:11.441900 64 bytes from 192.168.66.1: icmp_seq=37 ttl=64 time=83.271 ms
09:22:11.978813 64 bytes from 192.168.66.1: icmp_seq=38 ttl=64 time=314.980 ms
09:22:12.024739 64 bytes from 192.168.66.1: icmp_seq=39 ttl=64 time=55.763 ms
09:22:12.358714 64 bytes from 192.168.66.1: icmp_seq=40 ttl=64 time=84.609 ms
09:22:12.591745 64 bytes from 192.168.66.1: icmp_seq=41 ttl=64 time=15.308 ms
09:22:12.899667 64 bytes from 192.168.66.1: icmp_seq=42 ttl=64 time=15.680 ms
09:22:13.207618 64 bytes from 192.168.66.1: icmp_seq=43 ttl=64 time=21.033 ms
09:22:13.507885 64 bytes from 192.168.66.1: icmp_seq=44 ttl=64 time=16.031 ms
09:22:13.813300 64 bytes from 192.168.66.1: icmp_seq=45 ttl=64 time=16.132 ms
09:22:14.198959 64 bytes from 192.168.66.1: icmp_seq=46 ttl=64 time=96.444 ms
09:22:14.428684 64 bytes from 192.168.66.1: icmp_seq=47 ttl=64 time=23.663 ms
09:22:15.073803 64 bytes from 192.168.66.1: icmp_seq=48 ttl=64 time=363.885 ms
09:22:15.073824 64 bytes from 192.168.66.1: icmp_seq=49 ttl=64 time=59.673 ms
09:22:15.353040 64 bytes from 192.168.66.1: icmp_seq=50 ttl=64 time=33.749 ms
09:22:15.681044 64 bytes from 192.168.66.1: icmp_seq=51 ttl=64 time=56.405 ms
09:22:16.184903 64 bytes from 192.168.66.1: icmp_seq=52 ttl=64 time=255.023 ms
09:22:16.253102 64 bytes from 192.168.66.1: icmp_seq=53 ttl=64 time=18.260 ms
09:22:16.614055 64 bytes from 192.168.66.1: icmp_seq=54 ttl=64 time=77.865 ms
09:22:16.881901 64 bytes from 192.168.66.1: icmp_seq=55 ttl=64 time=40.495 ms
09:22:17.191748 64 bytes from 192.168.66.1: icmp_seq=56 ttl=64 time=45.002 ms
09:22:17.462854 64 bytes from 192.168.66.1: icmp_seq=57 ttl=64 time=15.884 ms
09:22:17.782188 64 bytes from 192.168.66.1: icmp_seq=58 ttl=64 time=31.476 ms
09:22:18.072574 64 bytes from 192.168.66.1: icmp_seq=59 ttl=64 time=16.491 ms
09:22:18.370586 64 bytes from 192.168.66.1: icmp_seq=60 ttl=64 time=9.821 ms
09:22:18.950501 64 bytes from 192.168.66.1: icmp_seq=61 ttl=64 time=284.631 ms
09:22:19.030469 64 bytes from 192.168.66.1: icmp_seq=62 ttl=64 time=60.622 ms
09:22:19.377957 64 bytes from 192.168.66.1: icmp_seq=63 ttl=64 time=102.817 ms
09:22:19.774317 64 bytes from 192.168.66.1: icmp_seq=64 ttl=64 time=193.918 ms
09:22:20.079066 64 bytes from 192.168.66.1: icmp_seq=65 ttl=64 time=196.224 ms
09:22:20.223937 64 bytes from 192.168.66.1: icmp_seq=66 ttl=64 time=35.874 ms
09:22:21.021728 64 bytes from 192.168.66.1: icmp_seq=67 ttl=64 time=528.149 ms
09:22:21.021810 64 bytes from 192.168.66.1: icmp_seq=68 ttl=64 time=227.697 ms
09:22:21.213152 64 bytes from 192.168.66.1: icmp_seq=69 ttl=64 time=117.261 ms
09:22:21.519085 64 bytes from 192.168.66.1: icmp_seq=70 ttl=64 time=118.130 ms
^C
--- 192.168.66.1 ping statistics ---
73 packets transmitted, 71 packets received, 2.7% packet loss
round-trip min/avg/max/stddev = 6.581/252.326/1793.339/352.982 ms
I'm running an r4.6.22.rss.mtk build. I've been chasing this for a few weeks and only resorted to bugging anybody here as a last stop. I don't want to cause undue noise if no-one else is experiencing this, but it would help me greatly to know if I'm chasing something unique to my setup/environment or not. No single STA is affected in my case, and it's not just a particular device type or OS. It seems indiscriminate in that sense.
If no one else is having this issue with recent builds, then I will know to continue focusing on specifics in my environment. Thanks!
I am running 4.6.21 as a dumb AP and haven’t observed any wireless instability.
I'm on 4.7 for testing but on previous releases I didn't get issues. So let's wait other feedback... But if no one says anything or nobody use or no issue...
Do you get also on snapshot, sorry for stupid question.
That's a fair question--not stupid at all! Let me roll an image straight off of snapshot and confirm if I see the behavior there as well. Will update this post later with results. Thanks!
So far I haven't experienced this. Currently using build based on r4.6.22.rss.mtk (with HEAD f383a48d36b6852f86e4e723b3524c40aa60b9ec)
Run PING to router for few mins (using iphone - network utility app).. no packet loss detected
@customcard @pesa1234 @AcidSlide Thank you all for your inputs and confirmation. This is also occurring on snapshot for me, so I'll continue to presume it's something unique to my environment and keep digging in from that angle. No need to continue pulling this thread sideways with my issue. Thanks!
it seems a bug from pbr package (policy based routing)
root@OpenWrt:/usr/share/nftables.d# fw4 reload
Section @defaults[0] specifies unknown option 'offload_delay'
Section @defaults[0] specifies unknown option 'ofd_packets'
Section @defaults[0] specifies unknown option 'ofd_proto'
Section @rule[13] (Allow-HTTP) is disabled, ignoring section
Section @redirect[0] (Plex) is disabled, ignoring section
Section @redirect[1] (gentoobx-443) is disabled, ignoring section
Section @redirect[2] (gentoobx-80) is disabled, ignoring section
Section @redirect[4] (DNS Intercept) does not specify a destination, assuming 'lan'
Section @redirect[5] (wgsrv) is disabled, ignoring section
Section pbr specifies unreachable path '/usr/share/pbr/firewall.include', ignoring section
Automatically including '/usr/share/nftables.d/table-post/20-miniupnpd.nft'
Automatically including '/usr/share/nftables.d/table-post/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-pre/dstnat/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/dstnat/20-miniupnpd.nft'
Automatically including '/usr/share/nftables.d/chain-post/forward/20-miniupnpd.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_forward/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_input/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_output/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_postrouting/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_prerouting/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/srcnat/20-miniupnpd.nft'
In file included from /dev/stdin:354:3-75:
/usr/share/nftables.d/chain-post/mangle_postrouting/30-pbr.nft:1:6-20: Error: Could not process rule: No such file or directory
jump pbr_postrouting comment "Jump into pbr postrouting chain";
^^^^^^^^^^^^^^^
In file included from /dev/stdin:359:3-69:
/usr/share/nftables.d/chain-post/mangle_input/30-pbr.nft:1:6-14: Error: No such file or directory; did you mean chain 'wan-input' in table inet 'banIP'?
jump pbr_input comment "Jump into pbr input chain";
^^^^^^^^^
root@OpenWrt:/usr/share/nftables.d# mv chain-post/mangle_postrouting/30-pbr.nft chain-post/mangle_postrouting/30-pbr.nft.disabled
root@OpenWrt:/usr/share/nftables.d# fw4 reload
Section @defaults[0] specifies unknown option 'offload_delay'
Section @defaults[0] specifies unknown option 'ofd_packets'
Section @defaults[0] specifies unknown option 'ofd_proto'
Section @rule[13] (Allow-HTTP) is disabled, ignoring section
Section @redirect[0] (Plex) is disabled, ignoring section
Section @redirect[1] (gentoobx-443) is disabled, ignoring section
Section @redirect[2] (gentoobx-80) is disabled, ignoring section
Section @redirect[4] (DNS Intercept) does not specify a destination, assuming 'lan'
Section @redirect[5] (wgsrv) is disabled, ignoring section
Section pbr specifies unreachable path '/usr/share/pbr/firewall.include', ignoring section
Automatically including '/usr/share/nftables.d/table-post/20-miniupnpd.nft'
Automatically including '/usr/share/nftables.d/table-post/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-pre/dstnat/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/dstnat/20-miniupnpd.nft'
Automatically including '/usr/share/nftables.d/chain-post/forward/20-miniupnpd.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_forward/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_input/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_output/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_prerouting/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/srcnat/20-miniupnpd.nft'
In file included from /dev/stdin:358:3-69:
/usr/share/nftables.d/chain-post/mangle_input/30-pbr.nft:1:6-14: Error: No such file or directory; did you mean chain 'wan-input' in table inet 'banIP'?
jump pbr_input comment "Jump into pbr input chain";
^^^^^^^^^
root@OpenWrt:/usr/share/nftables.d# mv chain-post/mangle_input/30-pbr.nft chain-post/mangle_input/30-pbr.nft.disabled
root@OpenWrt:/usr/share/nftables.d# fw4 reload
Section @defaults[0] specifies unknown option 'offload_delay'
Section @defaults[0] specifies unknown option 'ofd_packets'
Section @defaults[0] specifies unknown option 'ofd_proto'
Section @rule[13] (Allow-HTTP) is disabled, ignoring section
Section @redirect[0] (Plex) is disabled, ignoring section
Section @redirect[1] (gentoobx-443) is disabled, ignoring section
Section @redirect[2] (gentoobx-80) is disabled, ignoring section
Section @redirect[4] (DNS Intercept) does not specify a destination, assuming 'lan'
Section @redirect[5] (wgsrv) is disabled, ignoring section
Section pbr specifies unreachable path '/usr/share/pbr/firewall.include', ignoring section
Automatically including '/usr/share/nftables.d/table-post/20-miniupnpd.nft'
Automatically including '/usr/share/nftables.d/table-post/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-pre/dstnat/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/dstnat/20-miniupnpd.nft'
Automatically including '/usr/share/nftables.d/chain-post/forward/20-miniupnpd.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_forward/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_output/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_prerouting/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/srcnat/20-miniupnpd.nft'
root@OpenWrt:/usr/share/nftables.d# nft list tables
table inet banIP
table inet fw4
What build are you using? tried it on mine no errors.. i'm using PBR also
Custom build based on r4.6.22.rss.mtk (with HEAD f383a48d36b6852f86e4e723b3524c40aa60b9ec).
PBR version is pbr-1.2.1-r31.
# fw4 reload
Section @rule[10] (Ban-WARP-App-Ports) is disabled, ignoring section
Section @rule[11] (Ban-QUIC-UDP) is disabled, ignoring section
Section samba_nsds_nt (NoTrack-Samba/NS/DS) is disabled, ignoring section
Section samba_ss_nt (NoTrack-Samba/SS) is disabled, ignoring section
Section samba_smb_nt (NoTrack-Samba/SMB) is disabled, ignoring section
Section @redirect[1] (AcidSlideTrashWinDev80) is disabled, ignoring section
Section @redirect[2] (AcidSlideTrashWinDev80) is disabled, ignoring section
Section pbr specifies unreachable path '/usr/share/pbr/firewall.include', ignoring section
Automatically including '/usr/share/nftables.d/ruleset-post/30-pbr.nft'
Automatically including '/usr/share/nftables.d/table-post/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-pre/dstnat/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_forward/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_output/30-pbr.nft'
Automatically including '/usr/share/nftables.d/chain-post/mangle_prerouting/30-pbr.nft'
4.7.beta0 61bc0d71848e3c9e03de1cf4e45623ad27d0a776
ciao
luigi
pbr 2.1 removed these chains:
We can remove safely from our filesystem.
(I don’t know why these files are still on my filesystem)
Additional note, the /etc/init.d/pbr script has a missing space at 1278 line.
See https://github.com/stangri/pbr/commit/2e5f789f86cf6b0d00dd6baf01b3d1d18ee21d8d
ciao
luigi
Better check with Stangri for the PBR issues or file a an issue in his github
Already reported to pbr forum page