WOL packets across subnets?
-
WOL does not work over subnet... Do you understand how WOL works? You send specific packet to the mac address (layer 2).. If you want to wake up something on another layer 2 network, then you need something on that other layer 2 to send the packet.
Now it is possible - but you need something that has access to both the sender and the receiver. And you have to tell the guy between (router) to wake up dest device. This router needs to know the mac address of this dest device.. static arp entry can help with that, etc.
Going to say this again - its not worth the hassle.. But sure go ahead and help them ;) You can always log into the pfsense web gui and if you have setup static arp, dhcp reservation for this device as example you can send the wol packet from there.. So sure there are work arounds - awaiting your code changes to pfsense to allow for such a thing...
Get with your homebridge forum on how to have it send wol to different devices on different subnets.. Is that not a standard feature where you can say Wake Up X? Sure alexa and stuff can send the wol messages to device - but they have to be in the same layer 2 network!!
-
@johnpoz said in WOL packets across subnets?:
WOL does not work over subnet... Do you understand how WOL works? You send specific packet to the mac address (layer 2).. If you want to wake up something on another layer 2 network, then you need something on that other layer 2 to send the packet.
Now it is possible - but you need something that has access to both the sender and the receiver. And you have to tell the guy between (router) to wake up dest device. This router needs to know the mac address of this dest device.. static arp entry can help with that, etc.
Going to say this again - its not worth the hassle.. But sure go ahead and help them ;) You can always log into the pfsense web gui and if you have setup static arp, dhcp reservation for this device as example you can send the wol packet from there.. So sure there are work arounds - awaiting your code changes to pfsense to allow for such a thing...
Get with your homebridge forum on how to have it send wol to different devices on different subnets.. Is that not a standard feature where you can say Wake Up X?
I guess you are too focused on being negative and not on what people are wanting to do. How you are a global moderator with that attitude I have no idea.
Either way how is homebridge going to fix this? Homebridge is simply a hub for IoT devices sitting on the subnet. It can't route packets as it can only send them out on the broadcast address of the subnet its on. This would need to be done at the router level, which in this case, is my pfsense gateway. As for code changes..if theres work arounds then that is fine. How about just supplying people the workarounds instead of trying to argue?
Here seems to be a workaround I am going to give this a try. This isnt an impossible task unless the BSD kernel blocks it from happening specifically which could be an answer you could supply. : https://forum.netgate.com/topic/30355/wake-on-wan/3
-
@jeremym said in WOL packets across subnets?:
I'd personally like to find some kind of work around. I dont live in a mansion or anything either but id like to just say "Hey Siri, Goodnight" and my tv shuts off with everything else homekit shuts down. Maybe thats what he wants too? Simple automated convenance.
That's not the sort of thing WoL does. WoL stands for Wake on LAN, which is a method to turn a device on. There is no corresponding function to turn it off.
-
@JKnott said in WOL packets across subnets?:
@jeremym said in WOL packets across subnets?:
I'd personally like to find some kind of work around. I dont live in a mansion or anything either but id like to just say "Hey Siri, Goodnight" and my tv shuts off with everything else homekit shuts down. Maybe thats what he wants too? Simple automated convenance.
That's not the sort of thing WoL does. WoL stands for Wake on LAN, which is a method to turn a device on. There is no corresponding function to turn it off.
Correct. What I am wanting to do is have the WoL packet sent to my TV to wake it up. According to the dev, the plugin then uses the Samsung API to manage commands after that such as power off. I didnt go into detail of how the exact plugin works because honestly I do not know other than the high level aspect I just typed here because its found on the wiki of the plugin.
So if I can get the WoL packet to reach the TV then the plugin will utilize the Samsung API to do the rest. Just need to wake it up.
However I do recall more detail I read a few months ago about how this plugin worked. It might have been in a GitHub bug someone opened and it was a reply from the dev. I think theres more "voodoo" to shutting it off than what I said above because honestly it should shut off after I manually power it on the way I have things configured now but it doesnt.
The quick backstory of my little project is this..I had everything on the same lan working great. I decided to make things a bit more secure and created a separate vlan for my IoT devices. I wanted to leave my Apple devices and my Samsung TV on my regular lan. So I created an alias for my homekit hub devices (Apple TVs and HomePods), installed Avahi for mdns retransmissions across subnets, gave my hubs static IPs based upon their Mac in my DHCP server on the gateway, and opened up firewall rules so the devices on the IoT vlan could communicate with only the homekit hub devices on my lan. They cannot reach anything else on my lan. I created rules in reverse as well so I had no restrictions depending on what device initiated the connection request. For the wifi devices I got a cheap Linksys wireless router and put dd-wrt on it so it was as secure as I could get it "Linksys firmware is really out of date for this old thing so decided dd-wrt release from dec of 2019 is best I can do".
All is working great except for this plugin. Which is what lead me here because I know what WoL is and I was hoping someone had a solution to get the packet to relay to the right subnet when homebridge sent it out.
Here is a link to the plugin so you can take a look if you are interested in it. Works great when on the same subnet :)
https://github.com/tavicu/homebridge-samsung-tizen/wiki -
This post is deleted! -
@jeremym said in WOL packets across subnets?:
What I am wanting to do is have the WoL packet sent to my TV to wake it up.
Does your TV even support WoL?
-
If it's just one device then you should be able to add a static ARP entry for it and the appropriate port forward for whatever your application uses.
When I looked into this before I could see no way to allow forwarding directed broadcasts.Steve
-
Setup an internal proxy maybe? Such as: https://help.green-it-software.com/pdf/Raspberry%20Pi%20as%20WolProxy%201.0.3.pdf
Steve
-
It's certainly possible to set up a WoL relay agent.
-
Just because you have something that will relay or forward (that device that has access to both L2s) doesn't mean its going to work with alexa or google home or homekit, etc. etc.
Not without some major background work and setup most likely, and understanding the details of how your device you want to say wakeup X actually does that..
My Alexa can turn on my TV, and off.. but I have my harmony remote in the same vlan as alexa, while my tv is in its own vlan. Both of these vlans are different than my other vlans. It would prob work without even... Since the harmony remote isn't in standby and the alexa should be able to talk to it over L3.
But trying to find ways to move L2 data into another L2 is not the right approach.. Correct design of your L2s is better option from a security standpoint.. You need X to talk to Y via layer 2 - then put them in the same layer 2, its really that simple!!! Isolate that network from your other stuff..
Do you trust alexa... do you trust your tv, do you trust your iot - well no that is why we isolate them.. But if X needs to talk to Y via layer 2 stuff.. The simple solution is just put them in the same L2 ;)
