I don't want to waste people's time on this unnecessarily.
I had just upgraded from a ~2 year old build a few days ago, with no reset.
Later today when I can (we're working from home, desktops are wired) I'll do a "reset to defaults" and reconfigure - to rule out anything lurking in the nvram being the problem - and update.
I don't want to waste people's time on this unnecessarily.
I had just upgraded from a ~2 year old build a few days ago, with no reset.
Later today when I can (we're working from home, desktops are wired) I'll do a "reset to defaults" and reconfigure - to rule out anything lurking in the nvram being the problem - and update.
Please report your findings! I am facing same issues but no time for a reset and reconfig (worried about wire guard client and server configs mainly)
R7000P here on 49418 with this log after a PC performed the first wifi connection of the morning to the 5GHZ and then all the devices on both radios proceeded to DHCP back into the network afterwhich the wifis appear stable:
Jul 13 12:32:00 192.168.1.1 kern warning kernel [574098.880479] dhd_flow_rings_delete_for_peer: ifindex 0
Jul 13 12:32:00 192.168.1.1 kern warning kernel [574098.885690] dhd_bus_flow_ring_delete_request :Delete Pending
Jul 13 12:32:00 192.168.1.1 kern warning kernel [574098.891447] dhd_bus_flow_ring_delete_request :Delete Pending
Jul 13 12:32:01 192.168.1.1 kern info kernel [574099.332948] CONSOLE: 601898.994 wl1: wl_open
Jul 13 12:32:01 192.168.1.1 kern info kernel [574099.337300] CONSOLE: 601899.022 wl1: wlc_enable_probe_req: state down, deferring setting of host flags
Jul 13 12:32:01 192.168.1.1 kern info kernel [574099.596612] CONSOLE: 601899.208 enable 1: q0 frmcnt 0, wrdcnt 0, q1 frmcnt 0, wrdcnt 0
Jul 13 12:32:01 192.168.1.1 kern info kernel [574099.604588] CONSOLE: 601899.208 wl1: link up (wl1)
Jul 13 12:32:01 192.168.1.1 kern info kernel [574099.609486] CONSOLE: 601899.219 wl1: Radio pwrsave not supported in non-mbss case yet.
Jul 13 12:32:01 192.168.1.1 kern info kernel [574099.617472] CONSOLE: 601899.257 wl1: wl_open
Jul 13 12:32:01 192.168.1.1 kern info kernel [574099.621814] CONSOLE: 601899.286 wl1: wlc_enable_probe_req: state down, deferring setting of host flags
Jul 13 12:32:01 192.168.1.1 kern info kernel [574099.876394] CONSOLE: 601899.472 enable 1: q0 frmcnt 0, wrdcnt 0, q1 frmcnt 0, wrdcnt 0
Jul 13 12:32:01 192.168.1.1 kern info kernel [574099.884477] CONSOLE: 601899.472 wl1: link up (wl1)
Jul 13 12:32:02 192.168.1.1 kern info kernel [574100.136218] CONSOLE: 601899.665 wl1: link up (wl1)
Jul 13 12:32:02 192.168.1.1 kern info kernel [574100.141086] CONSOLE: 601899.672 wl1: wl_open
Jul 13 12:32:02 192.168.1.1 kern info kernel [574100.145456] CONSOLE: 601899.684 wl1: Radio pwrsave not supported in non-mbss case yet.
Jul 13 12:32:02 192.168.1.1 kern info kernel [574100.153427] CONSOLE: 601899.731 wl1: wl_open
Jul 13 12:32:02 192.168.1.1 kern info kernel [574100.157795] CONSOLE: 601899.760 wl1: wlc_enable_probe_req: state down, deferring setting of host flags
Jul 13 12:32:02 192.168.1.1 kern info kernel [574100.412545] CONSOLE: 601899.946 enable 1: q0 frmcnt 0, wrdcnt 0, q1 frmcnt 0, wrdcnt 0
Jul 13 12:32:02 192.168.1.1 kern info kernel [574100.420837] CONSOLE: 601899.946 wl1: link up (wl1)
Jul 13 12:32:02 192.168.1.1 kern info kernel [574100.425894] CONSOLE: 601900.138 wl1: link up (wl1)
Jul 13 12:32:02 192.168.1.1 user info [nas] : daemon successfully stopped
Jul 13 12:32:03 192.168.1.1 user info [nas] : start nas lan
Jul 13 12:32:03 192.168.1.1 user info [nas] : start nas for wl0
Jul 13 12:32:03 192.168.1.1 user info [nas] : NAS lan (wl0 interface) successfully started
Jul 13 12:32:03 192.168.1.1 user info [nas] : start nas for wl0.1
Jul 13 12:32:03 192.168.1.1 user info [nas] : NAS lan (wl0.1 interface) successfully started
Jul 13 12:32:03 192.168.1.1 user info [nas] : start nas lan
Jul 13 12:32:03 192.168.1.1 user info [nas] : start nas for wl1
Jul 13 12:32:03 192.168.1.1 user info [nas] : NAS lan (wl1 interface) successfully started
Jul 13 12:32:03 192.168.1.1 kern warning kernel [574102.094505] dhd_flow_rings_delete_for_peer: ifindex 0
Jul 13 12:32:03 192.168.1.1 kern warning kernel [574102.099716] dhd_bus_flow_ring_delete_request :Delete Pending
Jul 13 12:32:04 192.168.1.1 kern info kernel [574102.170997] CONSOLE: 601901.833 wl1: link up (wl1)
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Thu Jul 14, 2022 1:50 Post subject:
It's been proven in the real world ad nauseum infinitum that the settings in that sticky are bunk and do not follow any published standards or driver spec. _________________ "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
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Thu Jul 14, 2022 16:56 Post subject:
Which is pre-swconfig implementation. Hard reset required, manually re-configure from scratch. Most likely gremlins. I am currently bug testing on several Broadcom devices because of all of these reported "issues" and am failing to find anything of merit. _________________ "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
also in general i don't use the apply button. i save changes then reboot the router.
* i did go through a spat where 5 GHz would restart at times. not the router. just the radio. wasn't sure what caused it. i did an nvram erase and i haven't seen it happen for at least the last 2 or so public builds.
Which is pre-swconfig implementation. Hard reset required, manually re-configure from scratch. Most likely gremlins. I am currently bug testing on several Broadcom devices because of all of these reported "issues" and am failing to find anything of merit.
Ok, I hope to have time to do that today. That's the "reset to default settings" option in the UI?
Also, how can I be in a better position to help when I do encounter issues? Is connecting/capturing the serial output from the router much benefit? I can set up a PI or something to capture that.
Ok, had time today to reset to defaults and reconfigure. Will report how things are going tomorrow. If it makes it beyond 8hrs up time, that'll be a good sign.
I flashed the device with the old configuration of 2.4 band in client mode, 5GHz band in AP mode and changed them both to AP mode with all of the normal Broadcom wifi settings that I have used, tested ad infinitum without issues. NO RESET. I realized that for some reason the WAN port was still assigned to the 2.4 radio, so I had to change that setting under the Networking tab. Outside of that, the only "issue" I had was how long it took to boot up and have webUI available, but I think I already know the cause of that and can rectify that without resetting. I had one of the TVs connected to it wirelessly streaming after things settled in until earlier this evening without a glitch as far as I know of (if it cut out during the night, I would've awakened). One thing I do have that is not "NIB" from point of purchase is I have a different power adapter that has a grounded plug and is 12VDC ~5A and I always use a reputable surge suppressor/filter for power source. _________________ "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
I did have problem connecting on 5g last night and restarted it. Current uptime 11 hours.
My settings aren't quite the same as before though - I enabled QAM1024 (disabled before), and beamforming settings are at their default of disabled (vs enabled previously). 5g throughput is lower (60 vs 200 Mb) than before. I want to get to 24hrs uptime before I change anything else...
Joined: 01 Dec 2021 Posts: 289 Location: Maryland, United States
Posted: Sat Jul 16, 2022 18:32 Post subject:
You may want to try using the SFE option with CFT and FA Flow Acceleration gives me a substantially faster Wi-Fi. I found that using CFT instead of SFE currently was somewhat buggy. Initially, it gave faster Wi-Fi, but after several minutes it slows down to slower than using SFE with the above Flow acceleration settings. With SFE with the above Flow acceleration settings, I get well over 300Mbps Wi-Fi and wired.
