IPQ807X NSS Build

Why 4 vlans?

With one should be enough

1 Like

:joy: because I have just a little knowledge here, never ever deal with vlan before. Could you please tell me how to dial 4 pppoe sessions with vlan?

Yes, you can bind pppoe to different vlanIDs on the same lan in vlan binding mode on ONT, and then use the wan port of ax6 to link the lan port. But I'm not sure if it works.

1 Like

Dear Rmandrad.
Hello and I hope that you are well.
I just bought the ‎DL-WRX36 and I pretty much have it figured out as to how to flash the device with OpenWRT.
I just have one simple question - regarding the installation instructions on the Wiki.

1. Copy the initramfs image 
to a FAT-formatted flash drive

My question is do I format the USB to
fat or fat32 ?

Or does it matter - thanks that is all I need to know.

FAT VS. FAT32 is my inquiry

Thanks and Peace

The DL-WRX36 doc page OEM Bootlog shows an old kernel 4.4 is used. This is a Linux based firmware so FAT and FAT32 is the same driver. In other words, just use FAT32.

For all using IPQ807X hardware and still seeing WiFi clients issues (ping loss, etc.) it might worth checking this post.

For those who want to try nss-offloading on the ZyXEL nbg7815 I have managed to release a working version that once it's running has no errors so far.

Here is the link to this release.

Read advice before installing

4 Likes

I've faced same issue, the resolution was:

  • uninstall tc-bpf package and all tc releted one
    opkg remove tc-bpf tc-full tc tc-tiny
  • reboot
  • disable openwrt feed (commented out all lines in /etc/opkg/distfeeds.conf)
  • enable my build feeds in /etc/opkg/customfeeds.conf
  • install only tc-tiny rom my feeds:
    opkg install tc-tiny

after that no issues with error

Unknown qdisc "nsstbl", hence option "rate" is unparsable

@ReDaLeRt @zek-cmd @di_Niko @eww : I saw you had this issue, maybe this will also help you

3 Likes

I'm trying to shape a pppoe connection and I'm having problems with ingress traffic but no problems with egress traffic.
This is the process I have followed. The wan interface is including the lan1 device. This is the process I followed:

root@NBG7815:~# /etc/init.d/qca-nss-mirred start
root@NBG7815:~# insmod nss-ifb nss_dev_name=lan1
root@NBG7815:~# ip link set up nssifb
root@NBG7815:~# tc qdisc add dev nssifb root handle 1: nsstbl rate 500Mbit burst 1Mb
root@NBG7815:~# tc qdisc add dev nssifb parent 1: handle 10: nssfq_code limit 10240 flows 1024 quantum 1514 target 5ms interval 100ms set_default
root@NBG7815:~# tc qdisc add dev lan1 root handle 1: nsstbl rate 500Mbit burst 1Mb
root@NBG7815:~# tc qdisc add dev lan1 parent 1: handle 10: nssfq_code limit 10240 flows 1024 quantum 1514 target 5ms interval 100ms set_default

kernel log

Thu Aug 24 12:04:33 2023 kern.info kernel: [ 9110.283744] Created a NSS virtual interface for dev [nssifb]
Thu Aug 24 12:04:33 2023 kern.info kernel: [ 9110.288166] NSS IFB data callback registered
Thu Aug 24 12:04:33 2023 kern.info kernel: [ 9110.293858] NSS IFB transmit callback registered
Thu Aug 24 12:04:33 2023 kern.info kernel: [ 9110.298947] NSS IFB module loaded.
Thu Aug 24 12:04:43 2023 kern.info kernel: [ 9120.587815] 000000002a699657: Found net device [lan1]
Thu Aug 24 12:04:43 2023 kern.info kernel: [ 9120.587858] 000000002a699657: Net device [lan1] has NSS intf_num [1]
Thu Aug 24 12:04:43 2023 kern.info kernel: [ 9120.592366] Nexthop successfully set for [lan1] to [nssifb]
root@NBG7815:~# tc qdisc list | grep nss
qdisc nsstbl 1: dev lan1 root refcnt 5 buffer/maxburst 1Mb rate 500Mbit mtu 1514b accel_mode 1
qdisc nssfq_codel 10: dev lan1 parent 1: target 5ms limit 10240p interval 100ms flows 1024 quantum 1514 set_default accel_mode 0
qdisc nsstbl 1: dev nssifb root refcnt 2 buffer/maxburst 1Mb rate 500Mbit mtu 1514b accel_mode 0
qdisc nssfq_codel 10: dev nssifb parent 1: target 5ms limit 10240p interval 100ms flows 1024 quantum 1514 set_default accel_mode 0

The result, as i said before, is there is no control over the ingress. Egress traffic is well controlled.

Does anyone know what's going on with ingress traffic?
Is there anyone having the same problem?

1 Like

you are shaping traffic on lan1 port not wan - I assume that your pppoe connection is wan interface. If yes , then your traffic shaping should look like:

insmod nss-ifb nss_dev_name=wan
ip link set up nssifb

# Shape ingress traffic to 500 Mbit with chained NSSFQ_CODEL
tc qdisc add dev nssifb root handle 1: nsstbl rate 500Mbit burst 1Mb
tc qdisc add dev nssifb parent 1: handle 10: nssfq_codel limit 10240 flows 1024 quantum 1514 target 5ms interval 100ms set_default

# Shape egress traffic to 500 Mbit with chained NSSFQ_CODEL
tc qdisc add dev wan root handle 1: nsstbl rate 500Mbit burst 1Mb
tc qdisc add dev wan parent 1: handle 10: nssfq_codel limit 10240 flows 1024 quantum 1514 target 5ms interval 100ms set_default

It might be useful also to change quantum size from 1514 into 1518 for pppoe connection, since frame size for pppoe is 1518 - but I'm not sure if nss can handle custom size properly (worth to try)

1 Like

my wan connetion is on lan1 port.

i will change to 1518 to tray

I've compiled @bitthief repo + patch + wireguard, nss offload enabled, nss qdisc enabled, connection fiber, home usage stats for 24hr window https://imgur.com/a/yp3CCX2
Looks very stable in terms of cpu usage and memory
Only thing that worries me, is transfer that went through phy1-ap0. In my case it's 3TB which is definitely too high, can you also check if you have similar behavior for your wifi interfaces?

edit: stats for 1 week: https://imgur.com/a/lDvmCTe - looks very stable for me.

2 Likes

hello adamhnat ,can you share your grafana dashboard .

I've used board id 11147 - it's not mine, I've reused it and just change wireless interfaces from wlan0, wlan1 into phy1-ap0, phy2-ap0...

1 Like

Great build. luci-app-sqm is missing in the build?

New release, anyone can confirm if hardware offload works with PPPoE internet?

after update with saved settings now i can't connect to both wifi bands on my dynalink... any ideas why?

yep, trying at RAX120 and unable to install sqm-scripts (and luci-app-sqm too)

@bitthief NSS 6.1 repo is still on kernel 6.1.46.
How is it possible to update to latest 6.1.51. Did anyone make a rebase to latest OpenWrt master?

same as old release