See if these posts above provide helpful crash logs:

1 Like

I don't know how to do that, you mean mtu? this by default. 1500, I think.

Question: are you applying any custom tunings to the build? Any additional packages installed via opkg, like irqbalance.

No, nothing. image installed and clean. what if I keep is the configuration. Network, openVPN and adblock, is what I use

Posted in the Kong Build thread, but the non-ct drivers seem better. I have not had an nlbwmon 'out of memory' error since I re-booted it on Monday morning.

Running non-ct drivers (kmod) and firmware - or just the firmware?

Kong claims that his build has non-ct drivers and I guess the firmware as well. I did not check it, only relied on what he posted. Kong on non-ct

Keith

KONG NSS r16548

ath10k-board-qca9887 - 20201118-3
ath10k-board-qca9888 - 20201118-3
ath10k-board-qca988x - 20201118-3
ath10k-board-qca9984 - 20201118-3
ath10k-board-qca99x0 - 20201118-3
ath10k-firmware-qca9887 - 20201118-3
ath10k-firmware-qca9888 - 20201118-3
ath10k-firmware-qca988x - 20201118-3
ath10k-firmware-qca9984 - 20201118-3
ath10k-firmware-qca99x0-ct - 2020-11-08-1
...
kernel - 5.4.110-1-ca195f5aff0190c940b9016759f075f1
...
kmod-ath10k - 5.4.110+5.10.16-1-1
kmod-ath9k - 5.4.110+5.10.16-1-1
kmod-ath9k-common - 5.4.110+5.10.16-1-1

NSS cores perfectly stable here 800MHz static frequency, maybe setting 600MHz same voltage for specific cases.

I'm at a loss from for words on the performance regression on master as compared with the 19.07.3 release build that I was running on my R7800. Luckily I only flashed my spare R7800 with the latest master build so I can still go back to the other one running 19.07.3.

19.07.3 was running software flow offloading and I was able to achieve gigabit WAN<>LAN speeds (I have fiber with gigabit symmetrical speeds upto 942mbps), I was getting fairly close to 890-920mbps with just software flow offloading... My Wi-Fi performance peaked around 590~600mbps down with ath10k. I would have been fine with ath10k-ct had it not been for my TV not able to connect to 5GHz.
With master (about 3 weeks old) + software flow offload, I am seeing about 680mbps max line WAN<>LAN speed and my Wi-Fi speeds are degraded as well (ath10k or ath10k-ct don't make much difference), it is about 330-330mbps down max but upload is significantly improved and I can reach about 400mbps. What the heck happened ?

I'm inclined to try an NSS enabled build to get myself to the 1gbps mark.

@KONG Are these builds of your's built off master ? Anyone of these builds able to achieve close to 550~600mbps 5Ghz in VHT80 mode ? The advantage with such a build will be the lowered CPU usage due to NSS cores being enabled. Is WiFi traffic also hardware offloaded (NSS'd) ? I'm ok to tweak a few setting here and there once flashing an NSS build, but I was pretty happy with the default performance on the 19.07.3 build such that I only had to tweak two settings on startup such as below:

echo 35 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 10 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor

So I'll likely want to keep things as vanilla as possible, I don't run any qos but might consider it down the line to keep buffer-bloat in check, but that is very low in priority right now. Right now, WAN<>LAN speed and wifi throughput are more important. Also what doesn't help is the horrible jitter on the wifi (5GHz), doesn't matter if it is ath10k or ath10k-ct... Maybe the NSS helps with that a bit (does it)?

So might as well start with an NSS cores enabled build, but If I can get some feedback on WiFi performance on some of these builds, that would be great (I assume achieving gigabit line speeds shouldn't be a problem). I know there are multiple NSS builds (quarky's, Kong, Ansuel, hnyman, etc)...
anywhere I should start ?

Thx

Hello all,
i need your help because i've lost the track of the status of NSS development :slight_smile:
i've been using NSS builds for a while (since the original Ansuel's development), my build is also quite stable (i get a reboot once every two or three weeks), but i'm stuck at OpenWrt SNAPSHOT r14793+75 since then we got problems with master modifications and so on.
Basically, i'd like to update my version, but i lost the track on some points..

  • is NSS working (for what it can work) also over wifi, with plain ath10k drivers and firmware (not ct)?
  • did we manage to have a script for sqm, like the one kong uses in his builds?
  • is the development for kernel 5.10 going on? and what about dsa?
  • is crypto definitely abandoned, since it offered no performance gain?
  • is it safe, today, to build starting from ACwifidude repository and rebasing it with master? or something is going to break?

This should be all, thank you all as always (more to @ACwifidude :))

The prior Software offloading is faster but upstream linux went a different way so openwrt followed their lead.

Hardware offloading is the way to go with the ipq806x. I’m maintaining the build with the help of lots of great developers.

This is what wifi looks like using a 2x2 80mhz iphone 7 client and CT drivers:

Imagen de Kong nss del día 24 a 1 metro del router.
Redmi note 10T 2x2.

1 Like
  • is NSS working (for what it can work) also over wifi, with plain ath10k drivers and firmware (not ct)?
    -yes it is working with ath10k

  • did we manage to have a script for sqm, like the one kong uses in his builds?
    -There is a script in post 2 above that you can run at start up. I don’t have it integrated with the gui (luci) but would be interested in getting it in to luci.

  • is the development for kernel 5.10 going on? and what about dsa?
    -developers are working on 5.10 - NSS patches will need to be reconfigured

  • is crypto definitely abandoned, since it offered no performance gain?
    -NSS crypto was abandoned. The crypto in this build has all the packages needed to optimize performance (it is as fast as an optimized vanilla master openwrt build)

  • is it safe, today, to build starting from ACwifidude repository and rebasing it with master? or something is going to break?
    -It needs an update to the ECM patch. I’m going to fix it today. If you don’t rebase you can build it from the repo without issue.

Enjoy! :sunglasses:

With normal ath drivers (non-ct)?

I added a d7800 image. Feel free to test it and let me know how it performs.

@KONG - I forgot - did you successfully add a nss fq_codel script that you can use luci sqm page to configure?

If so I’d love to check it out if you happen to have it on your git page so that I can replicate it. :sunglasses:

Hello

I build and use the nss build from your repo.

Is NAT for ipv6 supported? I want to use dnat and masquerade. With normal openwrt build it is working. With nss build I see the initial packets are transmitted and then it stops working. It seems the time when the nss should start the acceleration.

Regards

Celle

IPv6 support is included and IPv6 NAT is supported.

This post has the full list of packages:

So if you tested it, I habe to debug my problem further.

I asked because also in the ipv6 frontend code I did not find Nat related things. In the ipv4 ecm frontend code I see it. Is the best way to try the connection and make a ecm_dump.sh?

Is there a way to prevent the acceleration of single connections? I know I can stop it globally with echo 1 > /sys/kernel/debug/ecm/front_end_ipv6_stop.

Personally I don’t use ipv6 NAT - the beauty of ipv6 is that ipv6 doesn’t require NAT (in the sense of ipv4). I let all my ipv6 devices create their own addresses and do their own thing. :sunglasses: