NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RKLEVY
Sep 28, 2020Aspirant
Telnetenable on Orbi RBR50--Firmware 2.7.0.70
Further to the discussion at https://community.netgear.com/t5/Orbi/PERMANENTLY-ENABLE-TELNET/m-p/1812682 I found that telnetenable.exe does not seem to work with Firmware update 2.7.0.70. Got the er...
FURRYe38
Sep 28, 2020Guru - Experienced User
Well for one the built in telnet feature on the debug.htm page works already. Not sure if external apps are needed.
RKLEVY
Sep 28, 2020Aspirant
I am aware that the telnet switch on the debug.htm page is working ..but once you reboot, it resets to it's default setting of NO "telnet". This was the subject of the prior post (link included in my recent post here). That's why TelnetEnable was needed to reset the switch each time a reboot script was automatically launched. The script enabled the telnet service on the router and then executed a reboot sequence (which unfortunately resets the telnet service to inactive). This script worked until the most recent firmware...apparently a change was made in the new firmware to the telnet service so that port 23 is no longer opened.
- FURRYe38Sep 28, 2020Guru - Experienced User
Maybe NG closed this backdoor.
- Mikey94025Jan 23, 2021Hero
I agree, I think the telnetenable backdoor has been closed or modified. I have been trying the various versions of telnetEnable against my RBR50 (latest firmware V2.7.2.102) and my RBR850 (latest firmware V3.2.17.12_1.4.14). It does not work and telnet is still closed for both my Orbi AC and Orbi AX.
For Orbi AC we can still enable telnet via the orbilogin.com/debug.htm web portal, but for Orbi AX the Enable Telnet toggle was removed long ago so I don't see any other way to get in.
- RKLEVYJan 23, 2021Aspirant
Thanks...looks like it's now confirmed...that's an unfortunate change but I have to say I've not been needing to reboot with the latest firmware (although I might like to)...it seems pretty stable and I've had no issues with it. Maybe NG will decide in it's wisdom to either update telnetenable to work with the current/future firmware or to install a toggle in the firmware that locks telnet to be active after reboot.
We'll see :smileyhappy: