REMOTE WAKE UP ON VLANS MAC

REMOTE WAKE UP ON VLANS MAC

Since the magic packet is a broadcast frame, it does NOT contain the MAC address of your NIC, which means your NIC has to watch for packets that contain it's IP address. WOL gets initialized by the OS when the Os tells your NIC which IP to look for. The magic packet is a broadcast frame.ĭon't forget, if you ever have a power-outage or un-plug your computer for any reason, you will more than likely have to boot to the OS and shutdown again before WOL will work. This one computer HAD to be on all vLANs because the packet is non-routable, so it had to originate on the local vLAN.ĩ9% of the reason for routers is to break up broadcast domains. Then 'telnet 12345 ' from another computer and the TCP request to open that port will wake your computer up.Īgain, your NIC has to support this and not just the 'Magic Packet'.Īnother thing is you would have a dedicated computer inside your network that you can remote onto and you can make that computer send off a 'Magic' packet to your computer to wake it up.Īt my last job, we had a central computer that did our WOL and we could send out magic packets to computers by name. Setup port forwarding on port 12345 to your computer. If your NIC supports it, you can set it up to wake up from ANY packets directed to it.Įg. Using a Netgear WNDR 3700 router and Netgear DS104 hub. Yeah, its a 2-year-old thread but I too found it through 'WOL over WAN' research and so will others looking for answers. According to the router, the target device for the magic packet is the printer, but the hub inside the LAN will also broadcast it to all devices, one being the hub-connected computer even though its not in the router's dynamic arp list.Īlways a good idea to reserve the IP addresses for the constant on device and the computer to be woken up, if your router supports it. When you send a magic packet to the router's IP address, it will forward it through the hub to the printer, however the magic packet contains the MAC address of the computer I want woken up. Therefore the packet will not get dumped since it has someplace to go. Set your router to port forward (Use port 9) to go to the constant active device (I have a cheap HP Combo Printer/Fax that is always on) and thus will always show up in the dynamic arp cache. A hub broadcasts to all devices connected to it, a switch will only send packets to the specific device its intended for and not the other connected devices. The caveat is you must have a printer, voip or any device with an IP/MAC address that is constantly on, then a simple inexpensive $15 hub after the router will work.

No telnet, no hacking static entry in DHCP that will eventually lockup your router, no suspect firmware, no VPN, no dedicated computer required.Īlthough similar, this is not VPN. However, there is a KISS way to bypass that pesky cleared arp list that obviously doesn't contain your shut-down computer. THis is also our MDT/ WDS server.Assuming you've already setup WOL correctly on NIC, bios, router, given a static ip to the computer, tested it out and were initially successful doing WOL over WAN, but failed after a period of shut-down time, is because your router clears its arp table as stated above. WOL is on the server IP address 172.20.10.14.I've also tried putting ip forward-protocol in VLAN 10 to forward the WOL packets to VLAN 20 where my workstations sit, but to no avail. As you can see I have enabled the relevant bits such as ip directed-broadcast and ip udp-bcast-forward at the root. How do I get WOL working across other VLANs?īelow is a snippet of the config file from my core switch.

Remote wake up on vlans