Posted: Fri Nov 18, 2022 10:28 Post subject: New Build - 11/18/2022 - r50906
Welcome to Atheros r50906 beta release thread for reporting, feedback to developers and 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 EA8500
DD-WRT v3.0-r50906 std (11/18/22)
Linux 4.9.333 #1366 SMP Wed Nov 16 16:53:38 +07 2022 armv7l
port 22 closed
boot back into r50841 -- all good again
yeahuh I had to do that from stupid webif commands shell
that was on both -- main router and other EA8500
#
Netgear WNDR3700 V4
DD-WRT v3.0-r50906 std (11/18/22)
Linux 3.18.140-d6 #158084 Fri Nov 18 06:49:07 +06 2022 mips
port 22 closed GUI ...install r50841 --all good again
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 probably untick "Prefer Algorithms for which a host key is known" or forget the HOST keys
If you have trouble connecting with WinSCP under Tools/Clean up Clear Cache
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Fri Nov 18, 2022 13:53 Post subject:
For those, like me, who don't get a whole lot out of the timeline of fixes applied recently, and who are always afraid to make a mess of ssh & key base access, here is how I succeeded after being told by my R7800 that port 22 is closed.
If you know all the ins and outs of ssh, keys and the various commands used, just skip ...
I did check from the documentation what ssh-keygen -R actually does, since generating new keys is not what you might want to do ... I have a slew of SBC's etc. using key based ssh access hither and thither and time-wise can't afford messing it up.
In my case the command needs to be repeated for both LAN IP and hostname (this is on a Linux Mint laptop):
arjen@HP430G5:~$ ssh-keygen -R 192.168.1.1
# Host 192.168.1.1 found: line 146
/home/arjen/.ssh/known_hosts updated.
Original contents retained as /home/arjen/.ssh/known_hosts.old
arjen@HP430G5:~$ ssh root@r7800.mdnet
Connection closed by 192.168.1.1 port 22
arjen@HP430G5:~$ ssh-keygen -R r7800.mdnet
# Host r7800.mdnet found: line 145
/home/arjen/.ssh/known_hosts updated.
Original contents retained as /home/arjen/.ssh/known_hosts.old
arjen@HP430G5:~$ ssh root@r7800.mdnet
The authenticity of host 'r7800.mdnet (192.168.1.1)' can't be established.
ED25519 key fingerprint is SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxx.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'r7800.mdnet,192.168.1.1' (ED25519) to the list of known hosts.
DD-WRT v3.0-r50906 std (c) 2022 NewMedia-NET GmbH
Release: 11/18/22
Board: Netgear R7800
==========================================================
Issues/Errors: IPv4 SSH seems broken. IPv6 working. I'm still investigating.
It does seem like IPv6 SSH changed with this release. The logs show my connection and then dd-wrt closes the connection. Using the same settings in PuTTY but changing the IP to v6 works.
Odd. Did SSH get changed in the firmware? _________________ Netgear R9000
DD-WRT v3.0-r55779 std (04/12/24)
Linux 4.9.337 #721 SMP Mon Apr 8 08:07:27 +07 2024 armv7l
Gateway, AP, DNSMasq, Clock 2000MHz
VAP on wlan1 for internet devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
CloudFlare, no SFE, SmartDNS, no QoS
2.4GHz: Vanilla, Airtime Fairness, NG-Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
5GHz: Vanilla, Airtime Fairness, AC/N Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
2 Netgear AX1800 WiFi Mesh Extenders
Xfinity 1.2Gbps/35Mbps
You could probably just have deleted your known hosts.
Not sure how that would happen. I was not doing anything in that folder, and I used SSH to load and write the new firmware. I could not reconnect once the new firmware came up _________________ Netgear R9000
DD-WRT v3.0-r55779 std (04/12/24)
Linux 4.9.337 #721 SMP Mon Apr 8 08:07:27 +07 2024 armv7l
Gateway, AP, DNSMasq, Clock 2000MHz
VAP on wlan1 for internet devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
CloudFlare, no SFE, SmartDNS, no QoS
2.4GHz: Vanilla, Airtime Fairness, NG-Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
5GHz: Vanilla, Airtime Fairness, AC/N Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
2 Netgear AX1800 WiFi Mesh Extenders
Xfinity 1.2Gbps/35Mbps
Joined: 18 Mar 2014 Posts: 12877 Location: Netherlands
Posted: Fri Nov 18, 2022 14:31 Post subject:
This worked for me
Quote:
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 probably untick "Prefer Algorithms for which a host key is known" or forget the HOST keys
If you have trouble connecting with WinSCP under Tools/Clean up Clear Cache
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 probably untick "Prefer Algorithms for which a host key is known" or forget the HOST keys
If you have trouble connecting with WinSCP under Tools/Clean up Clear Cache
That worked. Thank you! Why in the world did it just start after I did a router update??
...install r50841 --all good again
