The Firewalla creates a virtual network in the 192.168.99.x range for which it handles DHCP and does monitoring, all the devices in question are on this virtual network.
The Firewalla and Ubuntu server are hardwired, laptop and phone use wireless to get on the same network through my linksys MR8300 router (possibly through a switch). Xiaomi Mi9SE phone with the Wake On Lan app (also not really part of the concern, but used for testing WOL).
#Wakeonlan aquila windows 10#
Windows 10 laptop (not really part of the concern, but the machine I use to SSH to the others from). This is the device I want to be able to turn off and on. I would like to move the home automation to the Firewalla as it will use a lot less power and needs to always be on anyway (this is why the home automation was already delegated to docker, making it more like the to be situation). Currently always on and runs my home automation in NodeRED docker and a local NodeRED to allow me to use the execute node for certain functionalities (like the hibernate or suspend). Ubuntu 20.04.2 LTS fileserver (+ some other functionalities) on Asus f2a85-m motherboard and AMD A10-5700 CPU. I have loaded the latest NodeRED in docker on this device. Sure, devices (among others I expect would not expect to be relevant, think various IoT devices, printer, my HTPC, etc.):įirewalla Blue Plus: Linux based device, mostly acts as a firewall, but has the ability to add functionality through docker. as alternatives I could look into waking the machine on power and putting a NodeRED controlled power switch between it and its socket, or, because it's in a streacom case I could try to find a Flirc-SE and control it from my Logitech Harmony, either seems less ideal than just using WOL, though if I had a spare of either I might just set that up.
It consistently working from the phone app seems to suggest everything is ok on the server's side. I am not intimately familiar with Linux: I could not find an equivalent of the tool I used to confirm the packets were being received on my laptop.
#Wakeonlan aquila how to#
I'm running out of ideas on how to debug this. I tried UDP port 7, that worked once, no luck afterwards. Tried a phone app, which succeeded to wake my server each and every time. Tried a windows tool, Aquila's WakeOnLan, which confirmed that packets were coming in when I was trying to wake my (running) laptop from the wake on lan node. Double checked that the ethernet port was still in 'g' mode after a reboot, it was.
Could not consistently bring the server back up when I had hibernated or suspended it using NodeRED, nor when I manually do it directly on the server. Started on the shutdown (hibernate) part and got that working through the execute node from a NodeRED instance running on the server itself (using MQTT to talk between the 2 NodeRED instances). I turned it off from the command line in these scenarios.
#Wakeonlan aquila plus#
I have a Firewalla Blue Plus with NodeRED running in docker.Įverything looked good at first, couldn't bring it up from shutdown, but could bring it up from hibernate or suspend either would be fine for me. I've set up a fileserver at home and I don't usually need it running through the night so I figured I should be able to turn it on and off in an automation.
0 kommentar(er)
