> Anyone know how to enable telnet on the RAX75? [...]
Not I. Someone who has touched one might have more/better information.
> [...] The telnetable.bin trick [...] does not work...
Netgear appears to have been removing that (undocumented, unsupported) feature from various models in recent times. Whether that's intentional or just another blunder is not obvious. See, for example:
Yeah, I saw that article as well as a few others. My creds, mac address and ip are correct for telnetenable.bin. If tney are going to stop supporting it, thejr firmware is useless to me. I'm wanting to run dnsmasq on it more than anything.
I alsoopened a case - suppose I'll have to wait and hope 🙂
- the mac address as denoted on the router itself (underneath)
- hit the router with nmap: that provided an addtional mac address
- the internet mac address
I also tried using colons and no colons in the mac addresses when issuing telnetenable.bin
> When did they _start_ "supporting it"?
I am not suggesting it was ever supported. More so, I have two R9000s that do have this capability (I've since moved those over to DD-WRT). My point is, I am somewhat hobbled using their stock firmware. The AX75 is not supported on the DD-WRT site (no mention in the router database...nor do I see it under the beta downloads at ftp.dd-wrt.com/betas/2020)...
> Please report any interesting results.
Most definitely! I'm working around the firmware via my R9000s (as in putting my required functionality on them). Still rather annoying...
I must confess I do use my routers like computers and have a bunch of wireless client bridges around my home (long story). Having the ability to run chroot'd debian and/or entware is very nice...
The one you want is the LAN MAC address (not WAN/Internet): ADVANCED > ADVANCED Home : Router Information : LAN Port : MAC Address
> I also tried using colons and no colons in the mac addresses when > issuing telnetenable.bin
If you want to keep the colons, you can use the program which I modified: http://antinode.info/nte/ So far as I know, others are too lame to allow them.
> I am not suggesting it was ever supported. [...]
"stop supporting it" certainly suggested that to me. Hard to stop something which was never started.
> [...] Having the ability to run chroot'd debian and/or entware is very > nice...
I suspect that Netgear dislikes the resulting support problems. Releasing firmware with fewer defects/shortcomings would help, but that's more work.
Update on my situation: I spoke to "technical" support (note the quotes) - took a few emails and then finally I called after hearing nothing back. As far as I can tell, based upon the "technical" support person, enabling telnet is not possible.
Is it me, or does Netgear have the worst (or one of the worst) "technical" support departments? How embarrassing for Netgear as a company.
