Does the Locations plugin also handle Wake-On-LAN?

[george1421]

Just to add a bit more information, the WOL messages sent to other broadcast domains are sent as a unicast message and then converted into a subnet broadcast message. The router that isolates the subnets must allow directed broadcast messages. If you have a cisco router you will have to enable directed broadcast messages with ip directed-broadcast. Settings on other devices will use device specific commands.

You also need to enable WOL on the target computers. I find that WOL works 50/50 in some networks.

[Tom Elliott]

Even Further FUrther information.

FOGScheduler service, which is installed on All nodes, will also run the tasks WOL stuff on ALL nodes FOG is installed on (whether it be master or not.)

FOGScheduler is the ONLY service who does not care about node status. Paired with the WOL Broadcast plugin, should give you the most Dynamic WOL experience.

[moses]

I’m sorry I’m not really much of a networking expert.

Basically I’ve got three subnets: 192.168.1.0, 192.168.2.0 and 192.168.4.0

How would I go about configuring the WOL plugin so I can broadcast on those subnets?

[george1421]

@moses The first thing I would do is confirm that directed broadcasts work on your network.

Assuming your fog server is on 192.168.1.0 subnet and your clients are on 192.168.2.0, on the fog server console key in the following ping -b 192.168.2.255 This will send a directed broadcast ping to all devices on 192.168.2.0 subnet. If this works then you have a better chance for wol working.

If your target computers are on the same subnet as your fog server then you can focus on the wol part and ignore any directed broadcast bits.

[moses]

@george1421 Okay, from my master fog server, I can ping 192.168.X.255 on all the subnets in question.

[george1421]

@moses Just for clarity, you get a response(s) too?

Forgive me if I guess this part. I don’t personally use WOL in my environment.

Oops, forgot to ask are you trying to wake up a bunch of computers or only a single one? If it is a single one, then find the computer in your host list. Out of the host menu select basic tasks, then in the advanced menu select Advanced. Scroll down the list and choose wake-up and schedule an instant deployment.

[Sebastian Roth]

@moses Did you get this to work for you?

[moses]

@george1421 Unfortunately, when attempting to do that, the host doesn’t boot. It’s in the same subnet as the master FOG installation. This particular host I know already has WOL enabled, as I was testing it with another imaging solution before I started using FOG.

[Sebastian Roth]

@moses Tom said:

FOGScheduler service, which is installed on All nodes, will also run the tasks WOL stuff on ALL nodes FOG is installed on (whether it be master or not.)

FOGScheduler is the ONLY service who does not care about node status. Paired with the WOL Broadcast plugin, should give you the most Dynamic WOL experience.

[Sebastian Roth]

@moses Please check the Scheduler log to see if the client is being WOLed… (FOG Configuration -> FOG Log Viewer -> File: Scheduler)

[Sebastian Roth]

@moses Can we mark this solved or do you still struggle to wake all your clients?

[moses]

@Sebastian-Roth Go ahead and mark it solved, I haven’t had time to test and probably won’t anytime soon. It’s that busy time of the year