[BrainSlayer]

[hurleyp]

Firmware: v3.0-r47256 std (08/25/21)
Router/Version: Netgear R7000
Kernel: Linux 4.4.281 #3917 SMP Tue Aug 24 03:08:40 +07 2021 armv7l
Previous: v3.0-r47206 std (08/19/21)
Mode/Status: AP wired and wireless / Up and running for 21 hours
Reset: Soft boot before and after upgrade
Temperatures: CPU 62.5 °C / WL0 47.3 °C / WL1 52.2 °C
Issues/Errors: Nothing significant

Updated via webif. No 'nvram erase' this time, last one was in July 2018 (r36325).

Upload and Download speeds are to ISP spec. Nothing unexpected in the syslog.

Current basic R7000 setup (subject to change of course):
- Static WAN IP
- Shortcut Forwarding Engine: CTF, Flow Acceleration: Disabled
- STP - Enabled
- IPv4 only, both WAN and LAN
- LAN DHCP Enabled
- Wireless: AP, Regulatory Domain = CANADA, wl0 Mixed (ch. 6), wl1 AC/N-Mixed (ch. 36, VHT80), AES
- 1 wireless VLAN on wl0
- SNMP disabled, SSH enabled, Telnet disabled
- Firewall enabled, Log Level high
- Syslog: to local server. klogd: disabled.
- USB support - Off
- No custom scripts
- No: ttraf, Tor, VNC, Zabbix, VPN, Radius, OpenVPN
- No: UPnP, DMZ, QoS
- No: Samba, CIFS, JFFS2, miniDLNA, Entware, Optware

[itwontbewe]

Router Model: Netgear R7000P
Firmware Version: DD-WRT v3.0-r47256 std (08/25/21)
Kernel Version: Linux 4.4.281 #3923 SMP Wed Aug 25 02:51:09 +07 2021 armv7l
Reset: no
Operating Mode/Setup: Gateway / AP Unbound JFFS2
Status: running well. thanks BS and dd-wrt community

[dwardo]

Router/Version: TP-Link Archer C9 v1
File/Kernel: archer-c9v1-webflash.bin/
Previous/Reset: r47040/no (because r47206 and r47225 lead to bootloop after a clean reboot)
Mode/Status: Gateway/2.4GHz & 5GHz AP/Openvpn server/Wireguard server/DHCP server/DNS Server/Port forwarding/ipv4 & ipv6/CTF+FA
Issues/Errors:

* Cannot access anything but the 1rst access restriction --> has already been reported and announced to be fixed in next build.
* not "really" an issue : Had to reapply ctf+fa (although I had it before upgrade and new test detected hardware was capable (i.e. ctf_fa_cap was set to 1 on first boot). --> Maybe this could be done automatically instead of the user having to redo it...