Differences between version 4 and predecessor to the previous major change of WakeOnLanNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Thursday, April 14, 2005 8:36:45 pm | by DanielLawson | Revert |
| Older page: | version 3 | Last edited on Thursday, April 14, 2005 7:23:06 pm | by AristotlePagaltzis | Revert |
@@ -47,5 +47,13 @@
</verbatim>
Note that you'll need to change the setting anew on every boot, so stick the command in <tt>rc.local</tt> or whichever boot script is applicable.
--- Which open ports do you need to open for ether-wake. Could anyone explain
? -- thx
+----
+
+!
Which open ports do you need to open for ether-wake?
+
+First of all, you normally use ether
-wake to trigger a wake
-on-lan event on a powered off computer. It is unlikely to have a firewall running at this point!.
+
+ether-wake works by sending a special ethernet frame. Read the notes at MagicPacket for more information about this. Because this is an ethernet frame, and not actually an IP packet, it is not routable. The answer to the above question is "You can't".
+
+There are other types of wake-on-lan triggers however, and I believe the only requirement is that it follows the format specified in the MagicPacket notes. these may or may not IP packets, and whether you need to open firewalls up to them or not will depend entirely on the local configuration.
