Timeline for Wake on LAN across VLANs in IPv6 network
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 2, 2015 at 2:24 | comment | added | Lee Ballard | Not sure you need to worry too much about the switch remembering the port. Default behavior for most switches is to flood all ports if a MAC is not known. If you reboot a switch you'll get connectivity back before ARP caches timeout. Packets will flood until the target responds and the switch re-learns which port the MAC is on. Sending to the unicast IPv6 address should work. | |
| Apr 19, 2014 at 17:08 | comment | added | Michael Hampton | Exactly. There are no good options that I have ever heard of. Let's also remember that WoL was designed for single LANs (hence the name); it was never really intended to cross subnets though people did figure out ways to do that anyway. | |
| Apr 19, 2014 at 17:07 | comment | added | Avery Abbott | Default timers for ARP cache timeout and MAC address table timeout are both 5 minutes; this won't help for a 3AM wake-up call and I'm not going to try to set them for several days long. In a network with ~1300 workstations spread over a MAN, configuring BIOS-level wake-up events is not a legitimate option, and with a "green" employer, neither is not sleeping. I know there are no IPv6 broadcasts, but there are "All Nodes" multicast messages (address ff02::1) and there are still ethernet broadcast frames (ffff.ffff.ffff). | |
| Apr 19, 2014 at 16:18 | review | First posts | |||
| Apr 20, 2014 at 11:06 | |||||
| Apr 19, 2014 at 16:00 | history | answered | Michael Hampton | CC BY-SA 3.0 |