Wake On Lan not working in AP mode

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set Operation Mode of router to "Access Point Mode (AP)"
2. Allow a machine connected directly to one of the ASUS LAN ports to go to 
sleep.
3. Attempt to use the ASUS to send the WOL packet by using the router's web 
GUI. 
Alternatively, SSH into the router and run: 'ether-wake -b -i br0 
XX:XX:XX:XX:XX:XX'

What is the expected output? What do you see instead?

Even in AP mode, the ASUS should be able to send a magic packet to the 
broadcast address with the mac address of the machine to be woken. At the very 
least, it should be able to send this packet to all 4 LAN ports.

Instead, the web gui and ether-wake commands appear to execute correctly (no 
errors thrown), but the computer does not wake up.

What version of the product are you using? On what operating system?

ASUS rt-n56u, firmware  3.0.3.8-081. 

Please describe the problem as detailed as it's possible.
If you have connection problem, then syslog file is required. (please do
attach it as a file)
Note that if there will be a poor problem description the issue status will
be changed to 'Invalid'!

I have tried waking both Windows and Linux machines. I am able to wake these 
machines with another router (running Tomato firmware) on the same sub-net that 
is 2 hops away, so I can confirm that the machines in question are configured 
correctly for WOL. 

Original issue reported on code.google.com by mattbrit...@gmail.com on 16 May 2014 at 12:56

[GoogleCodeExporter]

I'm also having this issue. I'll have a look-see with wireshark later this 
evening.

Original comment by kitch2400 on 17 May 2014 at 8:50

[GoogleCodeExporter]

Scratch that, seems like a driver issue on my end. Unable to replicate this.

Original comment by kitch2400 on 17 May 2014 at 9:25

[GoogleCodeExporter]

Have you tryed to execute ether-wake from commandline of the router?

Original comment by d...@soulblader.com on 17 May 2014 at 7:11

[GoogleCodeExporter]

I did some testing today and have some additional information to add.

The RT-n56u is operating in AP mode and is downstream from my primary router. 
Using Wireshark I've found the following:

--Machines connected directly to the RT-n56u (wired & wireless) do not see 
magic packets sent from the RT-n56u.

--Machines connected directly to my primary router do see magic packets sent 
from the RT-n56u.

--If I use a WOL utility from a PC connected directly to the RT-n56u, magic 
packets sent by that utility are seen by all other machines on the network, 
regardless of which router they are connected to.

--I've tried using ether-wake from the command line of the router, and the 
results are the same as when using the GUI.

It's almost like the magic packets from the RT-n56u are going to the upstream 
router only and not to any of the other LAN ports on the RT-n56u. This may be 
by design, but I was under the impression that the broadcast packet would go 
out to all 4 LAN ports. Also, I don't understand why a magic packet sent by a 
PC connected to the RT-n56u would be treated any differently from one sent 
directly from the RT-n56u.

Original comment by mattbrit...@gmail.com on 17 May 2014 at 8:49