search

padavanfirmware / rt-n56u

Padavan Firmware
http://padavanfw.net/
6 stars 4 forks source link

Wake On LAN - Working! (1.0.1.7f-p10) #91

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello, Thanks goes out for this amazing custom firmware!!!

Here is how I got Wake On LAN to work with my computer.  It will wake from 
Power Off, Standby and/or Hibernate depending on your Motherboard and Network 
Interface Card capabilities.  Before you even start you'll need to configure 
your BIOS and NIC accordingly (Enable Wake on LAN turn off Green Ethernet turn 
on Wake on magic Packet, etc.)  These next steps are specific to the Rt-n56u 
and using it with you're remote client.

Step 1-
Setup the computer you use to have a Static IP address. Either at the router or 
at the PC.

Step 2 - Port Forwarding Setup
First we need to "Port Forward" (not "Port Trigger") the Magic Packet to Port 9 
(OTHER) on the computer you want to Wake From Outside your LAN.  Go to 
Advanced->WAN->Port Forwarding and fill out the information like so:

Service Name:  Wake On LAN
Port Range:   (Leave Blank)
Local IP: The Static local IP of the computer you want to Wake from outside of 
your network (typically 192.168.1.?)
Local Port: 9
Protocol: OTHER
Protcol No. 0

Step 3 - Turn off Power Saving ON THE ROUTER!!!
Advanced > LAN> Ethernet Switch>  "Green Ethernet?" NO

Step 4 - Configure your remote Wake On Lan Client 
For your Wake on LAN client on your phone or other PC you'll typically need to 
know this information from your sleeping computer:

 External IP address (or assigned a domain name)

 MAC Address of your computer's NIC

 Local Network Subnet Mask: (Typically looks like 255.255.255.0)

In order to get my computer to wake I had to duplicate the last three numbers 
of my Subnet Mask (so in the Wake Client I typed  255.255.255.255) in order to 
get it to send the Magic Packet to my global IP address rather than the 
router's broadcast address.

Hope this helps.  I was e-mailing Asus tech support for like 3 weeks until I 
realized their crappy firmware doesn't even support WoL.  Their tech still 
thinks heir firmware supports it. It doesn't.

What version of the product are you using? On what operating system?
1.0.1.7f-p10, Windows 7

Original issue reported on code.google.com by TMason...@gmail.com on 7 Feb 2012 at 6:29

GoogleCodeExporter commented 9 years ago 
Hello! Thank you very much! It will work but not for everyone. The thing is 
that your network card can except not only WOL packets but other types. Usually 
the packet is being sent to broadcast address.

Original comment by ser...@soulblader.com on 7 Feb 2012 at 6:39

GoogleCodeExporter commented 9 years ago 
Hi TMason,

As far as I know WOL works in LAN but not from WAN (internet) on the Asus 
firmware.
This was the first test I made when I bought the router (with one of the 
initial firmwares). In the configuration you described if you send the WOL 
packet to 192.168.1.255 it should work too (it worked for me when I tested it). 
The problem is that Asus firmware doesn't allow to send the packet from 
internet to 192.168.1.255 (your network broadcast address). My advice is to try 
using this solution with the custom firmware made by the authors of this 
project and WOL.PY script (it works for me):

http://code.google.com/p/rt-n56u/issues/detail?id=30&can=1

or to wait for the next versions where WOL functionality will be embedded 
directly in the custom firmware (as the firmware developers promised in another 
post - #67).

Thanks,
Aurelian Iordache

Original comment by bluesurv...@gmail.com on 7 Feb 2012 at 9:04

GoogleCodeExporter commented 9 years ago 
Thanks for the info Aurelian.  As of now what I did in my first post works 
great (for me) without any scripting or any additional future changes to the 
firmware.

Original comment by TMason...@gmail.com on 7 Feb 2012 at 9:17

GoogleCodeExporter commented 9 years ago 
About the Asus support, you're not the only one disappointed, after months of 
emailing them their final answer was "Asus routers doesn't currently support 
WOL from internet" - I knew that already and I sent them two possible solutions 
to make it work. You understand how happy I was when I found this project, made 
my day :)

