New Build - 06/05/2021 - r46885

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
DD-WRT-Nub
DD-WRT Novice


Joined: 26 Sep 2016
Posts: 24

PostPosted: Fri Jun 11, 2021 2:21    Post subject: Reply with quote
Router: Netgear R7800 (272-12536-01)
Firmware/Upgraded: DD-WRT v3.0-r46885 (06/05/21) via telnet
Kernel: Linux 4.9.271 #228 SMP Sat Jun 5 02:08:22 +07 2021 armv7l
Previous/Reset: DD-WRT v3.0-r44849 std (11/20/20) / nvram erase && reboot
Mode/Status: Gateway running OK 5 days & 13hrs
Temperatures: CPU 51 °C / wlan0 48 °C / wlan1 44 °C
Issues: runs fine with no RX&TX errors
Settings: Ignore WAN DNS/WPA2 AES with Custom Config: basic_rates=60 120 240 supported_rates=60 90 120 180 240 360 480 540/Additional DHCPd Options for minor ip-blocking/Port Forwarding/HTB Cake QoS/Elegant Dark Theme/WiFi Basic Settings:

Notes: on my previous build Short Preamble needed to be disabled to avoid wifi issues on a retired tv, and RX&TX errors were superficially reported when using QoS. All seems fine now with v3.0-r46885.

Thanks to the developer and all contributors!


Last edited by DD-WRT-Nub on Fri Sep 16, 2022 3:15; edited 1 time in total
Sponsor
DWCruiser
DD-WRT User


Joined: 15 Aug 2016
Posts: 223
Location: Melbourne, Australia

PostPosted: Fri Jun 11, 2021 10:17    Post subject: Reply with quote
Router: Netgear R7800 (x2)
Firmware: DD-WRT v3.0-r46885 std (06/05/21)
Kernel: Linux 4.9.271 #228 SMP Sat Jun 5 02:08:22 +07 2021 armv7l
Previous/Upgrade: DD-WRT v3.0-r46640 std (05-13-2021) via GUI
Reset: No
Mode & Uptime: Gateway running over 72hrs
Temperature: CPU 47.144 °C / wlan0 47 °C / wlan1 44 °C
Wireless: 5GHz and 2.4GHz (Vanilla) & vAPS
Features: OpenVPN Client with Kill Switch; OpenVPN Server (for b/up to own cloud); VLANS for added network secure isolation; QoS (HFSC/SFC) on MAC, netmask and i/faces priority; Port Forwarding; CPU overclocked OnDemand;
Issues/Errors: Nothing noted from my observation.

Many thanks to BS and all contributors.
DD-WRT-Nub
DD-WRT Novice


Joined: 26 Sep 2016
Posts: 24

PostPosted: Wed Jun 23, 2021 0:16    Post subject: Not sure if the following issue is fixed on newer builds: Reply with quote
Hi, a few weeks ago I was testing which Sensitivity Range (ACK Timing) settings might work better for my setup, ended settling on 1350 on both bands, although it seems the higher settings are recommended for stability rather than tweaking for a particular environment. The following weekend as a test I bumped the 5GHz band Tx Power to 30dBm without issues and later reverted due to not gaining anything except more range that I didn't need. The above after reverting to 20dBm crashed Vanilla Firmware disabling the 5GHz band and unfortunately I couldn't get the Logs due to WebGUI lagging and freezing for the first time while using Palemoon; I never had router issues like this with DD-WRT. Resetting even with a nvram erase both configuring from scratch or restoring from backup crashed 5GHz using the 1350 ACK Timing, but an interesting observation was that after the reset and nvram erase the router status page showed a defaulting ACK Timing of 900 rather than 500, I ended up using a 900 rate without issues.

Since this is our main router, today I was able to replicate the 5GHz Vanilla Firmware crashing by emulating similar setting changes and maintaining the same device WiFis turned-on (a Galaxy Note20 that only uses the 2.4 band) when this issue originally happened. Changes: 5GHz 20dBm TX Power to 23, 900 ACK Timing to 1350 back and forth x3 until it crashed the 5GHz band Vanilla Firmware. On this first vanilla crash I couldn't navigate the WebGUI, but after turning Off & On the router and changing from 1350 to 900, then finally to 1350, it crashed the 5GHz band while being able to navigate WebGUI with the following log (the fun seems to starts around 12:48:55):


Regards,

Nub


Last edited by DD-WRT-Nub on Wed Jun 23, 2021 0:41; edited 1 time in total
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Wed Jun 23, 2021 0:39    Post subject: Reply with quote
5GHz ack timing should be 3160, 2.4 band should be 3150. Read the sticky or wiki.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
DD-WRT-Nub
DD-WRT Novice


Joined: 26 Sep 2016
Posts: 24

PostPosted: Wed Jun 23, 2021 0:50    Post subject: Reply with quote
kernel-panic69 wrote:
5GHz ack timing should be 3160, 2.4 band should be 3150. Read the sticky or wiki.


