I have an HAOS-VM running on a machine attached to my router via cable, and another (wifi attached) machine that I want to WoL from HA.

Apparently, my router does not forward WoL packets from wired ethernet to wifi, so I just plugged in a usb-wifi dongle and connected HAOS via the dongle - wifi works, no problem.

WoL in general also works, I can wake the machine up from my MacBook without a problem. I can also use the very same dongle on a Debian desktop to send WoL packets.

However, doing it from HA fails. My configuration.yaml looks like this:

wake_on_lan:
switch:
  - platform: wake_on_lan
    name: wake_<machine>
    mac: <mac>

I tried deactivating the KVM brigde, so that the VM really only connects via wifi, but no changes here either.

There are no errors in any logs, so it doesn’t look like it’s failing per se.

To me it looks almost like the packet is send to nirvana, but there’s no way to configure the network interface in the WoL platform either.

Update

I kind of got everything to work, albeit in a rather weird way.

There already is a built-in WoL Service, accessible via the GUI, however, I have to use the Advanced Mode to access it, otherwise it simply doesn’t show up. Using that service and the proper broadcast address, I’m now able to wake the target machine via a button. What’s a bit concerning to me is that the “advanced mode” toggle seems to be lost after a reboot. I get a warning, that the WoL service couldn’t be found, that only resolves after setting the advanced mode off and on again - that’s rather stupid.

  • AggressivelyPassive@feddit.deOPEnglish
    1·
    9 months ago

    It’s USB pass through, so there shouldn’t be any filtering.

    Wireshark could be an idea, I’ll check that tomorrow.

    • SwingingTheLamp@midwest.socialEnglish
      2·
      9 months ago

      I realize that I forgot to answer the question! The wake_on_lan integration has a broadcast_address parameter. It doesn’t explicitly let you pick a network interface, but it might be worth trying to set it to the broadcast address of the Wi-Fi subnet. Then the routing table would ensure that the packet goes out on the correct interface.

      • AggressivelyPassive@feddit.deOPEnglish
        1·
        9 months ago

        I just tried to capture the wifi traffic, but couldn’t find anything from HA.

        My networking skills are a bit rusty, but using wireshark I could filter a bunch of UDP/DISCARD packets sent by my MacBook when issuing the wol-command. But HA doesn’t emit anything when clicking the wol button.

        I also tried to set the broadcast explicitly (255.255.255.255 and the local broadcast advertised by DHCP).

        Just to be sure, I checked “ip link” and there is no wired ethernet, just lo, docker, a bunch of virtual devices (e.g. vethb1ac13f@if11), but these should be for virtualization.

    • CondorWonder@lemmy.caEnglish
      2·
      9 months ago

      I second the packet capture idea. Did you remove the virtual nic in the vm or just disconnect it? I’d you just disconnected it the packets were likely still directed to it as it’s the first network device.

      I suspect you’re going to need to use a command line service to do a wol command as the integration doesn’t work let you pick a nic.

      • AggressivelyPassive@feddit.deOPEnglish
        1·
        9 months ago

        See my comment above, I tried wireshark without success.

        I removed the <interface> part from the Qemu-config, which I think should remove the device completely.

        Command line would be fine, but the buildroot image doesn’t seem to ship with anything WoL-y, at least nothing that I could find.