Are you saying that it works when sending the packet from internet too ?
I mean if you send the packet from a device not connected to your LAN (let's 
say a smartphone connected to internet through a mobile carrier, not through 
your router).
If it works please let me know 'cause then it's time for me to make new tests.

Thank you

Original comment by bluesurv...@gmail.com on 7 Feb 2012 at 9:32

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Guys, as I wrote, it works but with special hardware.
For example, I've got small server at home. there are 2 ethernet cards
Look at the interfaces: 

sudo ethtool eth0
...
    Supports Wake-on: g
    Wake-on: g
...

sudo ethtool eth1
...

   Supports Wake-on: pumbg
   Wake-on: g
...

So, for eth0 - is only possible to wake using broadcast.
For eth1 - there are many options, which could be configured (pumbg -letters)

If you have network card like eth1, then you can directly forward packets to 
your machine as it is described above

Original comment by d...@soulblader.com on 7 Feb 2012 at 10:19

GoogleCodeExporter commented 9 years ago 
With port forwarding setup as described in my first post and green ethernet 
switched off on my NIC and the RT-n56u Wake on LAN will indeed work from the 
internet too, and it works via my cell phone network as well.

I use Android app called Depicus Wake On LAN to wake from my phone and the GUI 
from Depicus to wake from other computers.

As long as you port forward to the computer as I described above (static ip, 
port 9, other etc.) and send the Magic Packet to your actual global IP and 
correct subnet mask it works from the internet for me. 

Just make sure when the Wake On LAN client sends the Magic Packet it is 
actually sent it to your actual Global IP, not your IP with .255 substituted 
for the last two digits.

I've done it over a dozen times now.  You must have the 1.0.1.7f-p10 firmware.  
The previous versions didn't work.

Good luck.

Original comment by TMason...@gmail.com on 7 Feb 2012 at 10:36

Attachments:

GoogleCodeExporter commented 9 years ago 
=) TMason818, that's great that it works for you and actually it works from the 
4th version (since it is possible to turn off 'GreenEthernet'). The think is 
that kernel doesn't allow to forward wan traffic to broadcast interface. In 
your case it's working only because you've got the network card like mine eth1, 
described above. The issue here - others have networking interface like mine 
eth0. It requires the 'magic packet', which should be sent from broadcast 
interface! In your case it can accept any packet

Original comment by d...@soulblader.com on 7 Feb 2012 at 11:43

GoogleCodeExporter commented 9 years ago 
I understand now. I'll check what is the equivalent of pumg in windows, who 
knows, maybe I have this kind of network cards too. Thanx for explanation, I 
wasn't aware about this difference between the network cards.

Original comment by bluesurv...@gmail.com on 7 Feb 2012 at 3:34

GoogleCodeExporter commented 9 years ago 
I think the options are common

man ethtool says:
---------------------
wol p|u|m|b|a|g|s|d...
              Sets Wake-on-LAN options.  Not all devices support this.  The argument to this option is a string of characters specifying which options to enable.
              p  Wake on phy activity
              u  Wake on unicast messages
              m  Wake on multicast messages
              b  Wake on broadcast messages
              a  Wake on ARP
              g  Wake on MagicPacket(tm)
              s  Enable SecureOn(tm) password for MagicPacket(tm)
              d  Disable (wake on nothing).  This option clears all previous options.

Original comment by d...@soulblader.com on 7 Feb 2012 at 3:56

GoogleCodeExporter commented 9 years ago 
Then, have anybody tried to configure VPN server. There is OpenVPN in wiki and 
VPNC in optware.
You can find a modile application, like this one 
-https://market.android.com/details?id=com.gmail.mjm4456.vpncwidget&hl=en

So, a mobile phone is connected to the internet and then is connected to home 
vpn, it is possible to send magic packets directly to home broadcast 
(192.168.1.255 for example, if ip - 192.168.1.1 and netmask CIDR is 24)

Original comment by d...@soulblader.com on 7 Feb 2012 at 4:10

GoogleCodeExporter commented 9 years ago 
My network card seems to only accept magic packets for wake events - at least I 
have it configured that way in Windows.  For example if I "ping" my PC it won't 
wake (from inside or outside my LAN), or if I try to connect my my PC via 
Windows Remote Desktop Connection it will not wake up.  It stays asleep 

