Perfect, thanks. I’ll post back with my results.
[COLOR=#ff0000]EDIT: As this is a production installation and it’s needed over the next few days, I’ve scheduled the upgrade for Monday morning. If anyone else experiencing the same issue does the upgrade before and has success, feel free to post so others are aware (although judging by Tom’s posts it looks good!)[/COLOR]
Sounds promising! Is there any quick and easy way to check my current svn revision? Although I’m sure you’re correct that below 2403.
And follow this for upgrading? (I’m a first timer!): [url]http://www.fogproject.org/wiki/index.php/SVN[/url]
[quote=“Tom Elliott, post: 37895, member: 7271”]The idea of the “plugin” would be to create a management page for WOL that you simply specify the broadcast addresses you need.
If you guys want to try:
maybe edit the 255.255.255.255 part of the WakeOnLan .class.php file and put it to your broadcast as in the post above?
(10.155.255.255) and see if that works?[/quote]
We actually did try this last week and it did work with a single VLAN broadcast IP. We then attempted to add in all of our VLAN broadcast IPs directly (copying and pasting the if statement) but that didn’t work, unsurprisingly.
If, as you mentioned in your last post, there was a mechanism to loop through all broadcast IPs specified in a plugin that would be ideal.
[quote=“Fernando Gietz, post: 37878, member: 13”]We may match the IP address with the broadcast address of the subnet. We put this relationship into wakeOnLan function, isn’t the best solution, but works.[/quote]
Fernando - just wondering where you would get the IP address you’re referring to? Just given that computers can and do change subnets fairly often in our environment, so the last IP of the workstation isn’t necessarily correct.
Unfortunately no. The first one refers to UDP relay which is not an option on our particular router. And the second article is exactly how we have things set up, but no go. It appears that the router is discarding broadcasts to 255.255.255.255 whereas subnet-directed broadcasts are working properly.
Jacob
Hi Tom,
Unfortunately with Cisco ip forward-protocol is a global setting only, it’s not available at the VLAN level in order to configure the VLAN broadcast IP.
We have other systems within our organization that use subnet-directed WOL and they work fine with no config changes. One in particular I know uses dns lookups to determine the IP based on the hostname and sends to the VLAN broadcast IP based on that. And like I mentioned before when using wakeonlan with the -i switch and the VLAN broadcast IP from the FOG server it works as well.
Jacob
OK sure, that makes sense. It seems like that was what was done with the workaround mentioned in the wiki above, although it was very much a messy solution (going through each VLAN one by one and sending a WOL packet to each VLAN broadcast IP).
Just an update: capturing packets on the same VLAN as the FOG server revealed that it is indeed sending out WOL packets to the destination IP 255.255.255.255. They are not travelling any further than the router however, as we don’t see them on any other VLAN.
We dug into this article: [URL=‘http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipapp/configuration/12-4/iap-12-4-book/iap-bph.html’][FONT=Calibri]http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipapp/configuration/12-4/iap-12-4-book/iap-bph.html[/FONT][/URL], tried to set ip helper-addresses and the like but still nothing. We even attempted allowing UDP broadcast flooding and still a no go. Everything else pertaining to that document is enabled (access lists, forward UDP port 9 enabled, ip directed broadcast enabled on VLANs, helper-addresses as mentioned).
We’re really at a loss. Anything jump out at anybody? I realize this isn’t a FOG issue per se just looking for some friendly advice.
Thanks!
Thanks Tom! I’ll check on our switch configs and post back.
Me again!
After attempting a number of things in house we are no closer to an answer. I just wanted to add some context.
Currently our routers allow our main FOG server to send directed broadcasts to all of our workstation VLAN broadcast IPs (X.X.X.255).
In version 0.32 we followed this wiki in order to forward WOL packets to the seperate VLAN broadcast IPs: [url]http://www.fogproject.org/wiki/index.php/WOL_Forwarding[/url]. It seems that this was a home-built solution and that editing the wol.php file is a thing of the past (or at least it isn’t possible to do it the same way).
Which brings me to the WakeOnLan.class.php file. I have extremely limited php knowledge so I’m not sure how this file works, but I can read comments as well as anyone and it clearly states that this is the file that builds the magic packet. Can anyone give me a brief breakdown on how it works and if editing is necessary to broadcast to VLAN broadcast IPs rather that 255.255.255.255?
[PHP]<?php
/** \class WakeOnLan
Builds the magic packet needed for waking systems from LAN.
*/
class WakeOnLan
{
private $strMac;
/** __construct($mac)
Stores the MAC of which to system to wake.
*/
public function __construct( $mac )
{
$this->strMac = $mac;
}
/** send()
Creates the packet and sends it to wake up the machine.
*/
public function send()
{
if ( $this->strMac != null )
{
$arByte = explode(':', $this->strMac);
$strAddr = null;
for ($i=0; $i<count( $arByte); $i++)
$strAddr .= chr(hexdec($arByte[$i]));
$strRaw = null;
for ($i=0; $i<6; $i++)
$strRaw .= chr(255);
for ($i=0; $i<16; $i++)
$strRaw .= $strAddr;
$soc = socket_create(AF_INET, SOCK_DGRAM, SOL_UDP);
if ( $soc !== FALSE )
{
if(socket_set_option($soc, SOL_SOCKET, SO_BROADCAST, TRUE))
{
if( socket_sendto($soc, $strRaw, strlen($strRaw), 0, "255.255.255.255", 9) )
{
socket_close($soc);
return true;
}
else
return false;
}
else
new Exception( "Failed to set option!");
}
else
{
$errCd = socket_last_error();
$errMsg = socket_strerror($errCd);
throw new Exception( "Socket Error: $errCd :: $errMsg" );
}
}
return false;
}
}[/PHP]
We are currently between web developers here or I would ask him/her to give me a quick tutorial. Any help would be greatly appreciated!
Jacob
Hello all,
We recently upgraded from FOG 0.32 to 1.2.0.
Our organization spans multiple VLANs (~30) and since the upgrade wake-on-LAN is no longer working. We haven’t changed anything on the networking side and it worked in 0.32. In order to get it to work we edited the wol.php file to add all of the VLAN broadcast IPs (X.X.X.255) but in 1.2.0 I don’t believe that is an option anymore. Or maybe it is and I’m just not seeing where.
We have one main FOG server that sends out the magic packets and it is allowed to send these broadcasts on our router (as I said, it worked fine in 0.32 and nothing has changed on the network side). If I send a WOL packet using the wakeonlan command it doesn’t work if I leave it default (sending to 255.255.255.255) but if I change the IP to the broadcast IP of the VLAN it does work.
Main FOG server info:
Linux Mint 13 (64-bit)
VMWare ESXi 5.1
FOG 1.2.0