Posted: Thu Jan 12, 2023 13:18 Post subject: New Build - 01/12/2023 - r51288
Welcome to Broadcom r51288 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.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
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.
Linksys E2500
DD-WRT v3.0-r51288 mega (01/12/23)
Linux 4.4.302-st28 #20908 Thu Jan 12 05:38:23 +06 2023 mips
'dd-wrt.v24-51288_NEWD-2_K3.x_mega.bin'
scp 'firmware.bin' installl over r51184
used as a WAP --- all ok
---
EDIT:
he's still all good
Uptime 2 days, 6:08
Last edited by mrjcd on Sat Jan 14, 2023 23:13; edited 1 time in total
Router/Version: Asus RT-N66U
File: dd-wrt.v24-51288_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r51288 big (01/12/23) (prev.DD-WRT v3.0-r51275 big (01/09/23))
Kernel: Linux 4.4.302-st28 #20904 Thu Jan 12 05:32:58 +06 2023 mips
Mode: Gateway, SFE disabled, 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: Installed ~ two hours ago, OK.
Firmware: v3.0-r51288 std (01/12/23)
Router/Version: Netgear R7000 Kernel: Linux 4.4.302-st28 #8500 SMP Thu Jan 12 03:47:54 +06 2023 armv7l
Previous: v3.0-r51184 std (01/06/23)
Mode/Status: AP wired and wireless / Up and running for 1 day
Reset: Soft boot before and after upgrade
Temperatures: CPU 58.0 °C / WL0 45.4 °C / WL1 50.8 °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 (500/500 Mbps).
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
- Not currently forwarding any ports
- Wireless: AP, Regulatory Domain = CANADA, wl0 N/G 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 _________________ Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7
Posted: Mon Jan 16, 2023 6:13 Post subject: Netgear R9000
Router/Version: Netgear R9000 File/Kernel: DD-WRT v3.0-r51288 std (01/12/23) Previous/Reset: r43324 / Reset to factory default during flsh Issues/Errors: Can not connect via ssh to router, telnet is working. Tried ssh with password and Private Key
See attached the settings in the service tab.
Is this a bug, or what I think is more realistic, am I doing something wrong. With previous version SSH was available.
But in old version there were only settings sshd = enable, ssh tcp forwarding = disable, password login = enable
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Mon Jan 16, 2023 7:19 Post subject: Re: Netgear R9000
k3067e3 wrote:
Previous/Reset: r43324 / Reset to factory default during flsh
[b]Issues/Errors: Can not connect via ssh to router, telnet is working. Tried ssh with password and Private Key
Your SSH client needs to accept the new server/host key (e.g. ".ssh/known_hosts"), because its format was changed to the shorter ed25519(ecDSA). _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Your SSH client needs to accept the new server/host key (e.g. ".ssh/known_hosts"), because its format was changed to the shorter ed25519(ecDSA).
I think I am to stupid for this.
Is there any chance just to use user/password?
I have new installation of raspbian, I delete known_hosts file in .ssh directory
I connect an DD-WRT Access Point Using older build 43324.
I type in the terminal ssh 10.76.0.252 -l root, I get the question if I want to connect, I types yes, then I am prompted for Password, which I enter and everything fine.
When I do this with the router
ssh 10.76.0.252 -l root there is no password prompt, I just get permission denied (publickey).
After I tried this, there is an additional line in the known_hosts with ssh-ed25519 but then a different string as in the router GUI.
I also tried with putty and I could not get it running
I have latest version of putty 0.78.
I have downloaded the private key after generating from router GUI, id_ed25519.ssh
I open PuttyGen, load the .ssh file and save it as privatekey id_ed25519.ppk
I open putty, load my existing config of the Router, and selected the ppk file.
Joined: 26 Mar 2013 Posts: 1858 Location: Hung Hom, Hong Kong
Posted: Mon Jan 16, 2023 9:51 Post subject:
k3067e3 wrote:
When I do this with the router
ssh 10.76.0.252 -l root there is no password prompt, I just get permission denied (publickey).
After I tried this, there is an additional line in the known_hosts with ssh-ed25519 but then a different string as in the router GUI.
I also tried with putty and I could not get it running
I have latest version of putty 0.78.
I have downloaded the private key after generating from router GUI, id_ed25519.ssh
I open PuttyGen, load the .ssh file and save it as privatekey id_ed25519.ppk
I open putty, load my existing config of the Router, and selected the ppk file.
You can always enable Password Login in Services->Secured Shell, fix your key problem then disable it again. When doing Password Login, your SSH client should NOT supply the private key. And remember, you always login as root@dd_wrt_router_ip_address when using SSH.
Did you also forget to set the ownership of the private key file to only your Windows account? Look at the error message carefully. _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Your SSH client needs to accept the new server/host key (e.g. ".ssh/known_hosts"), because its format was changed to the shorter ed25519(ecDSA).
I think I am to stupid for this.
Is there any chance just to use user/password?
I have new installation of raspbian, I delete known_hosts file in .ssh directory
I connect an DD-WRT Access Point Using older build 43324.
I type in the terminal ssh 10.76.0.252 -l root, I get the question if I want to connect, I types yes, then I am prompted for Password, which I enter and everything fine.
When I do this with the router
ssh 10.76.0.252 -l root there is no password prompt, I just get permission denied (publickey).
After I tried this, there is an additional line in the known_hosts with ssh-ed25519 but then a different string as in the router GUI.
no idea what you are doing... but the message "permission denied (publickey)" says that password login is disabled and there is no matching private key on your client!
So in the tab "Services" activate password login and press "apply".
Or download the private key and copy it with the appropriate rights in ~/.ssh
Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Mon Jan 16, 2023 11:08 Post subject:
If you have trouble connecting with SSH then download the latest Putty and make sure under SSH/Host keys to move ed25519 to the top and untick "Prefer Algorithms for which a host key is known" or forget your known HOST keys (the fingerprints) from your client.