Wake on LAN accross multiple routers
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-07-2014 10:06 PM
Create Date: Dec 5 2013 3:45PM
I have a server that needs to wake devices. I saw the "ipforwarding broadcast" command, but the VLANs the target devices are in are spread across an enterprise network and do not exist on the same router.
I need more of a "ipforwarding broadcast " type of command to send the WOL packet to remote buildings across many routed networks.
(from Mightyotis)
I have a server that needs to wake devices. I saw the "ipforwarding broadcast
I need more of a "ipforwarding broadcast " type of command to send the WOL packet to remote buildings across many routed networks.
(from Mightyotis)
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-13-2014 07:06 PM
I'm facing a similar situation, and this has pointed my in the right direction - thank you! Is there a way to enable the subnet broadcast from only one IP address? For instance, if in the above example, the server is at 10.0.0.10, can we set up L3-Gateway-3 to only accept/forward the WOL magic packets from 10.0.0.10?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-07-2014 10:06 PM
Create Date: Dec 6 2013 9:30PM
Hello Mightyotis
Here's the answer to your question. Let me know if there is anything else.
If the server and the Wake On LAN(WOL) clients are located in the same broadcast domain then we didnt need to configure anything even though the clients and server were deployed across several buildings.
If the server and Wake On LAN(WOL) clients are located in different subnets, then we need to enable "enable ipforwarding broadcast" only on the gateway of those networks.
For example
server---------------- |L3 Gateway-1|---------------------|L3 Gateway-2|-----------------------|L3 Gateway-3|
| | |
10.0.0.0/24 10.0.1.0/24 10.0.2.0/24
In the above topology when the server has WOL clients located on 10.0.2.0/24 subnet, then we need to enable "enable ipf forwarding broadcast" only on L3-Gateway-3.
Thanks
(from Paul_Russo)
Hello Mightyotis
Here's the answer to your question. Let me know if there is anything else.
If the server and the Wake On LAN(WOL) clients are located in the same broadcast domain then we didnt need to configure anything even though the clients and server were deployed across several buildings.
If the server and Wake On LAN(WOL) clients are located in different subnets, then we need to enable "enable ipforwarding broadcast
For example
server---------------- |L3 Gateway-1|---------------------|L3 Gateway-2|-----------------------|L3 Gateway-3|
| | |
10.0.0.0/24 10.0.1.0/24 10.0.2.0/24
In the above topology when the server has WOL clients located on 10.0.2.0/24 subnet, then we need to enable "enable ipf forwarding broadcast
Thanks
(from Paul_Russo)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-07-2014 10:06 PM
Create Date: Dec 5 2013 5:36PM
I might not have stated the problem correctly.
I have a single WOL device needs to wake up sleeping VDI terminals where there are multiple terminals on multiple VLANs spread across multiple routers (so the "vlan" part becomes a challenge in the "ipforwarding broadcast" command.
If I configure the WOL device to send UDP packets using port 67 and then set my bootprelay address to 192.168.1.255 (on the 192.168.1.0/24 network)would this then broadcast the WOL packet on the target VLAN????
(from Mightyotis)
I might not have stated the problem correctly.
I have a single WOL device needs to wake up sleeping VDI terminals where there are multiple terminals on multiple VLANs spread across multiple routers (so the "vlan" part becomes a challenge in the "ipforwarding broadcast
If I configure the WOL device to send UDP packets using port 67 and then set my bootprelay address to 192.168.1.255 (on the 192.168.1.0/24 network)would this then broadcast the WOL packet on the target VLAN????
(from Mightyotis)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-07-2014 10:06 PM
Create Date: Dec 5 2013 4:55PM
Hey Mightyotis
There are really two ways to get this to work. The first way is to use UDP forwarding where you have the switch grab the UDP broadcast packet and then forward it on to the server. This can be a little complex to setup.
The second way was done at another customer where they just had the WOL server respond to port 67 and added the server to their bootp server list. The switch sees it and sends it to the WOL server. They mentioned that this works pretty well and was easy.
Hope this helps.
Thanks
P (from Paul_Russo)
Hey Mightyotis
There are really two ways to get this to work. The first way is to use UDP forwarding where you have the switch grab the UDP broadcast packet and then forward it on to the server. This can be a little complex to setup.
The second way was done at another customer where they just had the WOL server respond to port 67 and added the server to their bootp server list. The switch sees it and sends it to the WOL server. They mentioned that this works pretty well and was easy.
Hope this helps.
Thanks
P (from Paul_Russo)
