Difference between revisions of "Wake-On-Lan fail with VM"
From ESS-WIKI
(Created page with "== How Wake-On-Lan Work == * Cloud server will request "Agent1" to wake up another "Agent2" * Agent1 will send broadcast magic packet which payload is the MAC address of Agent...") |
|||
| Line 1: | Line 1: | ||
== How Wake-On-Lan Work == | == How Wake-On-Lan Work == | ||
| − | |||
| − | |||
| − | |||
| − | == Routing Table | + | *Cloud server will request "Agent1" to wake up another "Agent2" |
| + | *Agent1 will send broadcast magic packet which payload is the MAC address of Agent2. | ||
| + | *When Agent2 receive magic packet, it power on device. | ||
| + | |||
| + | [[File:Wol-route-2.png|RTENOTITLE]] | ||
| + | |||
| + | == Routing Table Problem with VM installed == | ||
| + | |||
| + | *There are two broadcast address. | ||
| + | **Global broadcast address: 255.255.255.255 | ||
| + | **Local broadcast address: ex: 172.22.15.255 | ||
| + | **[[File:Wol-route-3.png|RTENOTITLE]] | ||
| + | **PowerOnOff plugin send WOL packet to global broadcast address. | ||
| + | |||
| + | *We found VM network adapter will modify global broadcast route rule that may makes broadcast fail. | ||
| + | **[[File:Wol-route-1.png]] | ||
| + | |||
| + | *Routing priority of windows: | ||
| + | *#Small metric rule will pick up first. | ||
| + | *#Then it will pick up the first interface that avaliable. | ||
| + | *PowerOnOff plugin will choose "255.255.255.255 | 192.168.189.1" rule from routing table in this example. | ||
| + | |||
| + | == Possible Solution == | ||
| + | *Send WOL packet with local broadcast address to each interface in current agent. | ||
Latest revision as of 10:41, 31 May 2018
How Wake-On-Lan Work
- Cloud server will request "Agent1" to wake up another "Agent2"
- Agent1 will send broadcast magic packet which payload is the MAC address of Agent2.
- When Agent2 receive magic packet, it power on device.
Routing Table Problem with VM installed
- There are two broadcast address.
- Global broadcast address: 255.255.255.255
- Local broadcast address: ex: 172.22.15.255
- PowerOnOff plugin send WOL packet to global broadcast address.
- We found VM network adapter will modify global broadcast route rule that may makes broadcast fail.
- Routing priority of windows:
- Small metric rule will pick up first.
- Then it will pick up the first interface that avaliable.
- PowerOnOff plugin will choose "255.255.255.255 | 192.168.189.1" rule from routing table in this example.
Possible Solution
- Send WOL packet with local broadcast address to each interface in current agent.