06-27-2002 02:12 PM - edited 03-01-2019 11:04 PM
We are using WOL successfully on individual segments of our network but cannot wake a PC if it is on a segment other than the management PC.
Our network consists of 2 - 6509's at the core and 40 fiber connected locations running 3500 gear. Each location is run as a VLAN and all routing is handled by the MSM's in the 6509's.
How do the MSM's need to be configured to pass the WOL requests?
06-27-2002 02:12 PM
WoL is a UDP packet dest. port 9. So try configuring 'ip forward-protocol udp 9' at the global config and 'ip helper-address [WoL server's ip]' on the interfaces clients are connected on your 6509s
04-25-2003 05:13 AM
enabling directed broadcasts you enable your network to the smurf attack!
There is an other trick:
add a static arp with a defined ip for each interface, pointing to the mac ffff.ffff.ffff
eg.
arp 172.16.10.254 ffff.ffff.ffff ARPA
arp 172.16.11.254 ffff.ffff.ffff ARPA
arp 172.16.12.254 ffff.ffff.ffff ARPA
Then you generate the magic packet with a destination 172.16.12.254 and subnet 255.255.255.255
The packet will be delivered to all hosts on the subnet 172.16.12.0/24 and will wake up the PC with the MAC defined in the magic packet.
This solution is NOT subject on the smurf attack because nobody will have the "virtual" IP address and nobody will answer to them!
11-08-2002 11:55 AM
It has been a long while since your post... Have you gotten this to work.
I believe WOL requires directed broadcasts enabled on router interfaces which probably isn't a good thing.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide