Wake on lan WOL (Windows only)

[6theo4]

maybe with:
> route ADD 255.255.255.255 MASK 255.255.255.255 192.168.1.2
destination^ ^mask ^gateway(use interface ip)

[Michael Vogel]

Thanks, but this can't be done because of missing admin rights on the specific PC in daily life. Anyhow this route is also seen by default for all interfaces (including the loopback) but the broadcast is created only for one interface (Interface 0).

While playing around I also found out, that the internal numbering scheme for interfaces may change (no idea if other paramters, like Hyper-V could influence the behaviour as well)
So the output channel for the broadcasts is more unpredictable as expected.

I am trying to bind the socket to a specific interface now, if this works, it would be still necessary to enumerate all interfaces to find the right one...