VPN on cascaded router will not connect anymore.

AlejandroL

Commendable
Oct 27, 2016
17
0
1,520
A lot has been written about this, but after reviewing more than 70 or 80 posts I can't for the life of me figure out what's going on with my setup, so any help would be GREATLY appreciated.

1. I have a tp-link 750AC Archer C2 router connected to my ISP thru the WAN port. (Router 1 or R1)
2. IP Range for LAN on R1 is 192.168.1.0/24 - Gateway & R1 IP is 192.168.1.1 - R1 DHCP range 192.168.1.100 to 119
3. I have a second router (same model, Router 2 or R2) cascaded to the first router thru its WAN port. (WAN on R2 connected to LAN R1).
4. The IP of the WAN port on R2 is 192.168.1.2. The IP for R2 WAN port is reserved using its MAC address in R1,
5. IP range for LAN on R2 is 192.168.2.0/24 - Gateway & R2 IP is 192.168.2.1 - R2 DHCP range 192.168.2.100 to 119
6. R1 has IP 192.168.1.2 (R2 WAN port) set as DMZ.
7. R1 has SPI Firewall Enabled, PPTP Pass-through:Enable, L2TP Pass-through:Enable & IPSec Pass-through:Enable
8. R1 gets a dynamic IP from my ISP.
9. NAT, Hardware NAT and Firewall are disabled on R2.

OK, so for the last year the IP I was dynamically assigned by my ISP was in a segment A.B.C.20 netmask 255.255.255.0 and I was able to connect R2 using L2TP and PPTP to my office's VPN.

As of 3 days ago my ISP assigned me a new dynamic IP address in the A.B.D.166 network with netmask 255.255.240.0 and since then the VPN connection can not be established. R1 still assigns R2 the correct internal IP, and no configuration has changed, at least not in my settings. I checked the ISP's A.B.D.166 IP and it is not blacklisted, and if I input my L2TP or PPTP credentials on R1, R1 does connect to the office's VPN with out problem, but I am left with no internet here at home.

I thought that the router might be broken or something, so I switched R1 with R2 and all the configurations and get the same results, and both can connect if they are not cascaded. Both routers have the latest firmware.

I also tried with a dlink dir-855 and a dlink dir-655 which I had laying around, and the same, when set up as R1 they can connect to either ISP or Office's VPN, but when cascaded they don't connect.

Please, this is driving me insane... I don't know what else to do, but I'll try anything.
Could it be something with the ISP's new IP? But if that is the case, why is it letting me connect to my office's VPN thru Router 1.
I doubt that the DMZ is not working on 4 different routers. I've opened up both UDP and TCP ports 1723, 500, 4500, 1701, etc for L2TP and PPTP to work as well (just in case)

I've even tried using Russian L2TP and Russian PPTP with the same results (and BTW, if someone could explain the difference between the regular tunnels and the russian ones, I would also appreciate it).

PLEASE! Any ideas and or suggestions are welcomed, and thank you in advance for your help.
Alex
 

AlejandroL

Commendable
Oct 27, 2016
17
0
1,520
That's just the way I was told to set it up a long time ago and it worked without a hitch for a long time... Now it doesn't...
I believe that this was done this way so that you could select the wifi networks from either router and either have a normal connection to the internet and or connect to the office's VPN directly. Each router handles its own DHCP for devices that connect to them.
If there is some other way to do it I don't mind trying it.
 


No that would make sense if you wanted to separate vpn traffic. The issue really stems from the router setup, cascading these types of routers is not ideal. A better solution would be a single router with multiple interfaces would would use a single gateway. This needn't be expensive but would give better more stability, function and control. I use Pfsense in a lot of situations and the hardware can either be a re-tasked pc but these aren't very power efficient r a purpose built box such as an ALIX board. The os is a freebsd distribution. (You could use the old routers as just WAPS.
 

AlejandroL

Commendable
Oct 27, 2016
17
0
1,520
Well... No wonder I felt like a stooge looking all over for the solution...
The IT guy from my office showed up half an hour ago and in 20 minutes had everything fixed the way it was described above.
According to him the issue is that the primary router (R1) seems to be broken and its ability to let traffic thru is busted. He thinks it was probably a power spike that fried something.
So he reconfigured R2 to be R1 (since it is a gigabit router and has VPN passthru), and added the D-Link DIR-855 as R2 with the configuration mentioned above and voila! Everything works again...

nigelivey, thanks for the advice, and I was about to look into that, but the problem is that most countries outside the US don't have those types or routers readily available, nor do they ship them to countries, like in my case, Mexico. The places that do ship them internationally usually charge an arm and a leg for them. BTW, do you know what the difference is between the Russian L2TP and Russian PPTP versus regular L2TP and PPTP?