WoL - Not working

Configuration
1

I currently have hassos setup in VMWare Fusion with a dedicated NIC (the primary machine uses another NIC for communications).

With that being said, I’m at my wits end trying to get WoL specifically to work with hassos. I have no issue calling the appropriate command from separate applications on multiple devices or respective terminal commands outside of hassos.

show_name: true
show_icon: false
type: button
tap_action:
  action: call-service
  service: wake_on_lan.send_magic_packet
  target: {}
  data:
    broadcast_port: 9
    mac: xx:xx:xx:xx:xx
name: PC
hold_action:
  action: none

Before it’s asked, yes, I’ve tried all combinations of quotations, dashes and colons possible. I’ve also tried from raw YAML, to the GUID, to Scripts. I simply can’t get hassos to send out a proper WoL command.

This applies to pretty much anything and everything I’ve used it against as well where as I have no issue outside of hassos. I have 2 current use cases, my PC and my lg tv – both I’ve verified work with every other tool.

I have no idea if there’s a weird NAT thing behind the VM or not causing this – but there really shouldn’t be ‽

2

Looks like you are trying to wake a PC. If it is a Windows PC, turn the firewall off and try it.

3

Did you enable WOL im config?

4

I assume you are refering to the firewall of VMWare? As there is no windows firewall when it is turned off, only BIOS (and WOL works when sent from another machine) :thinking:

5

No the firewall of the pc they are trying to turn on

6

https://answers.microsoft.com/en-us/windows/forum/all/wake-on-lan-not-working-anymore/1dbd1f7a-be46-4c36-9ae3-91bb601282d6

7

Tom, Francis… the WOL is working fine when send from any other machine…so there is nothing wrong with the target… he only cannot get it to work from HA :wink:

2 Likes
9

Please format your post correctly or it won’t help anyone. https://community.home-assistant.io/t/how-to-help-us-help-you-or-how-to-ask-a-good-question/114371#oneone-format-it-properly-16

10

The most likely errors are a missing configuration of the VMWare NIC to allow the magic packet to be routed (magic packets are normally not routed and hypervisors normally make their own internally LAN) or the broadcast_port, which needs to be correct for the magic packet to be send (if the HA installation only have one NIC, then leave it out).

1 Like
11

You might be the only one who potentially read through my full post here :sweat_smile:.

I believe this tracks with what I’m observing, although I have no resolution to the issue at hand (which is frustrating).

The VMWare Fusion Network Adapter is setup as such:

image
image1272×844 83 KB

And similarly the Ethernet bridge interface is set to essentially be a bridge:

image
image982×932 52.3 KB

The external Hassos address is a 192.168.7.255 subnet (being a separate virtual assigned Mac address over the host machine).

From here, I’m just a bit stuck.

Iteratively speaking, I’ve attempted using a broadcast address amongst other fields… maybe I should play with the host address?

1 Like
12

Unless you’re looking for log (there are no log emitting for wake_on_lan:) I’m unsure of what you’re asking for or looking for. . .

13

Bingo – you read my post!

14

Correct. The GUI would emit errors if I didn’t.

15

As noted in the original post:

I have no issue calling the appropriate command from separate applications on multiple devices or respective terminal commands outside of hassos.

I have 2 current use cases, my PC and my lg tv – both I’ve verified work with every other tool.

16

I’m unsure where to fix it but I’m nearly 100% sure Wally has it. If the WOL packet works somewhere else this is purely a sending issue. And as Wally said Hypervisor network stacks usually don’t pass that stuff.

17

Love the vote of confidence. It’s interesting because I’ve read through a ton of posts with WoL issues, no one seems to mention the virtualization portion. The only “solution” I’ve seen involves bridging host networks 100% within a Docker container which:

A.) Isn’t an option on macOS with Docker (or certain other OS’s)
B.) Is a crippling change if you want separate interfaces/traffic/NICs/etc
C.) Removes the benefits of running a dedicated hassos with powerful hardware
D.) Removes a loooot of benefits of using a dedicated VM over a striped down Docker instance.

Unsure of why this isn’t discussed more, maybe people just don’t dive in enough?

18

Because you’re trying to mix enterprise scale network controls with consumer grade gear. Sometimes it doesn’t translate.

19

It was a reply to a post that the author has since deleted.

20

Ah, I didn’t see that :sweat_smile:

21

That’s not true. I have host bridging on my macbook containers (for work) using named networks in my docker-compose stacks. Perhaps you are referring to Docker Desktop, which is limited in it’s execution (by design)?

Also not true as you can have multiple docker stacks that are bound to individual NICs and interfaces.

Also also not true. I have HA Core (docker) running on “powerful hardware” (Ryzen7 3700 with 64GB of RAM). The container takes as many resources as it needs. It runs in a separate stack connected to a central swarm across multiple hosts.

This one is partially true, but also not. Yes, you do lose some management benefits, but at the same time, there’s an ease of use factor going on as well. The only benefits that I know of that I lose are things like explicit CPU bindings and perhaps some over-simplicated things (like privileged mode execution for containers).

With all that said, it’s been a long time since I’ve used Fusion, but IIRC, you do need to bridge the hypervisor’s internal lan with the host LAN. Otherwise, VMF just swallows the outbound magic packet and it never gets broadcasted.

1 Like