Posted: Tue Mar 14, 2023 11:09 Post subject: New Build - 03/14/2023 - r52020
Welcome to Broadcom r52020 beta release thread for reporting, feedback to developers & community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery methods.
Avoid discussions, create threads for questions, general problems or use search; this thread is not for support.
List router model & version or revision, operating & wireless modes & exact filename/firmware image flashed.
CLI Flash: 'cd /tmp' then 'wget {file URL}' (httponly) or 'curl -O {file URL}' (http, https, ftp). 'write {file} linux' then 'reboot'.
Issues, observations, and/or workarounds reported:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Misc: stracetcpdumpwireshark.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, SB, WDS, Mesh) and applicable configurations to reproduce.
I don't think development of that App is current(?) and it may have to do with changes in SSL/dropbear/httpd. If the App doesn't support ED25519, then it's dead.
The issue should be directed to the App's support page:
Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Fri Mar 17, 2023 4:01 Post subject:
kernel-panic69 wrote:
I don't think development of that App is current(?) and it may have to do with changes in SSL/dropbear/httpd. If the App doesn't support ED25519, then it's dead.
The issue should be directed to the App's support page:
Router/Version: Netgear R7000
File/Kernel: DD-WRT v3.0-r52020 (03/14/23)
Previous/Reset: Reset
Mode/Status: Access Point only
Issues/Errors: Wifi devices do not want to connect to it when other APs using the same SSID are present
Factory defaulted the router. Flashed the 52020 version and factory defaulted again. Did the bare minimum config to get it on my network as an AP
- changed IP, gateway and DNS settings
- disabled WAN
- disabled DHCP
- added NTP server
- set SSID to "ddwrt x" for both 2.4 and 5GHz
Result: Devices will connect and operate correctly
Changed SSID to the house-wide SSID (single SSID on both 2.4 and 5GHz) so that this router could become available to any device.
Result: Devices do not want to connect to it. They always prefer devices further away with weaker signal strength.
Router/Version: Netgear R7000
File/Kernel: DD-WRT v3.0-r52020 (03/14/23)
Previous/Reset: Reset
Mode/Status: Access Point only
Issues/Errors: Wifi devices do not want to connect to it when other APs using the same SSID are present
Factory defaulted the router. Flashed the 52020 version and factory defaulted again. Did the bare minimum config to get it on my network as an AP
- changed IP, gateway and DNS settings
- disabled WAN
- disabled DHCP
- added NTP server
- set SSID to "ddwrt x" for both 2.4 and 5GHz
Result: Devices will connect and operate correctly
Changed SSID to the house-wide SSID (single SSID on both 2.4 and 5GHz) so that this router could become available to any device.
Result: Devices do not want to connect to it. They always prefer devices further away with weaker signal strength.
Used Windows and Android wifi clients for testing
Use different SSIDs for different bands and connect devices accordingly.
Use different SSIDs for different bands and connect devices accordingly.
I have done that other times for testing and that is not a solution. SSID per band is an ineffective way to run a Wifi network. Running multiple bands on one SSID works perfectly fine on other DDWRT versions eg v44213 and the Wifi clients optimally connect to the best signal. They know the signal strength better than me.
Use different SSIDs for different bands and connect devices accordingly.
I have done that other times for testing and that is not a solution. SSID per band is an ineffective way to run a Wifi network. Running multiple bands on one SSID works perfectly fine on other DDWRT versions eg v44213 and the Wifi clients optimally connect to the best signal. They know the signal strength better than me.
It works perfectly fine on this hardware with other versions of DDWRT. I'm not really sure what you are getting at
Most dual band or tri band devices will not choose the faster connection, they will connect to whatever they see first. this will cause performance issues for all connected devices on the network. Legacy 2.4Ghz devices will end up limiting higher performance 5.8Ghz devices capabilities and often lead to chaotic hard to diagnose performance and latency issues. While it appears to be a good idea to let the NIC decide which band to use in practice it is not and usually only ends in tears.