Thanks for the reply I did read it. I always thought both bands ACK Timings recommended settings were just suggestions for better ACK Timing function, not a dictation or else it will disable the 5GHz Vanilla Firmware.
ho1Aetoo
DD-WRT Guru


Joined: 19 Feb 2019
Posts: 2927
Location: Germany

PostPosted: Thu Jun 24, 2021 12:02    Post subject: Reply with quote
No if this is true it is a bug.
The Sensitivity Range / ACK Timing is freely selectable and depends on the actual distance between router and client.

If the values are too low, collisions occur because the sender does not wait long enough to start a retransmission and if the values are too high, the sender waits too long to retransmit lost packets.
Both can reduce the effective throughput.

That the ACK timing must be ~3000m is not true.
In many scenarios this is not the correct setting.
Maybe it would be the right setting for a PTP link with ~2000m distance.

The best wifi settings are also only recommendations of a single person.
They are not always up to date and not always correct.
The "best wifi settings" have already recommended prime numbers as a beacon interval - which has subsequently turned out to be nonsense.

just to mention it

you could also set the ACK timing to 0 with the firmware type "dd-wrt".
This activates Auto-ACK
Then you can compare the values with the values that are set automatically / dynamically.
Auto-ACK chooses for me for example some value between 600-1650m

by the way I use 900 as default setting
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Thu Jun 24, 2021 16:22    Post subject: Reply with quote
Well, there's only one other thing that would crash the wifi, but I'm sure I will get countermanded on that, too. All I can say is, I have had no issues with the webUI or wireless crashing, save and except for specific steps required to crash the wireless. But again, I am sure I will get told that I am full of it and don't know what I am talking about.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
kristianissimo
DD-WRT Novice


Joined: 12 Sep 2020
Posts: 9

PostPosted: Thu Jun 24, 2021 17:05    Post subject: Some issues on r64885 build on NETGEAR WNDR4300 Reply with quote
Router Model: NETGEAR WNDR4300 v1
Firmware Version: DD-WRT v3.0-r46885 std (06/05/21)
Kernel Version: Linux 3.18.140-d6 (root@linux) (gcc version 11.1.0 (OpenWrt GCC 11.1.0 r16592-aabc632023) ) #117859 Sat Jun 5 07:25:21 +07 2021 mips
CPU Model: Atheros AR9344 ver 1 rev 1.2 (0x2122) (CPU Cores 1, CPU Features MIPS32r1 MIPS32r2 MIPS16, CPU Clock 560 MHz)
Previous/Reset: Last known version of NETGEAR FW for this model (WNDR4300-V1.0.2.104.img) / Installed DD-WRT wndr4300-factory.img via OFW GUI + Reset to DD-WRT defaults
Mode/Status: Gateway / Working
Issues/Errors:

I've found some errors for this build, e.g.:

Security / Firewall tab - Log for firewall is on but Incoming Log and Outgoing Log is empty.




Last edited by kristianissimo on Thu Jun 24, 2021 17:49; edited 2 times in total
ho1Aetoo
DD-WRT Guru


Joined: 19 Feb 2019
Posts: 2927
Location: Germany

PostPosted: Thu Jun 24, 2021 17:32    Post subject: Reply with quote
kernel-panic69 wrote:
Well, there's only one other thing that would crash the wifi, but I'm sure I will get countermanded on that, too. All I can say is, I have had no issues with the webUI or wireless crashing, save and except for specific steps required to crash the wireless. But again, I am sure I will get told that I am full of it and don't know what I am talking about.


I remember that the router / firmware is not 100% stable.
If you restart the router or the WLAN 100x you can trigger any bugs.
For example, if I set any WLAN interface to auto channel and restart the WLAN 100x then at some point "iw dev ath* scan" hangs.
This is also the reason why the router sometimes does not boot when a WLAN interface is set to auto-channel.

Sometimes I have a worse WLAN performance after a reboot (then I measure e.g. only max 600Mbit instead of 800Mbit).
A new reboot solves the problem and I measure values in the gigabit range again.

These are any poorly reproducible Bugs - which have not been fixed to date.

Best not to restart the WLAN 100x is already a good approach to avoid problems.

