hi, @ACwifidude can You add support for Trendnet TEW-827DRU v1.0R for You custom image? Thanks
Is it supported by 21.02? If you can help me get the right .dts settings we could always give it a try.
@xeonpj haven’t noticed any lag with wired connections. Try setting it to a static IP and see if that helps. I’ve had devices go bad before and perform weirdly with DHCP but still work fine with static.
Use static IP.
On oem's or voxtel's firmware . Connection laptop (wifi intel ax200 160Mhz) <-> r7800 <-> (ethernet) NAS allows you to get 940 Mbit/s in both directions. This isn't the limit.
When I used the wan port as the second interface to the local network, I got 1.3 Gbps (I downloaded the file from nas to smb3 share).
For the r7800, the speed of a large gigabit over wifi is a normal situation.
When I installed the stock openwrt 21.02.1 with the Ath10k-ct driver, I got 400 Mbps (in) and 600Mbps (out). With the Ath10k driver, the speeds are lower.
With your build (Ath10k-ct + OpenWrt 21.02 (Stable) + NSS Hardware Offloading). I got 637 Mbps (int) and 940 Mbps (out) . With driver Ath10k, the speed in both directions drops by about 1.5 times.
Is it possible to get speeds comparable to oem / voxel firmware? Or near gigabit to receive?
It's not even supported in OpenWrt
not officialy, take a look here Unofficial TRENDnet AC2600 (TEW-827DRU v1.0R)
Speeds look right. Wish our expert developers had access to all the code. There are still bits that are proprietary and hold us back from the full potential. If you find anything to make open source performance better or have the skills to make master (kernel 5.10) compatible with NSS again I’d love to improve the performance further.
thanks for the information. I also don't have the necessary skills.
Anybody having dns issues?
I'm having the strangest problems recently after updating to the most recent version of this build last week. Basically, after a day or so everything grinds to a halt.
Running a dslreports speedtest results in this...
timeout doing a trial download error:8
The browser failed on a trial download (10kb) from the closest (by ping) speed test server. The speed test does not continue in this case.
Since the nearest server was already located successfully, failing to download a small test chunk of data is unexpected.
But going directly to my ISP's speedtest results in this.
It's SUPER weird.
Another strange thing is clients on 802.11n connect to the network but don't get internet access unless I join them to the network with a static address.
I tried doing a full factory reset from Luci but after setting things up again I'm seeing the same behavior. Should I try the hard reset button? Does it do anything different than the Luci reset button?
Normally I can figure things out on my own but this has me very confused. Thanks for any ideas/help.
I have had problems with that, I do not know the solution, the static IP solves for a while and fails again.
Hmm. I’ve added some dynamic dns packages the last couple builds - I’d check to make sure dynamic dns is turned off if you don’t use it. Everything else is the same so it’ll take more troubleshooting. Let me know if that helps.
I am still getting 940/940 and no lookup problems from the router or LAN. Is your router at x.x.x.1 for your IP and have dnsmasq set appropriately for this?
I'm running a PiHole for my DNS and have the router serving that address for DHCP clients.
The router sees this when it gets a DHCP address and DNS from the modem at 192.168.1.254:
Protocol: DHCP client Address: xxx.xxx.xxx.xxx/22 Gateway: xxx.xxx.xxx.1 DNS 1: 192.168.1.254 Expires: 0h 6m 7s Connected: 7d 11h 3m 53s
I serve my LAN at 192.168.2.0/24 with these DNS addresses as DNS forwardings (on the /network/dhcp page) as this is the v4 and v6 address of my pi hole:
192.168.2.3 'IPv6 of my Pi Hole'
under 'Interfaces > LAN > Advanced Settings' I have set the DHCP server to push the local dns with this 'DHCP Options':
and under 'IPv6 Settings', I put the IPv6 address of my Pi Hole.
I do not know if this is 'accepted best practice' or not but I get quick lookups and no complaints form the users (my family). A speedtest from an RPi Client on the LAN shows this:
Server: Nitel - Chicago, IL (id = 12187) ISP: AT&T U-verse Latency: 3.08 ms (0.04 ms jitter) Download: 937.53 Mbps (data used: 690.7 MB) Upload: 937.84 Mbps (data used: 1.1 GB) Packet Loss: 0.0% Result URL: https://www.speedtest.net/result/c/523f41dd-d6bf-4a98-b973-ffc69833192d
Looks good. I have a r7800 dedicated to wired routing only + 2 r7800’s as wireless APs behind it. It is the router and default DNS for my LAN (192.168.1.1, settings are vanilla / pretty much the OpenWrt defaults + tweaks in post#2 above). I’m not seeing any issues with DNS but I’m interested if there are any specific settings that are causing the issues mentioned above.
I do note one thing when I set it up after flashing a new image. Don't know if it causes any problems, though. When I install a new image, I have to add 2 packages to get ddns to work (for me): Drill, Curl. I use duckdns and without these 2 packages, ddns fails to start. I have no idea if it causes other issues, but I install these each time I upgrade.
This should have no connection to LAN DNS lookups, but I'm just posting this so you are aware of it.
@ACwifidude i'm preparing a patch for a clock controller for nss. What to test? I need to know the qsdk target tho.
Anyway in theory this should make all the scaling system work without crash
This patch is needed for nss-drv https://gist.github.com/Ansuel/cfd74b8036482ab94845e0b0d0b1f8f8
And this patches for the ipq806x target
This introduce the safe parent thing missing but in a modern less hacky implementation.
I would really appreciate if someone can confirm this. It's been a long time that i have a variant of this installed on my main router and in the days i'm not abusing it like hell to test other stuff, it does work without crash.
(also to test this it's required to remove the hack to force one frequency)
Cool. I can try to build with these. I’ll try first with the R7800 and see if I can expand from there.
5.10? wrong branch?
Missing includes for the dev_pm function and the declaration of the new clock function, since it doesn't have an include file.
I'll try it out with the 21.02 branch.
Got it running in my Askey RT4230W. The NSS core clks seems to be cycling up and down between 110, 600 and 800 MHz. So looking good so far. Will need more time to see if it fix the random reboot issue.
@Ansuel bad news. My RT4230W rebooted without any crash log. Looks like the problem is still there.
Wth... I need to check my current router why it doesn't crash with this on... The other problem is that i'm missing the firmware where the current image comes from...
but wait 21.02 is on 5.4 ?