I’ve only been using Mikrotik for about six hours so user error is definitely a possibility.
Using an RB450G running 3.30 in a “boring NATing router” configuration with PC A and PC B plugged into ports 4 and 5, and the internet plugged into port 1.
The desirable outcome is to be able to log into the RB450, run a script and WoL either of the PCs. PC A can WoL PC B using the Linux wakeonlan script and vice versa.
If I wireshark on A, I get nothing when I try to WoL A from the RB450.
But if A tries to WoL itself, I get:
The packet is a bit ill-formed (it seems to stutter-start a couple of times), but is close enough to get the job done.
Otherwise, I have to say I’m impressed with the RB450G and Mikrotik thusfar.
it’s an IP broadcast, this is why the packet will be sent out the gateway interface. if your PC is connected elsewhere, it will not work unless you specify the output interface in the RouterOS WOL command. then it will be sent as aan ethernet broadcast, out the correct interface.
I had an inkling it was something along those lines. The docs on the wol function are just scant enough to be vague.
So, in this case, I have gateway/internet on ether1, and ether2-5 bridged. Let’s say the computer I want to wake is on ether5 at 192.168.88.10. How would I properly format the WOL command?
I don’t think that will help, WOL is a new feature, and interface selection has only recently been introduced Downgrade will only get rid of WOL entirely.
Downgrade will only get rid of WOL entirely.