Posted by1 year ago
Jul 18, 2017 It can be used on a wide rage of devices, like: desktops, laptops, routers, gaming consoles, smartphones, tablets, etc. In this guide, we will help you configure OpenVPN on any TP-Link router. I) Setting Up OpenVPN on TP-Link Router. Before connecting to OpenVPN from any TP-Link router, you need to first set up OpenVPN on your router. Hi, I recently purchased a TL-R600VPN router but my work laptop can't connect to my work VPN. Laptop: Macbook Pro. OSX El Capitan. Using Network preferences to connect.
Archived
Hi folks,
I am currently trying to get wake-on-lan to work over my VPN and not having much success, so far:
- I'm trying to send a WOL packet from an Android phone (OnePlus 5).
- I've confirmed that WOL works on the local net, that being 192.168.1.0
- I've confirmed that WOL packets are received by the computer I am trying to wake when it is on and has a static IP assignment, these are successfully received regardless of which VPN the phone is connected to (and Wi-Fi is off)
- The only difference that I can see is that when sent locally the packet is received directly from the phone's IP, however when it is sent over the VPN the packet appears to come from the NAS (though I would expect this). The sending address comes from the 192.168.1.0 net despite the VPNs being allocated 192.168.2.0 and 192.168.3.0 nets respectively - this is what I want.
However the problem occurs when I turn the computer off, WOL will then work on the Wi-Fi (same subnet) but not over VPN.
I'm not sure what will be relevant so I'll detail everything about my setup:
- Internet is provided using PPPoE and uses Openreach FTTC with a separate fiber modem.
- TP-Link WDR-3600 running DD-WRT is connected to the modem/internet over the WAN port and connected to a 3Com Switch 4200G 48-Port LAN switch (an older corporate-style 48 port gigabit switch) via LAN port 1.
- The VPNs are hosted on a Synology DS415+ NAS and occupy 192.168.2.0 (OpenVPN) and 192.168.3.0 (L2TP/IPSec), the NAS is connected to the switch using LACP link-aggregation.
- The target computer is connected to the switch directly via Ethernet and uses a static IP set in the NIC properties, the target computer is dual-booting Windows 8.1 and Windows 10 (W10 just for GoW 4...)
- DCHP is set for 192.168.1.100 - 192.168.1.240 with addresses outside of this range set manually (>240 for networking gear, <100 for my own Client devices with static addresses).
- Wi-Fi is provided by a Unity Unify-Pro Access Point but generally only has 3-5 devices connected
- I know the NIC is configured correctly because WOL works locally - so frustrating!
Things I've tried:
- Using the 'Advanced Routing' section of DD-WRT to bridge the subnet's as I understand there may be a problem with layer 3 traversal for the WOL packets. However since I tried that I successfully received WOL packets on the target PC while it was on (as stated above) indicating this isn't the problem.
- Ensured VPN pass-through is enabled for all protocols
- The SPI firewall is enabled, but all VPN traffic makes it to the local net so I don't see this being the issue
- I setup a rule in the port-forwarding to route all traffic from my NAS' IP to my PC's IP (which is statically assigned) on port 9
I used to have a Billion 9600N router and it had a 'Static ARP' feature which allowed you to assign IP addresses to MAC addresses from the router, rather than from the computer. I believe I had WOL over VPN working with this though that was about 4 years ago.
From what I understand Static ARP just assigns a fixed address to a Client when they are detected on the network but I can't find a similar feature in the DD-WRT settings and I don't actually know if this will resolve my issue.
Please help!
4 comments
This question already has an answer here:
- machine wakes only on local magic packet 2 answers
I'm trying to setup wake on lan. My router doesn't allow port forwarding to broadcast so I've binded the mac address of my system to a static ip in the router's control panel. I've also forwarded port 9 to the ip I've set, so when the router gets a request it should forward it to the mac address of my computer. The only problem is that, for some reason, the computer wakes through lan but not through wan. I'm using android's WolOn app to send the magic packet and I've Kali linux installed on my system. My router is a TP-Link TD-W8961ND ver 3.0. Thanks for the help!
UPDATE: I've run tcpdump, turns out that my machine receives the magic packet both on lan and wan. For some reason, it doesn't wake on wan. Could it be that the system refuses wan magic packets? They seem to be different from the lan ones
Deci
DeciDeci
marked as duplicate by Kamil Maciorowski, n8te, music2myear, Spiff networkingApr 5 '18 at 23:59
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
1 Answer
From Wiki:
It is possible to launch a Wake-on-LAN through the Internet, to a machine located behind a NAT router, but this under certain conditions: the magic package must be a UDP packet, whose used port is redirected to the IP address of the machine that needs to be awake. The computer is off, so it is necessary to permanently configure the MAC address / IP address association in the ARP table of the router (otherwise, this association expires in the router after about 5 minutes, and the magic package will not be directed to the machine). Some routers can wake a machine from the local network through their web interface or via telnet.
When you say : I've binded the mac address of my system to a static ip in the router's control panel ...
Have you add an entry into ARP table ?
f14284f14284