Securifi Community Forum
Securifi Products => Almond+ => Topic started by: preternaturous on January 26, 2015, 12:51:46 pm
-
I usually put my Computer to sleep when I'm not using it. I want to be able to set up wake on wireless LAN so that I can use Chrome Remote Desktop to wake up and use my computer remotely. I have Windows set up properly, but it's not working. My belief is that the Almond+ does not support this. Is there a way to set this up?
-
Can you clarify what you mean by "the Almond+ does not support this." What do you mean by "this"?
If you mean, "forward wake on lan packets", the the Almond most certainly can. Just add a port forward for the magic packets (UDP 7 or 9 usually).
If you mean "Generate Wake on LAN packets in response to other traffic", then I think you're right. Very few routers have this functionality out of the box.
It's my understanding that Chrome Remote Desktop does not send out WoL packets. Ref:
https://productforums.google.com/forum/#!topic/chrome/rABmxceLRNk
You will need to send the packet yourself. OpenWRT has knockd and wol packages that can be used to set up automation. Basically, you'd have knockd run a wol command when triggered by an inbound connection on some other port. These will have to be installed - they are not stock on A+.
There's some really good info here, including web and Windows WOL packet generators:
http://www.wolcenter.com/faq.php
Also, there's an iWOL app for iPhone, and "Wake on LAN" for Android that can generate the wake-up packets for you if you have forwarding properly configured.
Ref: http://lifehacker.com/5786791/rule-your-computer-from-afar-by-setting-up-wake-on-lan
I highly recommend you test WOL on the local LAN to ensure it actually works, prior to troubleshooting anything else.
-
This is exactly the information I needed, thanks!! I know what I'm playing with tonight!
-
Okay. So I configured a port and also downloaded the WoL app on my android phone and got it set up. When I send a command, I know the router sees it, because the log changes. However, I'm not sure what the log is really saying, and my computer is not waking.
Jan 27 04:27:06 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.192.152.143, is not in any valid net for upstream VIF.
Jan 27 04:27:19 AlmondPlus user.info sysinit: RECV Membership query from 10.10.10.254 to 224.0.0.1
Jan 27 04:27:20 AlmondPlus user.info sysinit: RECV V2 member report from 10.10.10.142 to 239.255.255.250
Jan 27 04:27:20 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Jan 27 04:27:20 AlmondPlus user.info sysinit: The source address 10.10.10.142 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:27:23 AlmondPlus user.info sysinit: RECV V2 member report from 10.10.10.254 to 224.0.0.2
Jan 27 04:27:23 AlmondPlus user.info sysinit: The IGMP message was from myself. Ignoring.
Jan 27 04:27:24 AlmondPlus user.info sysinit: The source address 10.10.10.146 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:27:25 AlmondPlus user.info sysinit: RECV V2 member report from 10.10.10.142 to 224.0.1.60
Jan 27 04:27:25 AlmondPlus user.info sysinit: Updated route entry for 224.0.1.60 on VIF #1
Jan 27 04:27:27 AlmondPlus user.info sysinit: RECV V2 member report from 10.10.10.108 to 239.192.152.143
Jan 27 04:27:27 AlmondPlus user.info sysinit: Updated route entry for 239.192.152.143 on VIF #1
Jan 27 04:27:36 AlmondPlus user.info sysinit: iface = br-lan
Jan 27 04:27:36 AlmondPlus user.info sysinit: IP address is already set for the interface
Jan 27 04:27:42 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.192.152.143, is not in any valid net for upstream VIF.
Jan 27 04:27:44 AlmondPlus user.info sysinit: The source address 10.10.10.146 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:28:21 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:28:30 AlmondPlus user.info sysinit: iface = br-lan
Jan 27 04:28:30 AlmondPlus user.info sysinit: IP address is already set for the interface
Jan 27 04:28:33 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:28:48 AlmondPlus daemon.info hostapd: wlan00: STA ac:22:0b:be:89:9f WPA: group key handshake completed (RSN)
Jan 27 04:28:50 AlmondPlus daemon.info hostapd: wlan10: STA 9c:b6:54:de:d0:cc WPA: group key handshake completed (RSN)
Jan 27 04:28:51 AlmondPlus daemon.info hostapd: wlan10: STA 28:98:7b:d5:3f:41 WPA: group key handshake completed (RSN)
Jan 27 04:28:51 AlmondPlus user.info sysinit: The source address 10.10.10.146 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:29:10 AlmondPlus user.info sysinit: The source address 10.10.10.146 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:29:21 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:29:25 AlmondPlus user.info sysinit: RECV Membership query from 10.10.10.254 to 224.0.0.1
Jan 27 04:29:25 AlmondPlus user.info sysinit: RECV V2 member report from 10.10.10.108 to 239.192.152.143
Jan 27 04:29:25 AlmondPlus user.info sysinit: Updated route entry for 239.192.152.143 on VIF #1
Jan 27 04:29:25 AlmondPlus user.info sysinit: RECV V2 member report from 10.10.10.254 to 224.0.0.2
Jan 27 04:29:25 AlmondPlus user.info sysinit: The IGMP message was from myself. Ignoring.
Jan 27 04:29:27 AlmondPlus user.info sysinit: RECV V2 member report from 10.10.10.142 to 239.255.255.250
Jan 27 04:29:27 AlmondPlus user.info sysinit: Updated route entry for 239.255.255.250 on VIF #1
Jan 27 04:29:27 AlmondPlus user.info sysinit: The source address 10.10.10.142 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:29:30 AlmondPlus user.info sysinit: iface = br-lan
Jan 27 04:29:30 AlmondPlus user.info sysinit: IP address is already set for the interface
Jan 27 04:29:33 AlmondPlus user.info sysinit: The source address 10.10.10.108 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:29:34 AlmondPlus user.info sysinit: RECV V2 member report from 10.10.10.142 to 224.0.1.60
Jan 27 04:29:34 AlmondPlus user.info sysinit: Updated route entry for 224.0.1.60 on VIF #1
Jan 27 04:29:39 AlmondPlus user.info sysinit: The source address 10.10.10.146 for group 239.255.255.250, is not in any valid net for upstream VIF.
Jan 27 04:30:30 AlmondPlus user.info sysinit: iface = br-lan
Jan 27 04:30:30 AlmondPlus user.info sysinit: IP address is already set for the interface
Jan 27 04:31:21 AlmondPlus daemon.info hostapd: wlan10: STA 10:a5:d0:47:45:34 IEEE 802.11: associated
Jan 27 04:31:21 AlmondPlus daemon.info hostapd: wlan10: STA 10:a5:d0:47:45:34 RADIUS: starting accounting session 54C5F3B9-00000005
Jan 27 04:31:21 AlmondPlus daemon.info hostapd: wlan10: STA 10:a5:d0:47:45:34 WPA: pairwise key handshake completed (RSN)
Jan 27 04:31:22 AlmondPlus daemon.info dnsmasq-dhcp[3656]: DHCPREQUEST(br-lan) 10.10.10.150 10:a5:d0:47:45:34
Jan 27 04:31:22 AlmondPlus daemon.info dnsmasq-dhcp[3656]: DHCPACK(br-lan) 10.10.10.150 10:a5:d0:47:45:34 android-6daf8c0242a2f384
Jan 27 04:31:24 AlmondPlus user.info sysinit: The source address 10.10.10.146 for group 239.255.255.250, is not in any valid net for upstream VIF.
-
For this test, is your android on the local LAN / WLAN?
If so, then try the broadcast address instead of direct, since ARP entries expire after 20 mins.
WOL 10.10.10.255 MACMACMAC
Make sure the MAC address is the target system's mac.
EDIT:
Also, make sure your ARP and DHCP tables still show the adapter logged in to the wireless network (from OpenWRT, you can see wireless clients).
Or, wake up the computer, ping it, then put it to sleep, and immediately ping it.
If you cannot ping it before ARP cache expires, then your computer is not configured correctly to allow WoWLAN.
BIOS, Adapter, Drivers, and Driver settings are all needed.
-
I want to be able to set up wake on wireless LAN so that I can use Chrome Remote Desktop to wake up and use my computer remotely.
Wake-on-LAN doesn't work over Wi-Fi (aka wireless LAN). You need to use Ethernet.
-
Wireless WOL is possible but your wireless adapter / computer / OS all have to be compatible with it.
http://www.howtogeek.com/70374/how-to-geek-explains-what-is-wake-on-lan-and-how-do-i-enable-it/
-
Wireless/Wi-Fi *IS* Ethernet. It's important to be precise and accurate in technology.
Wake-on-LAN doesn't work over Wi-Fi (aka wireless LAN). You need to use Ethernet.
As a blanket statement that is false. It depends on the device and its drivers.
Basically, the WLAN card has to maintain link and be powered during suspended S3/S4 states.
It seems like v15.6 of the ProSet drivers support it.
Intel requirements for Wireless Wake on LAN:
https://communities.intel.com/message/224711#224711
A write-up/review of setting up WWoL/WoWL:
http://revolutionwifi.blogspot.com/2010/11/wake-on-wireless-lan.html
Intel references Wake on WLAN is supported:
http://www.intel.com/Assets/PDF/perfbrief/mobiletechnology.pdf
Now, I'm not saying it will work for preternaturous. I don't know his whole setup, which is why I'm having him try directly rather than through all of the gazillion pieces.
-
So, apparently my BIOS doesn't support wake on wireless LAN, which is fine. Now that I know, I've bought a longer ethernet cable and I'm wired in, so WoL is now working. However, what I was really wanting was Wake on WAN, i guess. I want to be able to send a magic packet from my phone when I'm not home. And when I plug in the almond plus internet IP, WoL isn't working. It does however work over the local network. Is there something I need to forward or enable on the almond plus?
-
Yah. Look back through the links I posted. I think they cover the exact port and forwarding rules to use. It's UDP, and a single digit port. (maybe 6-9?)
I'm not sure of the A+ supports forwarding to broadcast, but try that first, since it would let you do multiple systems WoL.
If that doesn't work, then set the MAC address of the PC to a fixed IP, and forward to that IP.