[bugreport] Wake on lan (WOL) broke on 384.3

[MikeBenson]

Hi,

I have a RT-AC68U and upgraded from 380.69_2 to 384.3 and WOL seems to have broken:

When running this nothing happens:

admin@RT-AC68U-8140:/tmp/home/root# /usr/sbin/ether-wake B8:AE:ED:7E:AA:CC
admin@RT-AC68U-8140:/tmp/home/root#

But when running the command from another host in the network, the machine does start up.

Let me know if I can provide more info or put this post in the wrong place.

 

[skeal]

Hi,

I have a RT-AC68U and upgraded from 380.69_2 to 384.3 and WOL seems to have broken:

When running this nothing happens:

admin@RT-AC68U-8140:/tmp/home/root# /usr/sbin/ether-wake B8:AE:ED:7E:AA:CC
admin@RT-AC68U-8140:/tmp/home/root#

But when running the command from another host in the network, the machine does start up.

Let me know if I can provide more info or put this post in the wrong place.

How about the wake on lan feature in the webui?

 

[MikeBenson]

How about the wake on lan feature in the webui?

That does actually work!

I wonder what command it uses, /usr/sbin/ether-wake did work in the old version.

 

[MikeBenson]

I now found that this does work:

/usr/sbin/ether-wake -i br0 B8:AE:ED:7E:AA:AA


The receiving machine is connected via LAN not WLAN. So eth0 should still be the right interface just like before right?


admin@RT-AC68U-8140:/jffs/test# /usr/sbin/ether-wake
BusyBox v1.25.1 (2018-02-13 16:08:41 EST) multi-call binary.

Usage: ether-wake [-b] [-i IFACE] [-p aa:bb:cc:dd[:ee:ff]/a.b.c.d] MAC

Send a magic packet to wake up sleeping machines.
MAC must be a station address (00:11:22:33:44:55) or
a hostname with a known 'ethers' entry.

-b Broadcast the packet
-i IFACE Interface to use (default eth0)
-p PASSWORD Append four or six byte PASSWORD to the packet
admin@RT-AC68U-8140:/jffs/test#
admin@RT-AC68U-8140:/jffs/test#
admin@RT-AC68U-8140:/jffs/test# ifconfig
br0 Link encap:Ethernet HWaddr 30:8A:4A:C3:82:43
inet addr:10.0.5.1 Bcast:10.0.5.255 Mask:255.255.255.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:13751 errors:0 dropped:0 overruns:0 frame:0
TX packets:16278 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1781967 (1.6 MiB) TX bytes:10721871 (10.2 MiB)

eth0 Link encap:Ethernet HWaddr D4:BE:39:84:A4:0A
inet addr:191.133.3.24 Bcast:193.148.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1597218 errors:0 dropped:0 overruns:0 frame:0
TX packets:1584815 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1592320263 (1.4 GiB) TX bytes:1564621473 (1.4 GiB)
Interrupt:179 Base address:0x4000

 

[RMerlin]

The receiving machine is connected via LAN not WLAN. So eth0 should still be the right interface just like before right?

No. eth0 is the WAN interface, br0 is the LAN bridge. You should always use br0.