WOL

Wayne Workman

This URL is how you would test FOG’s WOL abilities directly.

http://x.x.x.x/fog/management/index.php?sub=wakeEmUp&mac=aa:bb:cc:dd:ee:ff

Replace the Xs with the main fog server’s IP, and replace the MAC. When you call that URL with a browser, FOG will send a WOL out from every server to the MAC you put in.

adukes40

@Wayne-Workman When I type that in, nothing happens.

http://10.103.72.49/fog/management/index.php?sub=wakeEmUp&mac=b8:ac:6f:3d:6e:a4 = nothing

SSH into 72.49, run WOL to the remote host = nothing

SSH into the remote node, run WOL = turns on.

Tom Elliott

@adukes40 What ports are you blocking for UDP?

WOL is a broadcast layer item meaning it works from Layer 2. However, it’s also based on UDP and in particular FOG uses port number 9.

adukes40

@Tom-Elliott far as I know, it shouldn’t be blocked. Is there a way I can tell on the Linux box?

Tom Elliott

@adukes40 does the wol request work if you replace the ip with the ip of your remote node?

adukes40

@Tom-Elliott i tried that earlier, only way it works is off run wakeonlan (mac) from the terminal

Wayne Workman

@Tom-Elliott According to the MAN page for wakeonlan it uses a default UDP port of 9.
http://www.linuxcertif.com/man/1/wakeonlan/

Sebastian Roth

@adukes40 I am not exactly sure if I get this right. So I hope you don’t mind if I am telling you things you already knew. As Tom already said WOL is something that only works within a subnet (broadcast domain). If you want to wake up PCs from a different subnet you need to forward the packets. The DD-WRT site describes it nicely: http://www.dd-wrt.com/wiki/index.php/WOL#Remote_Wake_On_LAN_via_Port_Forwarding

Writing your own firewall rules using iptables it would be something like:

iptables -t nat -A PREROUTING -i eth0 -p udp -d 192.168.0.1 --dport 9 -j DNAT --to 192.168.1.254:9

Wayne Workman

@Sebastian-Roth Tom says that when a host is WOL’d, every storage node under the command of the main fog server is told to WOL that host’s MAC address all at once. And the OP has nodes at every site connected to his main fog server.

In summary - the Linux utility wakeonlan does wake up hosts. This utility uses UDP port 9 just as FOG does.

Fog’s WOL isn’t working for him, even after trying manual calls from the main and to remote nodes where the hosts are.

@adukes40 can you confirm those things?

Sebastian Roth

@Wayne-Workman Ok, then totally screw what I said!!! I didn’t know that FOG is that intelligent as I haven’t used it in big environments yet. My fault!

adukes40

@Wayne-Workman Correct, I am using location plugin, 1 master, 6 nodes. WOL only works if I use the wakeonlan utility. Running WOL, or deploying a task, does not WOL even at the master site. Also will not wake up when doing http://10.103.72.49/fog/management/index.php?sub=wakeEmUp&mac=b8:ac:6f:3d:6e:a4 but using the utility, typing wakeonlan b8:ac:6f:3d:6e:a4, turns on instantly

Sebastian Roth

@adukes40 Do you see any messages in the apache error log when accessing the mentioned URL to wake up clients?? See my signature on where to find the log.

Tom Elliott

I’m trying to understand how the magic packets are setup. See things seem to work fine, then I’m told they don’t and it varies from person to person, network to network, system to system.

I’ve even seen people say it works from this one system, but not that one system. (From or To can be used interchangeably here please).

mp12

@Sebastian-Roth

Server

FOG Version: RC-12 (42)
OS: Ubuntu 14.04

Client

Service Version: 0.11.5
OS: Win 7

I am having the same problem. Can wake-up the clients in the console using wakeonlan *MAC*. When trying to wake-up a client or group in FOG GUI it creates the following error in the apache error.log

[Tue Oct 04 10:08:18.989990 2016] [:error] [pid 9838] [client x.x.x.x:35286] PHP Fatal error:  Uncaught Error: Access to undeclared static property: WakeOnLan::$_port in /var/www/fog/lib/fog/wakeonlan.class.php:70\nStack trace:\n#0 /var/www/fog/lib/fog/fogpage.class.php(1316): WakeOnLan->send()\n#1 /var/www/fog/lib/fog/fogpagemanager.class.php(230): FOGPage->wakeEmUp()\n#2 /var/www/fog/management/index.php(25): FOGPageManager->render()\n#3 {main}\n  thrown in /var/www/fog/lib/fog/wakeonlan.class.php on line 70

Tom Elliott

@mp12 You’re running on working-RC-12 right now. While that issue shouldn’t be present, it isn’t the same as what @adukes40 is seeing either. I can fix the static property issue relatively easily.

Tom Elliott

@mp12 https://github.com/FOGProject/fogproject/commit/6f90796d3c13c5db23390b47884e0660a04393b9

That should fix the static variable issue for you too if you want to update again.

mp12

@Tom-Elliott

A single host wake-up in FOG GUI works fine.
WOL via URL http://x.x.x.x/fog/management/index.php?sub=wakeEmUp&mac=aa:bb:cc:dd:ee:ff works.
A Group wake-up via FOG GUI won’t work. I don’t get any error in the /var/log/apache/error.log.

mp12

bump.

Still having the problem when trying to wake-up a group of clients. They won’t wake up.
Wake-up of a single client works.

Wayne Workman

@mp12 how many are in the group? Please try a group of two. If either of them wake up, let us know and we will have more tests for you.

Tom Elliott

@mp12 said in WOL:

@Tom-Elliott

A single host wake-up in FOG GUI works fine.

WOL via URL
http://x.x.x.x/fog/management/index.php?sub=wakeEmUp&mac=aa:bb:cc:dd:ee:ff
works.

A Group wake-up via FOG GUI won’t work. I don’t get any error in the /var/log/apache/error.log.

If you try the URL as:

http://x.x.x.x/fog/management/index.php?sub=wakeEmUp&mac=aa:bb:cc:dd:ee:ff|ab:bc:cd:de:ef
Does it give the same issue? NOTE: The | and immediate following MAC Address. The second, third, or xth number of MAC’s don’t necessarily have to be “real” macs.

If that works, try replacing the “order” of the macs. So if aa:bb:cc:dd:ee:ff is your “valid” mac address, and you put it at the end of the “string” does it work? This will help me try to figure out what’s needed to happen.

@mp12, if I recall you’re running the “working-RC-12” branch right?

WOL

149

12.1k

17.3k

155.3k