However once I send the Magic Packet it will wake.  After that I can connect to 
my computer via Windows Remote Desktop Connection as long as I have correctly 
set up port 3389 (TCP) to forward to the local IP of the now awake computer.

So I imagine that my method won't work for people who have network cards that 
don't look for Magic Packets.

I have setup my computer to have a static IP via the LAN->DHCP Server->Manually 
Assigned IP around the DHCP List option in the router.

I haven't set up a VPN, only Windows Remote Desktop Connection.

This is the Android app I use from my cell network to wake the computer:

https://market.android.com/details?id=com.depicus.wakeonlan.free&feature=search_
result#?t=W251bGwsMSwxLDEsImNvbS5kZXBpY3VzLndha2Vvbmxhbi5mcmVlIl0.

Thanks again for the great firmware!

Original comment by TMason...@gmail.com on 7 Feb 2012 at 7:32

Attachments:

GoogleCodeExporter commented 9 years ago 
Unfortunately I failed in making OpenVPN to work... There must be something 
wrong in the configuration files,  I need to aquire more information when I 
find some free time. I'll double-check the steps from your tutorial too. About 
WOL I still believe the GUI solution is the best and I'll check the next 
version(s) hoping someday I'll find it there, you promised me you won't forget 
about it... :) I was thinking, do you have a way to accept donations ? Maybe 
you can place an PayPal button here ? 'Cause I  would like to donate for this 
project. I really want to help it.

Original comment by bluesurv...@gmail.com on 7 Feb 2012 at 7:47

GoogleCodeExporter commented 9 years ago

Original comment by d...@soulblader.com on 9 Feb 2012 at 7:59

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
To TMason818:

You attached the screenshot. All I wanted to say is that you're looking in 
wrong place... There is 'Advanced' tab. Find there 'wake on lan' in the list 
(sorry I'm not sure of names as I don't use windows and I'm writing what I 
remember )))
And there should be its value on the right. So in this list you can choose how 
your PC could be waked up...

Original comment by d...@soulblader.com on 17 Feb 2012 at 5:36

GoogleCodeExporter commented 9 years ago 
You're right, its in the "Advanced" Tab!

Original comment by TMason...@gmail.com on 17 Feb 2012 at 11:39

Attachments:

