Posted: Sat Mar 21, 2015 8:23 Post subject: VPN and DDNS not responding
I am using Linksys E1200 v2 and DD-WRT v24-sp2 (02/04/15) big - build 26138 and today I wanted to activate VPN with DDNS (like I already did on same router on other location). And the problem is that I can't connect to that VPN from anywhere and at DDNS settings I used freedns.afraid.org (same settings like on other location which works) but on the bottom at DDNS status where there should be log about connection there's just "Connecting to server" all the time.
And the router (who has local IP 192.168.0.1) is connected directly to modems (which has local IP 192.168.1.1) port, I'm not sure if I should maybe open/forward some ports on modem to my router's IP or something which will allow DDNS and VPN connection?
I assume this is a VPN “server” configuration. Would be nice to know which one (PPTP or OpenVPN).
If the modem is really a combo modem+router, then I would assign a static IP to the WAN of the dd-wrt router from the network of the modem+router, and place that IP in the DMZ of the modem+router. Now anything that’s blocked by the modem+router’s firewall will be passed to your router.
As far as DDNS, you can’t rely on the traditional configuration for DDNS when it’s NOT the primary router. By default, DDNS will always use the WAN ip of the router, which in this case is a private IP from the modem+router! What would work best is to have the modem+router handle it since it has the public IP. Or else you need to use an alternate approach for setting up DDNS on the dd-wrt router that uses a public IP checker rather than the WAN.
For example, try adding the following to the Additional DDNS Options field:
You configure a static IP from the modem+router's network (something not in use elsewhere, and not part of its DHCP server pool of IPs) to the WAN of your dd-wrt router. You then add that IP to the DMZ of the modem+router. Now the modem+router knows to forward traffic that it would otherwise block to that IP, which is, of course, your dd-wrt router.
Looks like the DDNS page may have changed, at least for some builds. I know at one time there was a field for additional DNS configuration. But I see on my recent Kong build it now has an option called “Use external ip check”, which is the same thing. It will bypass the WAN and determine your public IP using some website designed for that purpose.