QUOTE(kwss @ Aug 27 2025, 02:17 PM)
If the NIC only have one hardware queue, the number of threads won't really improve things that much. The reason is only 1 CPU core will receive hardware interrupt. There's a reason why Mellanox NIC cost so much.
Try different Coalesce setting? Most consumer hardware need this setting to not wreck your CPU.
Well, MTK one don't have such configuration, lol.
Just having quick check on NDIS version, this MTK even using 6.70 while the Realtek LAN driver is using latest 6.89, which is released for 24H2, lol.
So I guess MTK don't really put his mind on optimizing the performance of this chipset then, and my best choice is pull a cable if upgraded to 500M, or Intel BE200 etc.
For the WiFi >75%, just ignore the receive speed as it is power saving now.
» Click to show Spoiler - click again to hide... «
So as you can see, when it is 76%, you will get fake speed, so I don't think MTK really like to doing good thing on this WiFi Chipset...
QUOTE(coolguy_0925 @ Aug 27 2025, 09:20 PM)
Good that it is auto
I am 500M and still public ip as of now (someone's favourite 175.xxx.xxx.xxx)
Since you came from private to public, did you feel any improvement? (since someone kept preaching public ip is b
atter and low ping)

What, me?
There is a lot of 175.x.x.x, some already get corrupted by those DDoS/burst force kids, so had to jump ship liao.
Else, my family keep blame me why take 30 mins to reconnect the internet, I had such bad luck keep kicking/sharing the CGNAT IP with those script kiddie.

There is some early period of CGNAT issues, like during opening lowyat, it will reset connection as out of port etc, guess they solved it by reducing the sharing of same IP address, or because it is IPv6 generation.
This post has been edited by BenYeeHua: Aug 28 2025, 10:26 AM