GoogleCodeExporter commented 9 years ago 
I can see some more 'wake options'... Could you pls check if there are some 
parameters, which your PC could be waked up? As I described before (only magic 
packet etc)
Btw, to make a screenshot of active window you can use ALT+PrintScreen (or 
CTRL+PrintScreen - I don't remember which is correct)

Original comment by d...@soulblader.com on 18 Feb 2012 at 1:54

GoogleCodeExporter commented 9 years ago 
There is another option I had to switch on in the BIOS of my motherboard (as my 
Network card is integrated into it) and there is an option for wake on a 
"pattern match" but I that's disabled.  I've included some more screen shots.

When using Windows, that's all the options given.

Original comment by TMason...@gmail.com on 18 Feb 2012 at 5:11

Attachments:

GoogleCodeExporter commented 9 years ago 
****Update:

Looks like the procedure in my first post causes conflicts with FTP access from 
outside LAN because it doesn't allow you to define an incoming port number.  
These settings (so far) seem to be working.  I'm doing more tests tomorrow.  

NEW GUIDE (BTW, ONLY TESTED WITH WIRED LAN THAT HAVE WoL CAPABILITIES THAT ARE 
ENABLED!!!):

Step 1-
First we need setup the computer you want to Wake On LAN to have a Static IP 
address. Set this up either with the router or at the PC. Google "setup static 
IP".

Step 2 - Port Forwarding Setup
Now we need to "Port Forward" (not "Port Trigger") the Magic Packet to Port 9 
(BOTH) on the computer you want to Wake From Outside your LAN.  Go to 
Advanced->WAN->Port Forwarding and fill out the information like this:

Service Name: Wake On LAN (or what ever you want)
Port Range:   9(Or Any available unused port that isn't 21:22)
Local IP:   The Static local IP of the computer you want to Wake from outside 
of your network (typically 192.168.1.?)
Local Port: 9
Protocol: BOTH
Protcol No. (Leave Blank)

Step 3 - Turn off Power Saving ON THE ROUTER!!!
Advanced > LAN> Ethernet Switch>  "Green Ethernet?" NO

Step 4 - Configure your remote Wake On Lan Client 
For your Wake on LAN client on your phone or other PC you'll typically need to 
know this information from your sleeping computer:

 External IP address (or assigned a domain name)

 MAC Address of your computer's Network Card

 Port Number: (9 from above unless you used a different number)

 Local Network Subnet Mask: (Typically looks like 255.255.255.0)

IMPORTANT: In order to get my computer to wake I had to duplicate the last 
three numbers of my Subnet Mask (in the Wake Client I entered 255.255.255.255) 
in order to get it to send the Magic Packet to my global IP address.  This is 
typical of many Wake On LAN apps.

Done. You can use an Android APP to wake your computer or find a web based 
"Magic Packet" sending form.

Troubleshooting:

*You may have to disable Green Ethernet and/or Energy efficient internet on 
your Network card

*This is only confirmed to work with WIRED LAN, Wireless NIC and USB adapters 
are whole other game.

Good Luck!

Original comment by TMason...@gmail.com on 18 Feb 2012 at 7:19

GoogleCodeExporter commented 9 years ago 
My dgl-4300 died yesterday after 6 years of flawless service. It worked great 
to wake up two computers on my network with that device. I was able to set 
255.255.255.255 in the settings to broadcast to the computers and waking them 
up. So I went out and bought a new router ie the Asus n56u. I foolishly took 
for granted that WOL would work... 

Well it didnt and after a while I found this custom firmware and the 
instructions in this thread. I flashed 1.0.1.7f-p11 (which states WOL is 
supported, would be nice with further explanation of settings and/or how) but 
still it will only work to wake upp the computers (via android) almost 
instantly after shutdown. Waiting a couple of minutes and it is no longer 
possible to wake them up. I have turned of the green ethernet on the networkd 
cards and also green ethernet in the N56 settings. I then portforward directly 
to the ip of the computer I want to WOL. 

But still no workie, it feels as if the green ethernet setting is not fully 
triggering since it only works just after shutdown. Any ideas? Will 
broadcasting be supported in the future?

Thanks for the great custom firmware by the way.

/P

Original comment by peter.r...@gmail.com on 19 Feb 2012 at 5:55

GoogleCodeExporter commented 9 years ago 
 @peter

The issues you are experiencing are very similar to the things I went through 
with the original Asus firmware.  If the computer wakes moments after you put 
it in in standby it sounds like you have everything setup right...

For testing purposes have you tried forwarding the port you send your magic 
packet to the OTHER, protocol 0 setting? (like in my first post).

Original comment by TMason...@gmail.com on 19 Feb 2012 at 9:01

GoogleCodeExporter commented 9 years ago 
Doesnt work with OTHER either. Dont really know what to do. I really use the 
WOL feature alot so this is quite annoying. It says that WOL is supported in 
p11, in what way, is it by turning off green ethernet? I guess broadcastingen 
will not be supported.

Any ideas? Is there anything else to look into? Could it be that green Ethernet 
is not really turned off in the router?

Thanks
/P

Original comment by peter.r...@gmail.com on 20 Feb 2012 at 12:01

GoogleCodeExporter commented 9 years ago 
Hi Peter,

I have WOL from WAN working on my router, please see the WOL.PY solution from 
issue #30 (you'll need one USB flash for this).
Just a note: you'll need to use VI command to edit the WOL.PY script and change 
192.168.2.255 to your network broadcasting address (I put there 192.168.1.255 
for my network). 
Here is the description of the issue and the solution (copied them from #30):

"Unfortunately system doesn't allow traffic forward from external interface to 
broadcast address on needed ports.
So the solution is a crutch with tiny python script.
you will need login to your router in terminal

cd /
wget -c -P /opt/tmp http://dl.dropbox.com/u/44733876/utilits/wol_handler.tar.gz
tar -zxvf /opt/tmp/wol_handler.tar.gz
ipkg update
ipkg install python27
/opt/etc/init.d/S20wolhndl start

You should send a packet to:

host - your-addr.dyndns.com
port 7070
hwaddr - your local machine name hwaddr

I've tested using laptop connected to internet via 3G modem. It seems to be 
working.

Please, check ones more your broadcast ip in /opt/bin/wol.py.
Note that such configation is insecure. Everybody can wake up your local 
machines from web...

forgot to say - need to create the rule for iptables.
http://my.router/Advanced_VirtualServer_Content.asp

Service Name       Port Range       Local IP        Local Port     Protocol    
  wol                7070         router_ip_addr       7070          UDP
                                 (not broadcast!)"

Original comment by bluesurv...@gmail.com on 20 Feb 2012 at 6:37

GoogleCodeExporter commented 9 years ago 
Peter, if is something not clear there please let me know, I'm ready to assist 
you as I was helped here by the developers of this project.

Original comment by bluesurv...@gmail.com on 20 Feb 2012 at 6:43

GoogleCodeExporter commented 9 years ago 
bluesurv, thank you very much for your comments,

the thing I wanted to add is - it is better to use ipkg tool to setup this 
script 
#ipkg install http://dl.dropbox.com/u/44733876/utilits/wol_handler.ipk

It will automatically write your broadcast address in /opt/bin/wol.py, and it 
will also install python as a depend packet.

Original comment by ser...@soulblader.com on 20 Feb 2012 at 9:42

GoogleCodeExporter commented 9 years ago

Original comment by d...@soulblader.com on 20 Feb 2012 at 9:43

GoogleCodeExporter commented 9 years ago 
Hi! Thanks alot for all the response. Not really great with unix/linux but I 
logged on with putty. After that I am a bit confused, can I edit the broadcast 
adress (guess it should be 192.168.1.255 for me) when wol.py is copied in 
/opt/bin/wol.py? Why do I need a usb flash? 

Nevertheless I began with running 
wget -c -P /opt/tmp http://dl.dropbox.com/u/44733876/utilits/wol_handler.tar.gz 
in the root which produced 

Connecting to dl.dropbox.com (107.20.135.4:80)
wget: can't open '/opt/tmp/wol_handler.tar.gz': No such file or directory

So since that was kind of final I tried running 
ipkg install http://dl.dropbox.com/u/44733876/utilits/wol_handler.ipk
which gave me
/ # -sh: ipkg: not found

By the way, if 
#ipkg install http://dl.dropbox.com/u/44733876/utilits/wol_handler.ipk 
was to work what would I more need to do to get it to work?

Thanks for your patience.

Original comment by peter.r...@gmail.com on 20 Feb 2012 at 10:50

GoogleCodeExporter commented 9 years ago 
Peter, please see the wiki - 
http://code.google.com/p/rt-n56u/wiki/HowToConfigureOptware in order to make 
optware work.

Original comment by d...@soulblader.com on 20 Feb 2012 at 11:19

GoogleCodeExporter commented 9 years ago 
Hey Peter here is some more information about setup with my method in comment 
20:

Firstly,
I set my Desktop to have a static IP by putting the MAC address of
it in the LAN-> DHCP Server-> Manually Assigned IP around the DHCP List. I 
don't think this makes a difference if you setup static IP another way but just 
in case.  Be sure to set Enabled Manual assignment to ->Yes.

I was able to recreate the problem you have with the computer only waking 
within 5 or so minutes if I adjusted some settings on the Advanced Tab of the 
Network Card properties on my PC.  If I set "ARP Offload" to disabled and/or if 
I set "Energy Efficient Ethernet" to Enabled.

The correct settings are:
ARP Offload = Enabled
Energy Efficient Ethernet = Disabled
Green Ethernet = Disabled

Once I set them as above my PC would wake correctly even hours later.  My 
understanding about ARP offload is that Routers typically flush the MAC 
addresses of devices after a few mins.  They won't know where to send packets 
unless that information is "Offloaded" so that's why that setting needs to be 
enabled.  The Energy Efficient Ethernet is similar to Green Ethernet.

Hope this solves the problem! Good luck.

Original comment by TMason...@gmail.com on 21 Feb 2012 at 5:00

GoogleCodeExporter commented 9 years ago 
Hi Peter,

You'll need USB flash connected to the router because there will be installed 
WOL.PY script, the Python interpreter and all the stuff.
Installing WOL didn't worked because Optware is not installed on your router 
("ipkg: not found"), as Soul said you may follow instructions from 
http://code.google.com/p/rt-n56u/wiki/HowToConfigureOptware to make it work. 
After that you don't need to edit WOL.PY anymore, just run:

http://dl.dropbox.com/u/44733876/utilits/wol_handler.ipk

I wasn't aware that Soul created wol_handler.ipk which when is installed will 
detect your broadcast address automatically and write it in WOL.PY script 
(thank you, Soul).
That step with edit of WOL.PY was necessary when wol_handler.ipk was not 
available.
Please let us know how it works and how we can help. As I said this solution is 
working, WOL works okay on my router. I was in the same situation when I bought 
my router (I'm using often WOL from internet) so I know how you feel. Then I 
found this project and received a lot of help from the developers to make WOL 
functional.

Original comment by bluesurv...@gmail.com on 21 Feb 2012 at 11:34

GoogleCodeExporter commented 9 years ago 
Sorry, correction, I meant:

#ipkg install http://dl.dropbox.com/u/44733876/utilits/wol_handler.ipk 

About the linux, don't worry, that was the first time when I worked with linux 
too... ;)

Original comment by bluesurv...@gmail.com on 21 Feb 2012 at 11:37

GoogleCodeExporter commented 9 years ago 
i have done all the steps and I have then executed 
wget -c -P /opt/tmp http://dl.dropbox.com/u/44733876/utilits/wol_handler.tar.gz 

ipkg update however will only result in 
/ # ipkg update
-sh: ipkg: not found

Dont really know what to do

Thanks
/P

@TMason, I cant find an option for ARP offload in my NIC settings :(

Original comment by peter.r...@gmail.com on 21 Feb 2012 at 6:26

GoogleCodeExporter commented 9 years ago 
To clarify, I have done all the steps on howtoconfigureoptoware wiki and hence 
also set yes in the router UI for optoware.

Original comment by peter.r...@gmail.com on 21 Feb 2012 at 6:42

GoogleCodeExporter commented 9 years ago 
I have the following when check

/opt/lib/ipkg # cat status
Package: uclibc-opt
Status: install ok installed
Root: /
Version: 0.9.28-13

Package: ipkg-opt
Status: install ok installed
Root: /
Conffiles: /opt/etc/ipkg.conf c77c1062ce4663610577d1eaef76a91f
Version: 0.99.163-10

What else is needed? Why do I get 
-sh: ipkg: not found

Original comment by peter.r...@gmail.com on 21 Feb 2012 at 6:49

GoogleCodeExporter commented 9 years ago 
Peter, try just to reboot the device.

Original comment by d...@soulblader.com on 21 Feb 2012 at 7:06

GoogleCodeExporter commented 9 years ago 
you're getting the error because the PATH is set incorrectly now. It will be 
set correctly after reboot 100%

Original comment by d...@soulblader.com on 21 Feb 2012 at 7:10

GoogleCodeExporter commented 9 years ago 
Rebooted, same error message. I dont know, maybe I have missed something.
i have no clue what is the problem.

Original comment by peter.r...@gmail.com on 21 Feb 2012 at 7:21

GoogleCodeExporter commented 9 years ago 
Re-doing everything. Will report back!

Original comment by peter.r...@gmail.com on 21 Feb 2012 at 7:40

GoogleCodeExporter commented 9 years ago 
Finally! Although not reaching all the way atleast one of my computers now 
starts with WOL.

Setup in router for portforwarding is
Service Name       Port Range       Local IP        Local Port     Protocol    
  wol                7070         router_ip_addr       7070          UDP

Which for some reason only works for one machine. Any clue to why this is?

Also, does the USB pin have to be plugged to the router from now on? If the 
router reboots do I need to restart /opt/etc/init.d/S20wolhndl or is that 
automatic?

Thanks for all the help, hopefully I will get the other computer to start as 
well!

THANKS!

/P

Original comment by peter.r...@gmail.com on 21 Feb 2012 at 9:29

GoogleCodeExporter commented 9 years ago 
The USB stick needs to stay plugged in from now on.

Original comment by TMason...@gmail.com on 21 Feb 2012 at 11:49

GoogleCodeExporter commented 9 years ago 
Peter, as TMason wrote the USB stick needs to stay plugged in. The router 
automatically invokes scripts in /opt/etc/init.d if they start with 'S' on boot 
or USB plug-in.
If USB disk is plugged in it calls script with 'start' option. If the 'Remove 
USB' button in web GUI is pressed or reboot is called it calls script with 
'stop' option

Original comment by ser...@soulblader.com on 22 Feb 2012 at 8:42

GoogleCodeExporter commented 9 years ago 
Also if you have set the script with 'wget' (not using ipkg). Please, do not 
forget to edit /opt/bin/wol.py and replace 192.168.2.255 with your broadcast ip.

Original comment by ser...@soulblader.com on 22 Feb 2012 at 8:44

GoogleCodeExporter commented 9 years ago 
Hi Peter,

I'm thinking about two possible reasons, you should double-check:
- The MAC addresses for the other computers are defined correct in the 
application you use to send WOL packet;
- The internal IP address where you send the WOL packet is your network's 
broadcast address (ex. 192.168.1.255 in my case), not the IP of the computer 
which is currently starting with WOL.

Original comment by bluesurv...@gmail.com on 22 Feb 2012 at 4:25

GoogleCodeExporter commented 9 years ago 
Thanks for all the help. Currently I can wake up my Htpc/Server from Wan which 
is the most important thing. My other computer cannot be woken by WOL. This is 
a bit strange since it worked when I had my other router. I have checked MAC in 
my applications and also Wol.py. I will look into the NIC settings of the 
computer that is not woken.

Anyways, thanks ALOT for all the help. I really appreciate it.

Br
/P

Original comment by peter.r...@gmail.com on 23 Feb 2012 at 5:31

GoogleCodeExporter commented 9 years ago 
You're welcome, Peter. You should continue to look for the problem, it MUST 
work for all your computers. Until you find the problem you may use your server 
to send the WOL signal to the other computers . I have one ASPX page on my web 
server where I can send WOL to all my network (just in case I need it), if you 
wish I can provide the C# code to generate and send the packet. Anyway, I'm 
glad I could help :)

Original comment by bluesurv...@gmail.com on 23 Feb 2012 at 6:38

GoogleCodeExporter commented 9 years ago 
I installed firmware rt-n56u_1.0.1.8d-p1 today. Is this firmware WOL compatible 
with windows 7x64? My NIC is Intel 82567V-2Gigabit.I enabled the NIC to "Allow 
this device to wake up the computer" and "Only allow magic packet to wake 
computer". Further I enabled the BIOS to "WOL in S5". I also set the router 
green ethernet switch to "no". I also set the router port forwarding Port 9 to 
192.168.1.50 (static ip of host computer). Is there anything else that this 
firmware requires to make WOL and WOW work. Any help very much appreciated!!
Berndt

Original comment by Berndt.S...@gmail.com on 25 Feb 2012 at 5:57

GoogleCodeExporter commented 9 years ago 
2 Berndt

as i think u dont need any special modification.
what am i did for WoL?
-downloaded an application for sending magic packets and that's all...
swich in green mode, i didn't changed any settings from beggining.
my PC's ethernet adapter also has default settings

do u have special software to wake up ur PC with a magic packet?

maybe this link will help u 
http://en.wikipedia.org/wiki/Wake-on-LAN#Magic_packet

Original comment by overdoz...@gmail.com on 25 Feb 2012 at 9:08

GoogleCodeExporter commented 9 years ago 

updated from 7f-p11 to the last firmware 8d-p1 - still no probs.

Original comment by overdoz...@gmail.com on 25 Feb 2012 at 9:40

GoogleCodeExporter commented 9 years ago 
Hi,

Yes I will keep trying, since as you say it should work for all computers. 
Another question, when updating to new firmware, do I have to do the procedure 
all over again or is everything kept on the usb flash, ie i just update and 
thats it?

BR
Peter

Original comment by peter.r...@gmail.com on 25 Feb 2012 at 10:54