Trouble getting startmeup to wake the Server

[jksmurf]

I use /etc/mvpmc/ether-wake <MAC ADDRESS> in startmeup but my PC is determined not to wake.
Wondering if trying via my tomato based router for whuch I followed some script stuff many years ago, and works for remote waking, would work instead?

If so, what would the syntax be?

k.

[martint123]

It is either the sending side or the asleep that must be causing the problem.

Can you try waking it from another PC with WOLCMD?? http://www.depicus.com/wake-on-lan/wake-on-lan-cmd.aspx
Mine is like C:\tools\wolcmd 00196680d600 192.168.1.6 255.255.255.0

Is the above works then the sleeping PC is ok and your problem is with the NMT script.

If the above does not wake the PC then you have to delve into settings on it. Mine looks like this:- I don;t think I had to do anything in the BIOS, but there might be something hidden away in there.

[jksmurf]

Thanks Martin, that last pic is actually the depicus standalone gui utility, so I know that works remotely. Apparently 192.168.1.254 is a workaround to get to the broadcast address 192.168.1.255 (See http://www.justinmontgomery.com/wake-on-...ato-iphone).

This all works for me OK. But internally to my LAN I thought just the MAC address would work in startmeup. It doesn't seem to.

[Sykor]

Thanks Martin, that last pic is actually the depicus standalone gui utility, so I know that works remotely. Apparently 192.168.1.254 is a workaround to get to the broadcast address 192.168.1.255 (See http://www.justinmontgomery.com/wake-on-...ato-iphone).

This all works for me OK. But internally to my LAN I thought just the MAC address would work in startmeup. It doesn't seem to.

From my experience: WOL/MAC forwarding to broadcast ip from remote wakeup, direct LAN IP when waking from inside my network. Also, not sure if it changes anything, but the small app I use at home to wake, uses 0.0.0.0 as subnet mask for local waking, and 255.255.255.255 when send to a remote ip

[jksmurf]

From my experience: WOL/MAC forwarding to broadcast ip from remote wakeup, direct LAN IP when waking from inside my network. Also, not sure if it changes anything, but the small app I use at home to wake, uses 0.0.0.0 as subnet mask for local waking, and 255.255.255.255 when send to a remote ip

OK, ta. But how do you get the PCH script e.g. to wake it up ?

would Martin's wolcmd command line utility work equally well like this?

/etc/mvpmc/wolcmd <MAC ADDRESS> <IP ADDRESS> <0.0.0.0 as subnet mask> ?

[mvallevand]

Soccerdad wrote some instructions here http://forums.nextpvr.com/showthread.php...-Index.htm
that are quite good. ether-wake doesn't need a subnet mask for the broadcast, its gets that from the router which typically is 255.255.255.0

Martin

[jksmurf]

Hi Martin, is there some way to test what is being sent by the NMT script, to the router, to test which part is not working?

[mvallevand]

I guess you can telnet to your PCH and then run the same command using your MAC address

/etc/mvpmc/ether-wake 00:00:00:00:00:00

The program is very likely working ok and probably your router, but your PC, PCH and router do need to be on the same subnet. I'd check the script to see that it is set up according to soccerdad's instruction (it is in npvr.cgi not startmeup as you wrote earlier) especially the location of the file and the correct MAC and it that check out it is most likely your PC not responding to the WOL magic command.

Martin

[jksmurf]

it is in npvr.cgi not startmeup as you wrote earlier

Arrgghhh. ...I will try that ... I am still stuck in 2008 .... although you did write in the same thread "run it from your cgi script"

Martin123 wrote:

I put mine in startmeup (untouched from a very early version....) Substitute your MAC address

90% of the time the server wakes from hibernate before mvpmcx2 times out.
the other 10% of the time it drops back to the html menu and I have to do it again. From standby it is quick enough to start without problem (other than my USB tuner doesn't like standby).

Code:

#echo "Shell to mvpmcx2 "

/etc/mvpmc/ether-wake 00:0d:87:d2:66:0a

#remove the # from most appropriate line

# Analog TV settings

#/etc/mvpmc/mvpmcx2 -m ntsc &
#/etc/mvpmc/mvpmcx2 -m pal &

# HDMI/DVI settings

#/etc/mvpmc/mvpmcx2 -m 720 &
/etc/mvpmc/mvpmcx2  -o hdmi --emulate 192.168.1.5 &

http://forums.nextpvr.com/showthread.php...post311104

[mvallevand]

The location isn't important they both really make up the script, I was commenting on soccerdad's note. Regardless I am confident that ether-wake is still valid, and you need to focus on your network and PC's sleep configuration.

Martin