Thank you again !
Good Luck !

I want to achieve the following:

The router should be able to wake up my Server (internal LAN) in a temporal sequence. For example every day at 6am. WOL is enabled on the server and works. (tested on tomato WOL GUI)
Is it possible to implement this on the router?

- WRT54GL (Tomato 1.28)
- HP ML310 Server

Thanks for your response!

Flashing a router with a third party firmware is always at your own risk. It is a good idea to reset the settings after flashing with a new firmware (I tend to do it before as well). So yes you will have to re-enter all you connection information.

The worst case scenario, is to brick your router and being forced to buy another one. I have flashed my old router many times (DD-WRT (many versions), OpenWRT (multiple times with multiple versions), Tomato and original). I brick my router once and it was not because of this process. I played with something I shouldn’t (related to file system) using OpenWRT…

So I guess it is quite safe but you have to make sure your hardware is compatible first and what are the known issues. Than if you think it is worth the risk, do the flashing during open hours so you can rush to the store to buy another one in case it goes wrong

Pascal.

Thanks

I finally made the test and to connect to the Tomato Web GUI through SSH is as simple as creating a tunnel where the destination is your router IP address on port 80.

Pascal.

I will check if I can connect to Tomato’s GUI through an SSH tunnel… never tried it.

Pascal.

Thanks for the tip. I modified the script to echo “/usr/bin/ether-wake -i eth1 xx:xx:xx:xx:xx:xx”> /tmp/home/root/wakeup-mycomputer.sh, rebooted the router, and now it works no problem.

BTW, is there a way to access Tomato’s GUI after the SSH tunnel is initialised?

If I understand well, if you connect to router web interface, you are able to wake-up the second laptop. But if you connect SSH, it doesn’t wake-up.

I am sure it is not because you are from the LAN. You are executing the wake-up command from the router, no matter you connected to the router from LAN or Internet…

the wake-up script just calls the ether-wake program passing the mac address. I have no WoWLAN computer and never had to do it wireless… The ether-wake documentation talks about a second parameter that is the network interface. I guess the default is the wired ones… (eth0)

see: http://linux.die.net/man/8/ether-wake

if you logon SSH onto your router and send this command
ifconfig

you should see a list of available network interface. You will have to find the one that is the wireless and modify the script this way:

/usr/bin/ether-wake -i [network interface] [mac address]
example:
/usr/bin/ether-wake -i eth1 01:02:03:04:05:06

where the mac address is the one from your second laptop and the interface is your router wireless interface.

Finally, I guess that Tomato GUI is probably sending the wake-up on all network interfaces. That would explain why it works from GUI and not from command line.

I hope this is helping you.
Pascal.

I’m having problems waking my laptop up remotely.

I have two laptops at home, both connected to the same router. I have configured the router and my second laptop for the WoWLAN feature; however, I can only wake up the second laptop via the web interface (Tools–>WOL in Tomato) on my first laptop. Whenever, I SSH into the router and run the command sh wakeup-mycomputer.sh nothing happens. I have set the script exactly as you have described with my MAC address. Can it be because I’m testing within the LAN?

Any feedback is much appreciated.

this way I don’t need the extra step of setting the executing right. Each time your router will restart, you will be forced to set the execution bit because the file will be re-created.

Pascal.

Its important to give the file executing rights with:
chmod uog+x wakeup-mycomputer.sh

Login to the router via ssh (or telnet) (or run this command by any other means)

arp -s 192.168.1.254 ff:ff:ff:ff:ff:ff

Then forward UDP port 9 to 192.168.1.254. Presto – you can now forward to the broadcast address (layer 2 – which is what really matters.)

This assumes your network is 192.168.1 with a netmask of 255.255.255.0, you can modify it to fit your needs.

Pascal.

In Windows XP, I had to set these advanced settings for the network card:

• Wake From Shutdown: on
• Wake-Up Capabilities: Magic Packet

In the Wake-Up Capabilities, I had the option of: Magic Packet, Pattern Match or Both. I took Magic Packet. I guess this choice relates to the OSI-2 Layer packet vs UDP Packet…

In my BIOS, I had to turn on “Wake-Up from Onboard LAN”.

After a soft-off of the computer, I wake it up through SSH connection on the router using this command:
/usr/bin/ether-wake MA:Cx:Ad:dr:es:s0

Pascal.

Thank you for the clarification. Indeed I am using Depicus tools at the moment and it works. But it would be nice to also have it working using the approach you outlined above. In this way I do not have to remind my MAC address all the time

The magic packet is sent on the data link or OSI-2 layer and broadcast to all NICs within the network of the broadcast address; the IP-address (OSI-3 layer) is not used.

So far, my conclusion is ether-wake sends a native magic packet on the OSI-2 layer as opposed to the depicus GUI tool that sends an UDP (OSI-4 Layer) packet that wraps the magic packet. Since the depicus WOL sniffer (I assumed that’s the software you used) checks the OSI-4 layer, it won’t see the packet sent by ether-wake.

In the windows device manager, my “Wake Up Capabilities” options are:

• Magic Packet
• Wake Up Frame
• Both
• None

I guess the Magic Packet vs Wake Up Frame relates to these 2 technics (OSI-2 Layer packet vs UDP Packet).

I have some WOL issues with a new machine I just bought. I guess it may be the same situation as you. I will try to take a look tonight so I can give more information if I end-up with success.

Pascal.

I am currently using the Wake on Lan gui from depicus. To get it working I added two lines to the admin>scrips>init tab to setup an static arp (read this on a forum) and forward port 7 to the static arp ip address.

I cannot wake up my PC using the WOL tool from tomato. I tried it while accessing the tomato gui using a laptop which is inside my network.

However, remote desktop via ssh connection works like a charm !!

Thnx