Your 38 (34+4) should be a decently safe start.
As the wiki says, it’s best to err on the larger side.
When you switch to fiber then 42 or 46 should work better.
Are you running cake or fq codel?
Tested with both, performance is similar. Fq_codel is a bit faster than Cake within 5-10%. Cake generally has slightly better bufferbloat control though.
Good result.
do you have docsis and/or ack-filter enabled on cake?
Yes docsis cable. No special filters enabled on cake, just recommended settings for docsis: overhead 42 mpu 84. Packet steering on too of course.
What I'm seeing is ~800-850 with cake, ~850-900 with fq_codel as you can see from my waveform speedtest links above. Also getting 2.5Gbps with HFO. WiFi I get 700-800Mbps on 5G/80MHz width, but I'm throttling that slightly with AQL limits for lower latency.
This is all covered on the doc page for this device. These are fairly typical MT6000 results (and any Filogic 830 I'd assume).
2 Likes
Hello there. Could somebody please help me with understanding OpenWRT log records and fixing them if needed.
|Firmware Version| OpenWrt 24.10.0-rc5
Kernel Version 6.6.69
138 Sat Jan 11 21:38:29 2025 kern warn kernel: [ 1.115854] GPT:Primary header thinks Alt. header is not at the end of the disk.
139 Sat Jan 11 21:38:29 2025 kern warn kernel: [ 1.123396] GPT:1 != 15269887
140 Sat Jan 11 21:38:29 2025 kern warn kernel: [ 1.126351] GPT:Alternate GPT header not at the end of the disk.
141 Sat Jan 11 21:38:29 2025 kern warn kernel: [ 1.132349] GPT:1 != 15269887
142 Sat Jan 11 21:38:29 2025 kern warn kernel: [ 1.135301] GPT: Use GNU Parted to correct GPT errors.
.
.
.
216 Sat Jan 11 21:38:29 2025 kern err kernel: [ 7.635104] xhci-mtk 11200000.usb: ERROR Transfer event for unknown stream ring slot 4 ep 6
217 Sat Jan 11 21:38:29 2025 kern err kernel: [ 7.643433] xhci-mtk 11200000.usb: @0000000041014020 44716100 00000000 1a00000a 04078000
.
.
.
218 Sat Jan 11 21:38:29 2025 user info kernel: [ 7.683728] block: attempting to load /tmp/overlay/upper/etc/config/fstab
219 Sat Jan 11 21:38:29 2025 user info kernel: [ 7.691177] block: extroot: not configured
220 Sat Jan 11 21:38:29 2025 user info kernel: [ 7.695411] block: attempting to load /etc/config/fstab
221 Sat Jan 11 21:38:29 2025 user err kernel: [ 7.700699] block: unable to load configuration (fstab: Entry not found)
222 Sat Jan 11 21:38:29 2025 user err kernel: [ 7.707404] block: no usable configuration
223 Sat Jan 11 21:38:29 2025 user info kernel: [ 7.712525] mount_root: switching to f2fs overlay
224 Sat Jan 11 21:38:29 2025 kern warn kernel: [ 7.717938] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
225 Sat Jan 11 21:38:29 2025 user debug kernel: [ 7.729337] urandom-seed: Seeding with /etc/urandom.seed
226 Sat Jan 11 21:38:29 2025 kern info kernel: [ 7.770370] sd 1:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
227 Sat Jan 11 21:38:29 2025 kern warn kernel: [ 7.776651] sd 1:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
.
.
.
496 Sat Jan 11 21:38:36 2025 daemon err odhcp6c[5555]: Failed to send RS (Address not available)
.
.
.
848 Sat Jan 11 21:39:44 2025 daemon err collectd[3459]: Sleeping only 2s because the next interval is 11.070 seconds in the past!
.
.
.
889 Sat Jan 11 21:40:17 2025 daemon notice hostapd: phy1-ap0: DFS-CAC-COMPLETED success=1 freq=5180 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5250 cf2=0 radar_detected=0
890 Sat Jan 11 21:40:17 2025 daemon warn hostapd: Can't set DFS state for freq 5180 MHz
891 Sat Jan 11 21:40:17 2025 daemon warn hostapd: Can't set DFS state for freq 5200 MHz
892 Sat Jan 11 21:40:17 2025 daemon warn hostapd: Can't set DFS state for freq 5220 MHz
893 Sat Jan 11 21:40:17 2025 daemon warn hostapd: Can't set DFS state for freq 5240 MHz
894 Sat Jan 11 21:40:17 2025 kern info kernel: [ 80.145125] br-lan: port 6(phy1-ap0) entered blocking state
895 Sat Jan 11 21:40:17 2025 kern info kernel: [ 80.150789] br-lan: port 6(phy1-ap0) entered listening state
896 Sat Jan 11 21:40:17 2025 daemon notice netifd: Network device 'phy1-ap0' link is up
897 Sat Jan 11 21:40:17 2025 daemon notice hostapd: phy1-ap0: interface state DFS->ENABLED
898 Sat Jan 11 21:40:17 2025 daemon notice hostapd: phy1-ap0: AP-ENABLED
899 Sat Jan 11 21:40:26 2025 kern info kernel: [ 88.781050] br-lan: port 6(phy1-ap0) entered learning state
900 Sat Jan 11 21:40:34 2025 kern info kernel: [ 97.097959] br-lan: port 6(phy1-ap0) entered forwarding state
901 Sat Jan 11 21:40:34 2025 kern info kernel: [ 97.103738] br-lan: topology change detected, propagating
.
.
.
1081 Sat Jan 11 21:52:15 2025 daemon err procd: Got unexpected signal 1
.
.
.
1340 Sat Jan 11 22:56:29 2025 daemon err modprobe: failed to find a module named aufs
I sysupgraded yesterday from snapshotr 26329-cffd3ad8d7 to 24.10-rc5. I selected to keep configuration and keep packages... and nothing worked (could not connect to wireless but could connect using lan cable, wan connection did not work at all even though dhcp got an IP from the gateway...) until I reset configuration. afterwards everything seems to work fine.
For some reason, wan interface still always shows as down in luci overview even though it works well:
I also setup SQM and bufferbloat over wireless improved from D to A!
does name resulution work?
yes, everything works properly. wireless clients get internet access correctly. the DNS shown are taken from the wan gateway when openwrt gets its dhcp address for the wan interface.
the data counters under the interface icon also get updated as data flows.
i guess it wasent wery clear, did you try from the openwrt router or just the clients?
ping google.com
both work correctly
I just got this router for my parents and configured it remotely on the weekend. Fantastic unit! That 8 GB eMMC is really nice. Hats off to the developers too, everything works smoothly 
I have APU2 with custom build myself but GL-MT6000 seems like a solid device. Plenty of power for two people 
Edit. Oh, I forgot. Hello to you all, haha. I've been lurking here few weeks now.
3 Likes
I noticed that visual bug on eth1 too, although the link works without issue. Just post that in the rc5 thread not this one.
1 Like
I don't think it shows as down? It looks the same in 23.05, and says it has 1 GbE link?
If you mean the colour that is the colour of wan on the interface tab. Presumably with guest/IOT networks of different colours they would also show up here.
1 Like
Ah that clears it up for me too, I thought it was colored wrong.
How did you format it?
It just refers to the default interface colour where lan is always green and wan is red. Presumably to let you know wan is firewalled by default. If you changed wan to say blue then the red line would switch to blue: Interface color
Would be nice if we could set the colours within Luci. In my case one lan interface has almost the same colour as my Wireguard interface and looks a bit odd imho.
I just flashed 24.10.0-rc5 sysupgrade as it is. /rom has 7.2 GB, I think. Is there a different layout for partitioning that's recommended? Though, a separate partition for docker would be good if I end up installing it in the future. I've only tinkered with x86 devices in recent years. I'm not that familiar with overlayfs etc.
Wondering if anyone is seeing what's listed below in your MT6000 logs? It looks to me like recent "upgrade" to hostapd sometime in Sep 2024 may have introduced quite a few bugs?
Client roamed from 5GHz to 2.4GHz network, and logs shows client disconnected from 5GHz interface, but hostapd still sending management frame to disconnected client.
Thu Jan 16 23:34:05 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 2)
Thu Jan 16 23:34:05 2025 daemon.notice hostapd: phy1-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 16 23:34:05 2025 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 16 23:34:07 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=sae
Thu Jan 16 23:34:07 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 16 23:34:07 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 16 23:34:35 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 16 23:38:50 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 2)
Thu Jan 16 23:38:50 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 16 23:38:50 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 16 23:38:50 2025 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=sae
Thu Jan 16 23:38:50 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 16 23:38:50 2025 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 16 23:39:20 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 16 23:39:55 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Thu Jan 16 23:39:55 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 2)
Thu Jan 16 23:39:55 2025 daemon.notice hostapd: phy1-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 16 23:39:55 2025 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 16 23:39:57 2025 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=open
Thu Jan 16 23:39:57 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 16 23:39:57 2025 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 16 23:40:25 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jan 16 23:44:40 2025 daemon.notice hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: did not acknowledge authentication response
Thu Jan 16 23:44:40 2025 daemon.notice hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: did not acknowledge authentication response
Thu Jan 16 23:44:40 2025 daemon.notice hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: did not acknowledge authentication response
Thu Jan 16 23:44:40 2025 daemon.notice hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: did not acknowledge authentication response
Thu Jan 16 23:44:41 2025 daemon.notice hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: did not acknowledge authentication response
Thu Jan 16 23:44:42 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 2)
Thu Jan 16 23:44:42 2025 daemon.notice hostapd: phy0-ap0: Prune association for xx:xx:xx:xx:xx:xx
Thu Jan 16 23:44:42 2025 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Thu Jan 16 23:44:42 2025 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx auth_alg=sae
Thu Jan 16 23:44:42 2025 daemon.info hostapd: phy1-ap0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Thu Jan 16 23:44:42 2025 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED xx:xx:xx:xx:xx:xx
Thu Jan 16 23:45:12 2025 daemon.info hostapd: phy0-ap0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)