This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
ViperGeek,
Hi,
I just got the r7000 last week and have been testing it out. WOL is important to me and I know I have to set up a static arp entry to make it work.
I've run into a problem though. Even after running the 'new' telnetenable successfully I still can't access the router using telnet. I get an error saying "cannot open connection to host on port 23, connect failed when I try to telnet in.
The r7000 is on firmware v1.0.4.18_1.1.52.
Anyone able to telnetEnable on R7000 with lastest firmware? Post above is recent, I am using latest telnetEnable.exe x.x.x.x mac Firmware Version V1.0.4.30_1.1.67, but always getting
send failed: 10057
Tried all kinds of variations, mac with or with '-', ip without mac, old Gearguy ... no luck. mac ip verified with arp -a any suggestions?
You're running the exact version that worked for me in Post #28, so it's known to work in that release. The "send failed" error makes me think it's on the PC side, rather than the router side.
Two wild guesses off the top of my head:
Are you running as Administrator in Windows?
Can you try another NIC (network card) or even Wi-Fi?
Good luck. It should just "work" if you're running the latest version of telnetEnable.exe.
Anyone can tell me how to run the telentenable command from win 7 x64? It says its incompatible with 64 bit version. There is no link to a 64 bit version anywhere...
Anyone can tell me how to run the telentenable command from win 7 x64? It says its incompatible with 64 bit version. There is no link to a 64 bit version anywhere...
I'm running the new TelnetEnable.exe under Win 7 x64 and it works fine:
I'm running the new TelnetEnable.exe under Win 7 x64 and it works fine:
...
Click View Raw to save it as a .EXE.
Oh man, thanks a lot Dave. I just right clicked on the exe and "saved link as". Didn't realize I had to go into it and click and Raw. You learn something everyday. All is good, arp entry added and WoL working across the interwebs.
ViperGeek, I can see several posts made by you in this thread, and none deleted, so are you referring to a solution within this thread or another thread?
____________________________ Working on behalf of Netgear My name is Andy
ViperGeek, I can see several posts made by you in this thread, and none deleted, so are you referring to a solution within this thread or another thread?
Thanks for the response, Andy. My posts survived, but some of the juicy content was removed. For example, Message 25 had detailed steps for using TelnetEnable and creating static ARP entries, and Message 32 had possible solutions for another customer's problems that were seemingly removed. Finally, another user's quote of my original solution in Message 35 was converted to "...".
I'm OK with the edits if they were purposeful. It's just unfortunate that the most effective, viable solution was removed from this forum thread.
I can see that those posts are clearly truncated, but even though these forums allow limited editing now, an edited post is tagged as ‘Edited’. I can only assume that text was lost in the transfer, but it seems too selective. Short of me asking everyone capable of such edits, we will have to wait and see if someone has an answer, but my guess is that no one had an issue with what you had posted.
____________________________ Working on behalf of Netgear My name is Andy
Now that I've confirmed that the removal of my solution was a moderation, I'll try repeating it from memory (I was actually using this thread, bookmarked, to remember how to do it).
Open a DoS/Command Prompt on a PC directly connected to the same LAN and type 'telnetenable.exe <router-IP> <router-MAC> admin <admin-password>'
Telnet to the router
Type 'arp -i br0 -s x.x.x.x mm:mm:mm:mm:mm:mm' where x.x.x.x is the WoL destination IP address (not .255) and mm... is the WoL destination's MAC address
You should then have a static ARP entry in your router. Set up forwarding of port 9/UDP to your device you want to wake and it should work.
I can see that those posts are clearly truncated, but even though these forums allow limited editing now, an edited post is tagged as ‘Edited’. I can only assume that text was lost in the transfer, but it seems too selective. Short of me asking everyone capable of such edits, we will have to wait and see if someone has an answer, but my guess is that no one had an issue with what you had posted.
The original postings used [List] .. [/List] ie. numbered listing,. appears to be lost in transfer. Original postings have been updated with original content.
thanks for posting your solution again. It works excellent for me.
One more matter. Is it safe to keep telnet console open? Because once you open telnet console to router there is no way to disable it till router is rebooted, but when router is rebooting we are loosing all settings.
You're very welcome. I'm glad the solution worked for you as well.
There is a risk from keeping the telnet listener enabled, but the risk is mitigated by the fact that it's only accessible from the LAN side. Assuming you don't have a hostile local network and your LAN (including wireless) is fairly well controlled, you should be OK leaving telnet enabled. I'm unaware of a way to re-disable the telnet listener without rebooting.
This solution works perfectly. Thanks for sharing ViperGeek. The only issue is the new ARP PERM entry gets cleared every time the router is rebooted. Then I have to go back and re-do all the entries. This could be a hassle after a power failure. Are you aware of a way to save these settings permanently? I'm running an R7000 on 1.0.4.30_1.1.67 firmware
Are you aware of a way to save these settings permanently? I'm running an R7000 on 1.0.4.30_1.1.67 firmware
Hi MillerTime.
Unfortunately, I've found no way to have these commands auto-execute on boot. I messed around with /etc/init.d, but I believe the R7000 uses a volatile filesystem in that everything is recreated based on config at startup. Nothing written to /etc, for example, will survive a reboot either.
