I am able to wake up a particular machine with the Wake On LAN tool on my LAN, so I know I have the BIOS and Windows 10 settings enabling WOL. Now I am trying to wake up the machine via the internet. Aparently my firewall does not allow port forwarding to a broadcast address, so I set up a rule to forward to the specific NAT address of the machine I want to wake up. When the machine is awake, and I have the "Listener" window open, when I send the WOL pakect over the internet it is displayed in the Listener window. Everything is correct: the NAT address, the port and MAC. However, when the machine is sleeping and I send the WOL packet over the internet, the machine does not wake up.
So my question is, is it typical that a sleeping NIC only listens to broadcast magic packets??? Any other idea why the internet wake up call gets displayed in the Listener when awake, but does not wake up the machine when sleeping?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I am not sure if I can reply to this as I don't even have a source forge account anymore (for years now).
Yes, this is normal. You cannot NAT to an address to wake up the machine because when the machine is off it has no IP address.
You can use the WOL Agent to run on a server on your net, and it will broadcast the wol packets to your lan like a repeater.
Please contact us on github or look at wol.aquilatech.com for more information.
From: Joseph Dupre [mailto:jdupre@users.sf.net]
Sent: Monday, July 24, 2017 2:22 AM
To: [aquilawol:discussion]1105198@discussion.aquilawol.p.re.sf.net
Subject: [aquilawol:discussion] Must WOL packets be broadcast, or may they be unicast?
I am able to wake up a particular machine with the Wake On LAN tool on my LAN, so I know I have the BIOS and Windows 10 settings enabling WOL. Now I am trying to wake up the machine via the internet. Aparently my firewall does not allow port forwarding to a broadcast address, so I set up a rule to forward to the specific NAT address of the machine I want to wake up. When the machine is awake, and I have the "Listener" window open, when I send the WOL pakect over the internet it is displayed in the Listener window. Everything is correct: the NAT address, the port and MAC. However, when the machine is sleeping and I send the WOL packet over the internet, the machine does not wake up.
So my question is, is it typical that a sleeping NIC only listens to broadcast magic packets??? Any other idea why the internet wake up call gets displayed in the Listener when awake, but does not wake up the machine when sleeping?
Thanks for the reply. Your web site directed me to Source Forge for support. Is there a better forum?
I installed WOL Agent on Windows 7 Pro. I see that the service is running. With Wireshark I see the incoming packets from the internet that pass through my firewall to the WOL Agent machine. However, there are no broadcast WOL packets being sent out.
I disabled the firewall, and now I see the broadcast packets. Enable the firewall, and broadcast packets do not get sent. How do I set up a rule to allow the WOL Agent service to send the broadcast WOL packets to the LAN?
Joe
Last edit: Joseph Dupre 2017-07-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You need to allow UDP port 9 packets through the firewall.
You say "your web site directed me to source forge".
Our website points to Github for support. Can you reply with the URL of the website you are referring to?
I'll try and respond with better detail soon...
From: Joseph Dupre [mailto:jdupre@users.sf.net]
Sent: Wednesday, July 26, 2017 2:00 AM
To: [aquilawol:discussion]1105198@discussion.aquilawol.p.re.sf.net
Subject: [aquilawol:discussion] Must WOL packets be broadcast, or may they be unicast?
Thanks for the reply. You web site directed me to Source Forge for support. Is there a better forum?
I installed WOL Agent on Windows 7 Pro. I see that the service is running. With Wireshark I see the incoming packets from the internet that pass through my firewall to the WOL Agent machine. However, there are no broadcast WOL packets being sent out.
I disabled the firewall, and now I see the broadcast packets. Enable the firewall, and broadcast packets do not get sent. How do I set up a rule to allow the WOL Agent service to send the broadcast WOL packets to the LAN?
My mistake. Apparently Google directed me here, not your website.
It was Windows's firewall that was blocking the incoming packets, so WOL Agent never got them, thus no broadcasts. Adding a rule to Windows firewall solved that. (I forgot that Wireshark taps in before the firewall, that's why I was confused to see the incoming unicast packet but not the outgoing broadcast.)
All is good. Thanks for the cool tool.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm glad you got it working.
I'm going to add the firewall rules automatically in a future release.
I don't know why Google insists on pointing to a 5 year old out of date link. Oh well.
From: Joseph Dupre [mailto:jdupre@users.sf.net]
Sent: Thursday, July 27, 2017 9:35 PM
To: [aquilawol:discussion]1105198@discussion.aquilawol.p.re.sf.net
Subject: [aquilawol:discussion] Must WOL packets be broadcast, or may they be unicast?
My mistake. Apparently Google directed me here, not your website.
It was Windows's firewall that was blocking the incoming packets, so WOL Agent never got them, thus no broadcasts. Adding a rule to Windows firewall solved that. (I forgot that Wireshark taps in before the firewall, that's why I was confused to see the incoming unicast packet but not the outgoing broadcast.)
I am able to wake up a particular machine with the Wake On LAN tool on my LAN, so I know I have the BIOS and Windows 10 settings enabling WOL. Now I am trying to wake up the machine via the internet. Aparently my firewall does not allow port forwarding to a broadcast address, so I set up a rule to forward to the specific NAT address of the machine I want to wake up. When the machine is awake, and I have the "Listener" window open, when I send the WOL pakect over the internet it is displayed in the Listener window. Everything is correct: the NAT address, the port and MAC. However, when the machine is sleeping and I send the WOL packet over the internet, the machine does not wake up.
So my question is, is it typical that a sleeping NIC only listens to broadcast magic packets??? Any other idea why the internet wake up call gets displayed in the Listener when awake, but does not wake up the machine when sleeping?
Hi, I am not sure if I can reply to this as I don't even have a source forge account anymore (for years now).
Yes, this is normal. You cannot NAT to an address to wake up the machine because when the machine is off it has no IP address.
You can use the WOL Agent to run on a server on your net, and it will broadcast the wol packets to your lan like a repeater.
Please contact us on github or look at wol.aquilatech.com for more information.
From: Joseph Dupre [mailto:jdupre@users.sf.net]
Sent: Monday, July 24, 2017 2:22 AM
To: [aquilawol:discussion] 1105198@discussion.aquilawol.p.re.sf.net
Subject: [aquilawol:discussion] Must WOL packets be broadcast, or may they be unicast?
I am able to wake up a particular machine with the Wake On LAN tool on my LAN, so I know I have the BIOS and Windows 10 settings enabling WOL. Now I am trying to wake up the machine via the internet. Aparently my firewall does not allow port forwarding to a broadcast address, so I set up a rule to forward to the specific NAT address of the machine I want to wake up. When the machine is awake, and I have the "Listener" window open, when I send the WOL pakect over the internet it is displayed in the Listener window. Everything is correct: the NAT address, the port and MAC. However, when the machine is sleeping and I send the WOL packet over the internet, the machine does not wake up.
So my question is, is it typical that a sleeping NIC only listens to broadcast magic packets??? Any other idea why the internet wake up call gets displayed in the Listener when awake, but does not wake up the machine when sleeping?
Must WOL packets be broadcast, or may they be unicast?https://sourceforge.net/p/aquilawol/discussion/1105198/thread/fef182b8/?limit=25#b0bd
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/aquilawol/discussion/1105198/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Thanks for the reply. Your web site directed me to Source Forge for support. Is there a better forum?
I installed WOL Agent on Windows 7 Pro. I see that the service is running. With Wireshark I see the incoming packets from the internet that pass through my firewall to the WOL Agent machine. However, there are no broadcast WOL packets being sent out.
I disabled the firewall, and now I see the broadcast packets. Enable the firewall, and broadcast packets do not get sent. How do I set up a rule to allow the WOL Agent service to send the broadcast WOL packets to the LAN?
Last edit: Joseph Dupre 2017-07-26
You need to allow UDP port 9 packets through the firewall.
You say "your web site directed me to source forge".
Our website points to Github for support. Can you reply with the URL of the website you are referring to?
I'll try and respond with better detail soon...
From: Joseph Dupre [mailto:jdupre@users.sf.net]
Sent: Wednesday, July 26, 2017 2:00 AM
To: [aquilawol:discussion] 1105198@discussion.aquilawol.p.re.sf.net
Subject: [aquilawol:discussion] Must WOL packets be broadcast, or may they be unicast?
Thanks for the reply. You web site directed me to Source Forge for support. Is there a better forum?
I installed WOL Agent on Windows 7 Pro. I see that the service is running. With Wireshark I see the incoming packets from the internet that pass through my firewall to the WOL Agent machine. However, there are no broadcast WOL packets being sent out.
I disabled the firewall, and now I see the broadcast packets. Enable the firewall, and broadcast packets do not get sent. How do I set up a rule to allow the WOL Agent service to send the broadcast WOL packets to the LAN?
Must WOL packets be broadcast, or may they be unicast?https://sourceforge.net/p/aquilawol/discussion/1105198/thread/fef182b8/?limit=25#229d
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/aquilawol/discussion/1105198/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
My mistake. Apparently Google directed me here, not your website.
It was Windows's firewall that was blocking the incoming packets, so WOL Agent never got them, thus no broadcasts. Adding a rule to Windows firewall solved that. (I forgot that Wireshark taps in before the firewall, that's why I was confused to see the incoming unicast packet but not the outgoing broadcast.)
All is good. Thanks for the cool tool.
I'm glad you got it working.
I'm going to add the firewall rules automatically in a future release.
I don't know why Google insists on pointing to a 5 year old out of date link. Oh well.
From: Joseph Dupre [mailto:jdupre@users.sf.net]
Sent: Thursday, July 27, 2017 9:35 PM
To: [aquilawol:discussion] 1105198@discussion.aquilawol.p.re.sf.net
Subject: [aquilawol:discussion] Must WOL packets be broadcast, or may they be unicast?
My mistake. Apparently Google directed me here, not your website.
It was Windows's firewall that was blocking the incoming packets, so WOL Agent never got them, thus no broadcasts. Adding a rule to Windows firewall solved that. (I forgot that Wireshark taps in before the firewall, that's why I was confused to see the incoming unicast packet but not the outgoing broadcast.)
All is good. Thanks for the cool tool.
Must WOL packets be broadcast, or may they be unicast?https://sourceforge.net/p/aquilawol/discussion/1105198/thread/fef182b8/?limit=25#94c9
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/aquilawol/discussion/1105198/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/