Hi, I've tried several times but it doesn't work for me, downloading and uploading remain unchanged.
I use NSS buidli from apccv. These are the steps I performed:
- I installed luci-app-sqm
- then I downloaded this mq-scripts-nss_20230217c-1_all.ipk
and I installed it via package upload - I set the mega, I checked it and then I selected fq_codel and nss-rk.qos and link layer adjustment on none.
but no changes to activate else?
WAN E WAN6 Sono su et0.101
Maybe it doesn't work with map-t?
Maybe it doesn't work on 22.03.x.
I am trying to get 23.05.0+NSS to build all modules but it is not going well. I see dependency issues with the NSS packages when building everything. Messy slow to track down. With luck I'll clear it soon.
I posted a build for 23.05-rc2 couple months ago. You could try that one but I am really reluctant to recommend it as -rc2 had some issue or other and I personally never used it beyond making sure it powered up. Go for it only if you are really desperate.
1 Like
Great I hope you succeed, I prefer to keep this at the moment anxiously waiting for 23.05, the map works perfectly and at the moment no problems regarding daily use however in gaming every 10 seconds I have stutters as if the ping increases even if it doesn't shows, it will be due to the bufferbloat which also goes up to 500 ms, I used dscp but this didn't help
Should I worry about these in my logs?
[103532.273531] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[103811.159419] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[103831.187669] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[104110.065844] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[104130.094727] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[104408.975314] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[104429.006594] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[104707.885643] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[104727.916141] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[105006.792291] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[105026.826895] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[105305.701306] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[105325.736683] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[105604.607670] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[105624.644361] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[105903.514371] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[105923.550560] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[106202.420469] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[106222.466232] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[106501.334663] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
[106521.380389] phy0-ap0: NSS TX failed with error: NSS_TX_FAILURE_TOO_SHORT
I see those too.
Some kind of failure. Seems only an issue if you get tons of them:
On the latest 23.05 build: OpenWrt 23.05-SNAPSHOT, r23499+22-86e852bcd0
I do have some WiFi disconnects with the ath10k build. I also see these messages
[37233.602455] ath10k_warn: 6 callbacks suppressed
[37233.602472] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode
Should I try the Ath10k-ct build?
Can I ask the most basic newbie question? What do most people run? Master (r23580) or Stable (r23499)? I'm used to using KONG builds where the choice is just with nss or without.
-Pat
Vanilla 23.05.0 build with NSS including all modules.
Builds for generic and chromium in bin folder.
Packages can be installed directly from this repo as long as:
etc.opkg.keys.4d45cfc5892d56b4file in thebuild-fixesfolder file needs to be copied to/etc/opkg/keys/4d45cfc5892d56b4- the
etc.opkg.distfeeds.conffile also in thebuild-fixesfolder file is to be copied to/etc/opkg/distfeeds.conf
after that opkg operations should install any package from the official repository and kmods from this repo. Of course packages can be manually installed without these changes.
Cursory testing shows it to work as expected. NSS is, well, NSSing.
Terminal Output
BusyBox v1.36.1 (2023-10-09 21:45:35 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 23.05.0, r23497-6637af95aa
-----------------------------------------------------
root@AP4:~# dmesg | grep NSS
[ 6.140192] * Driver :NSS GMAC Driver - RTL v(3.72a)
[ 6.236185] (unnamed net_device) (uninitialized): nss_gmac_clk_ctl_dev_init: ctx->clk_ctl_base(0xde894000) + CLK_HALT_NSSFAB0_NSSFAB1_STATEA(0x3c20): 0x5b00
[ 6.263645] (unnamed net_device) (uninitialized): nss_gmac_dev_init: nss_base(0xde880000) + NSS_GMACn_CTL(1)(0x34): 0x90c0c
[ 6.276549] (unnamed net_device) (uninitialized): nss_gmac_dev_init: nss_base(0xde880000) + NSS_ETH_CLK_DIV0(0xc): 0x100
[ 6.316813] ipq8064-mdio 37000000.mdio eth0: Initialized NSS GMAC1 interface eth0: (base = 0x37200000, irq = 38, PhyId = 4, PollLink = 0)
[ 6.406411] (unnamed net_device) (uninitialized): nss_gmac_clk_ctl_dev_init: ctx->clk_ctl_base(0xde894000) + CLK_HALT_NSSFAB0_NSSFAB1_STATEA(0x3c20): 0x5b00
[ 6.433841] (unnamed net_device) (uninitialized): nss_gmac_dev_init: nss_base(0xde880000) + NSS_GMACn_CTL(2)(0x38): 0x80c0c
[ 6.446777] (unnamed net_device) (uninitialized): nss_gmac_dev_init: nss_base(0xde880000) + NSS_ETH_CLK_DIV0(0xc): 0x100
[ 6.468740] (unnamed net_device) (uninitialized): nss_gmac_qsgmii_dev_init: NSS_QSGMII_CLK_CTL(0x2c) - 0x0
[ 6.515076] ipq8064-mdio 37000000.mdio eth1: Initialized NSS GMAC2 interface eth1: (base = 0x37400000, irq = 39, PhyId = 0, PollLink = 0)
...
[ 6.741018] nss_driver - fw of size 544712 bytes copied to load addr: 40000000, nss_id : 0
[ 6.741702] nss_driver - Turbo Support 1
[ 6.795032] bf071880: nss core 0 booted successfully
[ 6.860605] nss_driver - fw of size 218860 bytes copied to load addr: 40800000, nss_id : 1
[ 6.892607] bf075fc0: nss core 1 booted successfully
...
[ 2568.699670] Created a NSS virtual interface for dev [nssifb]
[ 2568.817336] Nexthop successfully set for [eth0] to [nssifb]
...
I am using it on an AP. AP bufferbloat on WiFi scores an A or a B on close proximity with throughput around 500MBits and CPU usage in 25%-50% range. Pretty much in line with previous builds.
YMMV as a router.
If there's interest I'll post the ImageBuilder to Mega.
BEWARE: traffic shaping doesn't seem to work -- but I think I know why
root@AP4:~# tc qdisc add dev nssifb root handle 1: nsstbl rate 500Mbit burst 1Mb
Unknown qdisc "nsstbl", hence option "rate" is unparsable
Seems I'm not alone but I have not found a fix.
IPQ807X NSS Build - #178 by zek-cmd
The qdisc module is loaded but nothing is using it, at least on my device (TP-Link C2600). Maybe on the Netgears it will work. If anyone is adventurous enough to try it please share the results.
Don't like -ct?
Connect via Ethernet (WiFi will die during this operation)
- Ensure software indexes are OK.
opkg update - Figure out which radio chip you have.
opkg list-installed | grep ath10k-firmware - Remove the -ct firmware installed. eg,
opkg remove ath10k-firmware-qca99x0-ct - Install non -ct firmware. eg,
opkg install ath10k-firmware-qca99x0 - Remove the kernel module.
opkg remove kmod-ath10k-ct - Install non -ct kernel module.
opkg install kmod-ath10k(smallbuffers an option) - Reboot
ImageBuiler and howto
Generic ImageBuilder: https://mega.nz/file/Mz502DTA#sqMaBek3Owm4wqI9YwnSqLYsgv6hh964LUj_tJm4t40
Chromium InageBuilder: https://mega.nz/file/UyQRHbha#avURe9_Ejx-OjQSH4ZQFYlOI5kodVGzaLuhLwYQbY18
What to do with that?
- Download it
- Unarchive it (eg,
tar -xvf <file.xz>and cd into it - Get the
etc.opkg.keys.4d45cfc5892d56b4file in thebuild-fixesfolder and store it in thekeysdirectory as4d45cfc5892d56b4 - Get the
etc.opkg.distfeeds.conffile also in thebuild-fixesfolder. Modify therepositories.conffile starting line 6 so that it uses those repo entries instead (do not delete the config lines after repo list, those stay). Should look like this:
## Place your custom repositories here, they must match the architecture and version.
# src/gz %n https://downloads.openwrt.org/releases/23.05.0-rc2
# src custom file:///usr/src/openwrt/bin/ipq806x/packages
## Remote package repositories
#src/gz openwrt_core https://downloads.openwrt.org/releases/23.05.0/targets/ipq806x/generic/packages
src/gz openwrt_nss https://github.com/APCCV/OpenWRT-23.05.0-NSS/raw/23.05.0-nss/bin/targets/ipq806x/generic/packages
src/gz openwrt_base https://downloads.openwrt.org/releases/23.05.0/packages/arm_cortex-a15_neon-vfpv4/base
src/gz openwrt_luci https://downloads.openwrt.org/releases/23.05.0/packages/arm_cortex-a15_neon-vfpv4/luci
#src/gz openwrt_nss https://downloads.openwrt.org/releases/23.05.0/packages/arm_cortex-a15_neon-vfpv4/nss
src/gz openwrt_packages https://downloads.openwrt.org/releases/23.05.0/packages/arm_cortex-a15_neon-vfpv4/packages
src/gz openwrt_routing https://downloads.openwrt.org/releases/23.05.0/packages/arm_cortex-a15_neon-vfpv4/routing
#src/gz openwrt_sqm_scripts_nss https://downloads.openwrt.org/releases/23.05.0/packages/arm_cortex-a15_neon-vfpv4/sqm_scripts_nss
src/gz openwrt_telephony https://downloads.openwrt.org/releases/23.05.0/packages/arm_cortex-a15_neon-vfpv4/telephony
## This is the local package repository, do not remove!
src imagebuilder file:packages
option check_signature
make infowill list the profiles available. Identify the one needed.make imagewill do what it says. Requires parameters and such. For example:
PROFILE="tplink_c2600" PACKAGES="luci" make image- In addition,
make manifestwill list the packages that will be included. Requires parameters too. Good for comparing with a running router after aopkg list-installedto make sure everything needed made it in. For example:
PROFILE="tplink_c2600" PACKAGES="luci" make manifest - Image will be in
bindirectory - other files can be added... ImageBuilder documentation here: https://openwrt.org/docs/guide-user/additional-software/imagebuilder
How to Build (although honestly save yourself the pain and just use the repo and maybe the ImageBuilder)
-
git clone https://git.openwrt.org/openwrt/openwrt.git && cd openwrt
-
git checkout v23.05.0
-
git remote add other https://github.com/ACwifidude/openwrt.git
-
git fetch other
-
git cherry-pick 14a9e74463e59f97a469a4226e95e379833cb842
-
git cherry-pick db80ce5e1d6d58632431f5d18924dd982df16ed5
-
git cherry-pick ad0915613dc47d30c43a5aa1325237c9c2b37a0c
-
git cherry-pick 2aafd3e050287c374601d1c1e7bf8c3e5f1caabe
-
git cherry-pick d31598618aec1658ac7010b0a58a1b32839771eb
-
git cherry-pick 31f4c9bbfbe26a46e477f976acb75f2567c0df41
-
git cherry-pick 468f2939af7a6a75c57aac4d1920c5f7b985aaa5
-
git cherry-pick 004578b74db32319040fa048b846c6e1fb31a9a5
-
git cherry-pick bb6b7919f8e011d90270cae29fb52721a740a193
-
git cherry-pick 54960e199007b513d1b0159e803f06c64dd6d6c4
-
git cherry-pick 5837453cd19968a496542e46114ab54042da3ea2
-
git cherry-pick 361d02afba5a5ebfb3056f8b730a2b331a91ec4c
-
git cherry-pick f826c6f09035a94d92d34fb02212c2d49c6ac6c5
-
git cherry-pick 3092a9569fb9771e219bbeaa1488ad95e51a64ef
-
git cherry-pick 75a06e063ca94384741970da6b76504fd4b5ec90
-
git cherry-pick 32b108cc22496c80dbf0da49366bcc4d7882fde4
-
git cherry-pick 5008148c7ce9f253a8a8d4283311b125cedd4ee7
-
git cherry-pick cbcb45924e9599fb7ece4bf88fdc4d33557344c3
-
git cherry-pick 6fc098316410d2aaac9cb82f463f5914c5e46723
NOTE: cherry pick commit sha2s might change once ACwifidude rebases -
git branch 23.05.0-NSS
-
git checkout 23.05.0-NSS
-
git remote remove other
-
./scripts/feeds update -a && ./scripts/feeds install -a
-
cp build-fixes/feeds.nss.qca-nss-clients.Makefile feeds/nss/qca-nss-clients/Makefile
-
cp build-fixes/feeds.nss.qca-nss-ecm.Makefile feeds/nss/qca-nss-ecm/Makefile
-
./scripts/feeds install -a
-
cp config.nss .config
-
make defconfig
-
make menuconfig
-
make V=s -j9 (adjust CPU cores if different from 8)
3 Likes
I don't know if we've ever run a poll.
- If you are a tinkerer or have very specific needs, build your own (of either).
- If you like the latest and greatest, or if your device is only supported by Master, run Master.
- If you prefer stability and known issues, run Stable.
@apccv , @ACwifidude , I didn't chime in for a while.
At the moment I'm wrapping my head around a openWRT template on a cheap Intel firewall to substitute my loyal R7800, but...
Do you know how much of a difference you make in this world? I wanted to stress it.
We live in a world of disposable objects. Ones that are very expensive to produce, and to buy, and for several reasons we are obliged to throw them away for the next "good thing".
But not with you.
It's at least two years that I stumbled in this thread, with my second-hand Netgear router. Two years that my R7800 serves internet to me and 2 other apartments. Two years that it's doing much, much better than in its original factory condition. Two years of a product that could be just "meh", because of SW castration, and it's "wow", because some people like you knows how to optimize, and chooses to share this huge knowledge.
You even made it accessible to everyday SimpleSimpel like me, that hasn't got a programming background.
So thanks. Really.
You're some geeks I'd love to have a beer with.
Let me know if your everyday life needs any improvement. I could come and paint your apartment for free!
8 Likes
great job I knew you could do it, I can already install it on my xr500 have you tried if custom sqm works? I've seen now you wrote that Traffic Shaping does not work
Yes please, post the ImageBuilder to Mega.
Collected errors:
- check_data_file_clashes: Package kmod-nat46 wants to install file /lib/modules/5.15.134/nat46.ko
But that file is already provided by package * kmod-qca-nat46 - opkg_install_cmd: Cannot install package map.
It gives me this error
I solved it by deleting kmod-qca-nat46
I went back to version 22.03 because when I installed Map the download dropped to 500 megs out of 1000 and the CPU was at 100% during speed. Then while using the Sqm the connection no longer worked, only after deactivating it and restarting the router did the connection return. I've tried this several times
oookaaaayyyy then.
Sorry about that. Guess that build is a bit of a dud.
Thank you for the feedback. There are other nss modules that might have been needed for the map thing (kmod-qca-nss-drv-map-t comes to mind) but if you're back to 22.x it's too late to try those out. If you ever feel like tinkering please install that guy as part of your setup.
There is something off with SQM on that build... but at least you got a reaction out of it. It has ignored me so far. I used to have a spare to test router functions but one router died so I can't do that anymore.
Thank you for trying that out. As an access point the thing works awesome but that is only using a fraction of what you are.
Cheers!
PS:
Well, that probably killed some critical NSS piece, and resulted in 100% CPU at 500mbit.
This is a tough dependency issue to solve as NSS is an add on to the OpenWrt system and the map package has no clue of its existence. map would need to be modified to have a NSS variety.
I suggest you force re-install kmod-qca-nat46 after map has been installed to overwrite the module with the NSS version. No guarantees that will work but we may both be surprised.
Oh man, you're too kind. But honour where it is due.
First, there are many people that make the linux kernel what it is. Then there are plenty more that make everything beside the kernel. Then there's another huge crowd that made OpenWrt what it is for the so many years that it is been around, both OpenWrt proper and feeds. On top of that there's a select group of experts that figured out the NSS piece of it. Last but not least there's ACwifidude who started this thread and has kept it going for 4 years and counting.
Me? I just take what all those people have accomplished and make it work for me. I happily share what I do and I really enjoy it if it helps someone else, but my contribution is a spec on an ocean of free software generosity.
So thank you, much appreciated. However, the number of people that deserve recognition equally, or most probably much more than me, even if you're thinking of this thread exclusively, is outstandingly large.
5 Likes
Uploaded.
Edited post above to include a section about ImageBuilder. Link inside. Cheers!
1 Like
The amount of fabulous people in the Linux environment and particularly in owrt is so clear that it feels like being back to school, but with an exciting twist!
I've been thanking others in these years, on this right thread, too. But as you say, the list is soo long that I keep losing myself.
But rest assured, some of the best gentlemen I met here are particularly kind.
I'm visiting frequently the forum on proxmox site and...well, didn't encounter the same availability.
My two cents.
3 Likes
tried but it didn't work.
Maybe this could work.
my situation is a bit complicated because I have to send high and stable speeds therefore with low jitter and bufferbloat. Call of duty is a bit strange, it goes against any IT law that we know because in reality it needs a few kbytes but if you set 20 mb the player doesn't run smoothly whereas if you set 1000 it runs smoothly but you get very strange kills. So I want to get somewhere in between.
I was thinking about buying a new router to fix this problem. The connection will be ONT-router (with nss openwrt 22.03 with map-t active if possible with passthrough without firewall etc.) and in cascade a router, the most powerful one (with nss openwrt 23.05 ACwifidude connected via static ip so as to be able to use sqm) do you think it could work? What router do you recommend?