WOL Not working FOG .32
-
Did you look in ‘FOG Settings’ like i asked?
-
Yes, sorry I forgot to mention that.
I went to the UI, other information > fog settings:
FOG_WOL_HOST server_ip
FOG_WOL_PATH /fog/wol/wol.php
FOG_WOL_INTERFACE eth0 -
‘server_ip’ was 172.17.14.206, right?
-
Ha!
I changed FOG_WOL_HOST server_ip
To FOG_WOL_HOST localhost
and now it works! -
Next i would test that the WOL script is being called correctly.
On the FOG server 172.17.14.206, run:
[code]tail -f /var/log/apache2/access.log[/code]
Now execute a WOL, you should see the WOL call in this access log. If you dont, then the call is never getting to Apache.[I]NOTE: You will see other URL calls here from FOG / FOG Clients… make sure you are looking at the right IP[/I]
-
I see this when executing a WOL from advanced task menu
[CODE]::1 - - [18/Dec/2011:20:23:37 -0500] “GET /fog/wol/wol.php?wakeonlan=f0
f1:9e:d9:10 HTTP/1.1” 200 192 “-” “-”
[/CODE] -
[quote=“Blackout, post: 120, member: 1”]‘server_ip’ was 172.17.14.206, right?[/quote]
That is correct. -
The log reports HTTP 200, so the page GET was successful and the PHP page was processed. Did the WOL event work?
If not, what happens if you manually go to below, does it work?
[url]http://172.17.14.206/fog/wol/wol.php?wakeonlan=f0f1:9e:d9:10[/url]It looks like its working as intended. There should be zero difference between you manually requesting that page and FOG requesting (its basically the same thing)
This sounds like some sort of configuration issue.
The next step would to tcpdump and see what the traffic is doing.
You will need to dump from your server and from your client to get a full picture of what is going on.
You want to check if the client is receiving the WOL Magic packet or not.
It should be a broadcast UDP packet to port 7 or 9 with a total of 102 bytes. 6 bytes of nulls, followed by the clients MAC address 16 times. -
Here is the wireshark wiki page on WOL.
[url]http://wiki.wireshark.org/WakeOnLAN[/url]
That is what you are looking for. You want to verify the WOL packet is getting to your client.
-
I have too, if I test whit the command [I]wakeonlan [mac][/I] it works fine.
But if i test it whit [url]http://10.0.0.1/fog/wol/wol.php?wakeonlan=40:61:86:01:72:43[/url] it[COLOR=#000000] send [/COLOR][COLOR=navy][COLOR=#000000] nothing.[/COLOR][/COLOR] -
I have the Same issue manualy wol is working ok
I use the menu option in FOG (.32) nothing is happening!192.168.48.150 - - [15/Jun/2012:14:51:17 +0200] “GET /fog/management/index.php?node=tasks&confirm=406&type=host&direction=wol&singlescheddate=&cronMin=min&cronHour=hour&cronDOM=dom&cronMonth=month&cronDOW=dow HTTP/1.1” 200 1606 “[url]http://fog/fog/management/index.php?node=tasks&type=host&direction=wol&noconfirm=406[/url]” “Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5”
192.168.48.150 - - [15/Jun/2012:14:51:17 +0200] “GET /favicon.ico HTTP/1.1” 404 496 “-” “Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.56 Safari/536.5” -
I am having the same problem, I am running the FOG server under Hyper-V on Windows 2008R2 datacenter. Could the virtualized network adapter (legacy network) on Hyper-V cause this?
It does not work either manually or thru the menu. I have used a WOL utility from the same subnet and it works. FOG does not seem to be sending any WOL packet.