Hello, I am currently using the "R7800-20240115-Stable2305NSS-sysupgrade.bin" from ACwifidude. Unfortunately, he has not yet released a new build for 23.05.3 and he will probably change his main router - probably the motivation for new builds is now missing.
Can I upgrade to "23.05/ipq806x-nss/kong-ipq806x-generic-netgear_r7800-squashfs-sysupgrade.bin" without any problems? Or do I have to pay attention to anything?
I have nothing special, a few firewall rules, OpenVPN server, DDNS alias, separate guest WLAN and Internet via PPPOE dial-up.
You can just upgrade, the core is absolutely identical. The only difference is, that I ship my dark theme and a different set of included apps. Openvpn,DDNS,PPPOE is among the included apps, thus you don't even have to use opkg to install anything after flashing.
@KONG Installed your latest (non-nss) stadard build on R7800 (8th of April) - classic sysupgrade, keeping settings. I had nothing special configured (guest lan which redirects to wireguard via pbr) so standard config, done from scratch begining of this year.
All fine - but I am getting below spam in SYSTEM log (kernel log looks fine):
It just continues every minute or so. Not sure if previously it was the same - cannot remember. I am upgrading regurarly and don't remember seeing this in Jan/Feb.
I run as vanilla configuration of Kong build as possible (nothing installed, nothing disabled or removed) for few years now - speaking of which, owing big deal to Kong!. This is to mitigate any problems and - because I am not-technical in this space, more of a newbie.
This was also feedback of a Kong (non-nss) build - not to spam System log output as this behaviour is present by default and I think it has happened just recently. So my config:
I used to have openvpn and ddns disabled but any new flash enables them back. Not sure what else is safe to disable and/or even uninstall. In my case, not planning VPN server or OpenVPN, thus they are disabled as well.
I honestly didn't know what it was (quick google showed usage for IP TV) - so if it's not required by any other critical components remove it please. If it provides super useful feature than keep it and just fix the log spam. Thanks for your firmware @KONG!
I have seen you've updated NSS branch twice in last two days, any update to the non-nss one or not really required? I am still in doubt of going cutting edge to NSS branch on this router - so rather keep things as stable as.
Another question - which WiFi6/7 router do you think will replace R7800 in its legendary status? Sadly (or luckily?) I can only purchase router you will support
No change in the last two nss builds except adding new packages. Thus no need to update.
My favorite would be the qnap, but it is expensive. The Armor G5 I use for testing was 60€ on ebay:-) The qnap has no fan and has more leds, easy to add a 3.5 jack for serial connection.
For the last few builds I’ve been having 2.4ghz problems but wasn’
t with enough time to explore. I’ve updated to the latest build two days ago and now most of my IoT devices are getting dropped and log shows lots of IEEE 802.11: did not acknowledge authentication response . I’ve restored default settings, loaded my backup with vanilla wireless settings but still having errors. Any clues on how to fix this?
Unfortunately didn't work. I've also disabled disassociating on low ack, still not working. It seems to improve the disconnection interval after reboot, but after some hours it's back to every other minute.
On a fresh install with default settings it works okay for 1 day, then starts again.
This is what my log shows:
Fri Jun 7 17:54:41 2024 daemon.info hostapd: phy1-ap0: STA ec:fa:bc:7c:72:8e WPA: pairwise key handshake completed (RSN)
Fri Jun 7 17:54:41 2024 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED ec:fa:bc:7c:72:8e
Fri Jun 7 17:54:42 2024 daemon.info dnsmasq-dhcp[11052]: DHCPDISCOVER(br-lan) ec:fa:bc:7c:72:8e
Fri Jun 7 17:54:42 2024 daemon.info dnsmasq-dhcp[11052]: DHCPOFFER(br-lan) 192.168.1.210 ec:fa:bc:7c:72:8e
Fri Jun 7 17:54:46 2024 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED ec:fa:bc:7c:72:8e
Fri Jun 7 17:54:46 2024 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED c8:2b:96:04:bd:1a
Fri Jun 7 17:54:47 2024 daemon.notice hostapd: phy1-ap0: STA ec:fa:bc:7c:72:8e IEEE 802.11: did not acknowledge authentication response
Fri Jun 7 17:54:47 2024 daemon.info hostapd: phy1-ap0: STA c8:2b:96:04:bd:1a IEEE 802.11: authenticated
Fri Jun 7 17:54:47 2024 daemon.info hostapd: phy1-ap0: STA c8:2b:96:04:bd:1a IEEE 802.11: associated (aid 7)
Fri Jun 7 17:54:56 2024 daemon.info hostapd: phy1-ap0: STA c8:2b:96:04:bd:1a IEEE 802.11: deauthenticated due to local deauth request
Fri Jun 7 17:55:12 2024 daemon.info hostapd: phy1-ap0: STA ec:fa:bc:7c:72:8e IEEE 802.11: authenticated
Fri Jun 7 17:55:12 2024 daemon.info hostapd: phy1-ap0: STA ec:fa:bc:7c:72:8e IEEE 802.11: associated (aid 4)
Fri Jun 7 17:55:21 2024 daemon.info hostapd: phy1-ap0: STA ec:fa:bc:7c:72:8e IEEE 802.11: deauthenticated due to local deauth request
Fri Jun 7 17:55:23 2024 daemon.info hostapd: phy1-ap0: STA c8:2b:96:04:bd:1a IEEE 802.11: authenticated
The problem is with 7 clients (IR Hubs, ESP32 and Samsung Washer and Refrigerator)
Edit: before May 27th everything was working fine, and restoring settings from dates before that doesn't seem to make things any better. I've checked here and I've updated on May 9th to the current KONG version at that time
Edit2: Just found out that system clock was losing sync from NTP servers/browser sync. I've resynced and got the following kernel error:
[ 66.024137] br-lan: port 3(phy0-ap0) entered forwarding state
[ 676.957838] ath10k_pci 0001:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[ 797.598971] ath10k_pci 0001:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[ 1140.077592] ath10k_pci 0001:01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0
[ 1311.187312] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 1311.187349] rcu: 0-...!: (0 ticks this GP) idle=478/0/0x0 softirq=33440/33440 fqs=0 (false positive?)
[ 1311.192042] (detected by 1, t=2102 jiffies, g=53989, q=477)
[ 1311.201413] Sending NMI from CPU 1 to CPUs 0:
[ 1311.207319] NMI backtrace for cpu 0
[ 1311.207325] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.158 #0
[ 1311.207331] Hardware name: Generic DT based system
[ 1311.207333] PC is at arch_cpu_idle+0x38/0x3c
[ 1311.207347] LR is at arch_cpu_idle+0x34/0x3c
[ 1311.207353] pc : [<c03071dc>] lr : [<c03071d8>] psr: 60000013
[ 1311.207357] sp : c0d01f60 ip : de80400c fp : c0d04f98
[ 1311.207359] r10: c0d04f08 r9 : ffffe000 r8 : 00000000
[ 1311.207362] r7 : 00000000 r6 : c0d00000 r5 : c0d04f68 r4 : 00000000
[ 1311.207365] r3 : c0316a00 r2 : 00000001 r1 : 00000000 r0 : 00bf6530
[ 1311.207368] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none
[ 1311.207373] Control: 10c5787d Table: 45e8c06a DAC: 00000051
[ 1311.207376] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.158 #0
[ 1311.207380] Hardware name: Generic DT based system
[ 1311.207387] [<c030ddd8>] (unwind_backtrace) from [<c0309d28>] (show_stack+0x10/0x14)
[ 1311.207400] [<c0309d28>] (show_stack) from [<c05eb0a4>] (dump_stack_lvl+0x40/0x4c)
[ 1311.207415] [<c05eb0a4>] (dump_stack_lvl) from [<c05f295c>] (nmi_cpu_backtrace+0xc4/0x110)
[ 1311.207427] [<c05f295c>] (nmi_cpu_backtrace) from [<c030c698>] (do_handle_IPI+0x5c/0x12c)
[ 1311.207437] [<c030c698>] (do_handle_IPI) from [<c030c780>] (ipi_handler+0x18/0x20)
[ 1311.207445] [<c030c780>] (ipi_handler) from [<c0370df0>] (handle_percpu_devid_irq+0x78/0x13c)
[ 1311.207457] [<c0370df0>] (handle_percpu_devid_irq) from [<c036afe4>] (handle_domain_irq+0x5c/0x78)
[ 1311.207471] [<c036afe4>] (handle_domain_irq) from [<c03012e4>] (gic_handle_irq+0x7c/0x90)
[ 1311.207482] [<c03012e4>] (gic_handle_irq) from [<c0300b7c>] (__irq_svc+0x5c/0x78)
[ 1311.207491] Exception stack(0xc0d01f10 to 0xc0d01f58)
[ 1311.207496] 1f00: 00bf6530 00000000 00000001 c0316a00
[ 1311.207500] 1f20: 00000000 c0d04f68 c0d00000 00000000 00000000 ffffe000 c0d04f08 c0d04f98
[ 1311.207504] 1f40: de80400c c0d01f60 c03071d8 c03071dc 60000013 ffffffff
[ 1311.207507] [<c0300b7c>] (__irq_svc) from [<c03071dc>] (arch_cpu_idle+0x38/0x3c)
[ 1311.207517] [<c03071dc>] (arch_cpu_idle) from [<c034f3e0>] (do_idle+0x23c/0x29c)
[ 1311.207534] [<c034f3e0>] (do_idle) from [<c034f744>] (cpu_startup_entry+0x18/0x1c)
[ 1311.207545] [<c034f744>] (cpu_startup_entry) from [<c0c011a0>] (start_kernel+0x6b4/0x6c4)
[ 1311.208316] rcu: rcu_sched kthread timer wakeup didn't happen for 2103 jiffies! g53989 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
[ 1311.418521] rcu: Possible timer handling issue on cpu=0 timer-softirq=23471
I've dropped to 22.03 ath10k-ct NSS but still having log errors and those clients dropping. Any suggestions for a stable build for a R7800? I've been quite behind all the discussion.
Sat Jun 8 00:08:49 2024 kern.info kernel: [ 417.720116] ath10k_pci 0001:01:00.0: mac flush vdev 0 drop 0 queues 0x1 ar->paused: 0x0 arvif->paused: 0x0
