I had this issue. I had setup port forwarding to send udp/port9 traffic to my HTPC and it worked sometimes, other times not. My home router is a D-Link DSL-G604T, which it turns out doesn't support forwarding WOL packets very well. The issue was that sometimes my router had an arp entry for my HTPC and other times it didn't. The only way to ensure it always had one, was to set a static arp entry. This however doesn't survive a reboot of the router, but I can live with that as it doesn't happen very often. Here are my notes:
Trying 10.1.1.1...
- Access modem via browser at http://10.1.1.1:8080/
- Tools tab>Admin>Remote Telnet Management
- Enable and set IP & Netmask details of computer that will telnet to modem
- $ telnet 10.1.1.1
Connected to 10.1.1.1.
Escape character is '^]'.
BusyBox on (none) login: admin
Password: ********
BusyBox v0.61.pre (2007.05.09-12:40+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
# arp -s 10.255.255.254 FF:FF:FF:FF:FF:FF
# arp
Address Hwtype Hwaddress Flags Mask Iface
10.1.1.11 ether E0:CB:4E:24:F9:26 C br0
10.255.255.254 ether FF:FF:FF:FF:FF:FF CM br0
This results in the address 10.255.255.254 becoming a pseudo broadcast address for the WOL packet on my LAN. Create a port forward for upd/port9 traffic to this address, send your WOL packet with the MAC of your HTPC's NIC to your routers external IP, and Job done.
- Configure port forwarding on modem for UDP port 9 to 10.255.255.254
- Note: Static ARP entry will not survive modem reboot
Well, thanks for the tips. Will try that. But the strange thing is that WOL over 3G works flawless in other apps. So I now have a seperate App witch sends the WOL package and then Ampdroid does the rest. This is not perfect, but it works.