By the way, when I just changed from "vanilla" to "dd-wrt" my R7800 made a spontaneous reboot (I'm relatively sure that this was not intended).

In the end it doesn't matter, I just said that ACK-timing doesn't have to be 3000.
It must also work with any other values (by the way, I'm using 1350 right now - no problems).
ho1Aetoo
DD-WRT Guru


Joined: 19 Feb 2019
Posts: 2927
Location: Germany

PostPosted: Thu Jun 24, 2021 17:37    Post subject: Re: Some issues on r64885 build on NETGEAR WNDR4300 Reply with quote
kristianissimo wrote:

I've found some errors for this build. On Services tab WAN Traffic Counter is Disabled, but on Status / Bandwith tab there are windows with traffic graphs


the ttraff daemon and the bandwidth monitor are two different things

the ttraff daemon, detects your data consumption on the WAN interface and you can see the statistics under "Status > WAN".
kristianissimo
DD-WRT Novice


Joined: 12 Sep 2020
Posts: 9

PostPosted: Thu Jun 24, 2021 17:45    Post subject: Re: Some issues on r64885 build on NETGEAR WNDR4300 Reply with quote
ho1Aetoo wrote:
kristianissimo wrote:
I've found some errors for this build. On Services tab WAN Traffic Counter is Disabled, but on Status / Bandwith tab there are windows with traffic graphs

the ttraff daemon, detects your data consumption on the WAN interface and you can see the statistics under "Status > WAN".

Oh, I see. Thank you. I turned it on for a while to see the effect at the WAN tab but now I turned it off again.
lexridge
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 960
Location: WV, USA

PostPosted: Thu Jun 24, 2021 20:52    Post subject: Re: Some issues on r64885 build on NETGEAR WNDR4300 Reply with quote
kristianissimo wrote:

I've found some errors for this build, e.g.:

Security / Firewall tab - Log for firewall is on but Incoming Log and Outgoing Log is empty.


They do show up in dmesg.

_________________
Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate

Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r53562
Features in use: multiple VLANs over single trunk port

Linksys EA8500 WDS Station x2 - DD-WRT r53562

Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port.

OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.

Forum member #248
lexridge
DD-WRT Guru


Joined: 07 Jun 2006
Posts: 960
Location: WV, USA

PostPosted: Thu Jun 24, 2021 21:19    Post subject: Reply with quote
EA8500 R46885
Full reset when flashing to R46836, did not reset for 46885. Vanilla Firmware

I have several devices now that are not connecting. This is the error I am getting from all those unable to connect:
Code:

Jun 24 17:10:31 gatekeeper daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx MLME: auth request, signal -34 (Accepted)
Jun 24 17:10:31 gatekeeper daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Jun 24 17:10:31 gatekeeper daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx MLME: assoc request, signal -33 (Accepted)
Jun 24 17:10:31 gatekeeper daemon.notice hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: Could not set STA to kernel driver

After a reboot, I get this in dmesg:
Code:

[    8.349778] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA99X0/hw2.0/firmware-6.bin failed with error -2
[   10.269651] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/QCA99X0/hw2.0/firmware-6.bin failed with error -2
[   15.150186] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA99X0/hw2.0-vanilla/firmware-6.bin failed with error -2
[   19.583721] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/QCA99X0/hw2.0-vanilla/firmware-6.bin failed with error -2


EDIT: As read in another thread, disabling TurboQAM fixed it.

_________________
Linksys EA8500 (Internet Gateway, AP/VAP) - DD-WRT r53562
Features in use: WDS-AP, Multiple VLANs, Samba, WireGuard, Entware: mqtt, mlocate

Netgear R7800 (WDS-AP, WAP, VAP) - DD-WRT r53562
Features in use: multiple VLANs over single trunk port

Linksys EA8500 WDS Station x2 - DD-WRT r53562

Netgear R6400v2 WAP, VAP 2.4ghz only w/VLANs over single trunk port.

OSes: Fedora 38, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '94, never having owned a Windows PC.

Forum member #248
DD-WRT-Nub
DD-WRT Novice


Joined: 26 Sep 2016
Posts: 24

PostPosted: Fri Jun 25, 2021 17:58    Post subject: Reply with quote
Thanks for the reply guys. On this build I started applying settings right away rather than saving, when the initial issue happened and I tried restoring the backup with a working 1350 ACK-Timing made prior of bumping the Tx Power to 30dBm, it still crashed the 5GHz band and I deleted it assuming corruption. IMHO it doesn't make sense it's actually the ACK-Timing function causing my issue or Tx Power changes, it could be simply a bug when applying certain settings right away specially with these newer firmwares with the dual WiFi option of DD-WRT or Vanilla Firmware drivers.

ho1Aetoo, thanks again for testing on your router trying replicating the issue, if it doesn't happens to somebody else, my router is deteriorating somehow, although I don't have operational issues except what occurred during the 'experimentation'.

You're good kernel-panic69, we've our own personalities and different environments on our setup which msoengineer does says read the Wiki, but if lazy use the QCA BEST WIFI SETTINGS which in his testing gave him the most stability. My username or poor choice of words sometimes can give a certain impression. If remembering correctly, you preferred the old default value of 2250 which seems to be a middle ground, but I know you were trying to help suggesting recommendations. I feel msoengineer decided on recommending higher ACK-Timing values due to what brainslayer said, instead of nitpicking to a specific range due to the complexity an environment can bring.

Cheers!
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Fri Jun 25, 2021 18:15    Post subject: Reply with quote
My main router EA8500 has both radios w/ack time set at 900.
Up 20 days 7hrs w/ r46885 ... NO problems
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum