Posted: Sat Apr 17, 2021 9:31 Post subject: New Build - 04/17/2021 - r46380
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and device specificrecovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Issues, observations, and/or workarounds reported:
• DNScrypt 1.95 can still be used in the GUI, but v2 (not compatible) requires Golang and thus Entware. #6246
• WDS does not work on Broadcom ARM devices(only MIPS<->MIPS) & bridge modes on k4.4 devices may sometimes work
in some configurations for certain builds but are not supported by the bcmdhd driver. Use client or repeater instead.
• VAPs not working at bootfixed for unbridged VAPs in40562 - 40566. Effective startup commandsdiscussion thread is here.
• If start-up scripts do not work from USB add a delay, e.g. wait script or 'sleep 25'.
• Broadcom ARM devices if 5 GHz channels are missing, via Telnet/SSH: 'nvram set brcm_unlock=1' 'nvram commit' 'reboot'
• Show us your findings with steps to reproduce, configuration, output, logs and important information below!
Important:
• For issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, klog, serial, strace, tcpdump, wireshark etc.
• Any firewall NAT or WAN issues, show output: 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and /tmp/.ipt file.
• Search SVN tickets & discuss in forum before opening. Before reporting: reset & manually set up, not restore from a backup.
• Please include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) & relevant configuration information.
Joined: 18 Mar 2014 Posts: 12922 Location: Netherlands
Posted: Sat Apr 17, 2021 9:44 Post subject:
Router Model: Netgear R6400v1
Firmware Version: DD-WRT v3.0-r46380M Community Build (04/16/21)
Kernel Version: Linux 4.4.265 #1 SMP Fri Apr 16 20:29:20 CEST 2021 armv7l
Upgraded from: DD-WRT v3.0-r46329M Community Build
Reset: No not this time
Status: Up and running for 24 hours, basic setup as Gateway, static leases, Advanced routing, Port Forwarding, IPv4, DynDNS, 2.4 GHz and 5 GHz.
Running WireGuard tunnel to own WG server for site-to-site connection.
Running OpenVPN client to KeepSolid.
Router/Version: Netgear R7000
File: netgear-r7000-webflash.bin
Firmware: DD-WRT v3.0-r46380 std (04/17/21) (prev. DD-WRT v3.0-r46329 std (04/13/21))
Kernel: Linux 4.4.265 #2518 SMP Fri Apr 16 08:29:28 +07 2021 armv7l
Mode: Gateway, Wifi disabled, Wireguard for external access, WAN to DSL, Keep Alive reboot 5:00 in the morning
Reset: No
Status: Ok, 4:56 up.
Router/Version: Asus RT-N66U
File: dd-wrt.v24-46380_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r46380 big (04/17/21) (prev. DD-WRT v3.0-r46329 big (04/13/21))
Kernel: Linux 4.4.265 #8257 Sat Apr 17 11:32:49 +07 2021 mips
Mode: Gateway, Wifi disabled, WAN disabled, Wireguard Endpoint for external VPS, connected via LAN to WRT1900ACS v2, Keep Alive reboot 6:05 in the morning
Reset: No
Status: Ok, 4:55 up.
are you sure it's after login?
For me, this is the sequence of events that I observe:
On PC: SSH to router, tail -f /tmp/var/log/messages , no login error message yet
On mobile phone: open ddwrt control panel main page --> info page shows up, no password required & no error in SSH on PC yet.
On mobile phone: click on any other page of ddwrt (setup/wireless/services/security/management...) --> login prompt shows up & error message appears in SSH on PC (same error as you posted)
On mobile phone: enter username & password --> can access the page & no error message in SSH on PC
are you sure it's after login?
For me, this is the sequence of events that I observe:
On PC: SSH to router, tail -f /tmp/var/log/messages , no login error message yet
On mobile phone: open ddwrt control panel main page --> info page shows up, no password required & no error in SSH on PC yet.
On mobile phone: click on any other page of ddwrt (setup/wireless/services/security/management...) --> login prompt shows up & error message appears in SSH on PC (same error as you posted)
On mobile phone: enter username & password --> can access the page & no error message in SSH on PC
These error messages are 'normal'. This has been 'normal' for almost 3 years now since I've been here. Probably been 'normal' for much longer than that. Why do we post information about 'normal' syslog entries? _________________ "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
These error messages are 'normal'. This has been 'normal' for almost 3 years now since I've been here. Probably been 'normal' for much longer than that. Why do we post information about 'normal' syslog entries?
These error messages are 'normal'. This has been 'normal' for almost 3 years now since I've been here. Probably been 'normal' for much longer than that. Why do we post information about 'normal' syslog entries?
Can you please help me understand how this is considered normal?
This entry suggests incorrect credentials are supplied to router while it is not true. Maybe I am missing something obvious here, no?
These error messages are 'normal'. This has been 'normal' for almost 3 years now since I've been here. Probably been 'normal' for much longer than that. Why do we post information about 'normal' syslog entries?
Can you please help me understand how this is considered normal?
This entry suggests incorrect credentials are supplied to router while it is not true. Maybe I am missing something obvious here, no?
The point is the error log appears when the login prompt shows up, not after you have successfully logged in.
My wild guess is that when you open ddwrt page, the web browser tries to auto login with the previously stored cookie, but for some reason, ddwrt doesn't accept that old cookie (session timeout? router restarted?), writes the error log, then asks to re-authenticate. There's no error log for a successful login at all.