Posted: Mon Jul 21, 2025 11:49 Post subject: Failed to change TP-link to LinkSys in dd-wrt VPN tunnel
Task: Connect two sites - Main with white IP and Remote with gray IP behind ISP NAT to get access to all LAN devices at remote position from Main network.
I've got two TP-link WR-841ND routers : DD-WRT v3.0-r44715 std (11/03/20).
One of them is VPN (PPTP server)
Broadcast support - disabled
MPPE Encryption - enabled
MTU/MRU - 1436
Second one WR-841ND on remote postion
WAN - disabled,
Local IP within ISP router network
DHCP forwarder
Gateway to ISP router
Advanced Routing - operation mode - Router
VPN (PPTP client)
Server Ip Main.site.IP.address --nobuffer
MPPE Encryption - mppe required
MTU/MRU - 1436
NAT - Disable
Router on remote position has custom bash script that check if connection is lost initiate in again and add route to this gateway.
route add -net 192.168.1.0 netmask 255.255.255.0 gw <ip-address-of-pptp-client>.
This configuration works! BUT....
CPU of WR-841nd too weak to handle VoIP data. Moreover, WR-841 has no JFFS2 support to keep the bash script and if router's power is lost then I need to connect to Remote Router via SSH by VPN tunnel and inject there script again to restore whole system configuration.
Now I got LinkSys E3000 more powerful router
I Flashed it with dd-wrt.v24-44715_NEWD-2_K2.6_mini-e3000.bin
Copy all settings for VPN as it was for WR-841nd , except some differences in
Setup - Switch Config
WR-841ND has all ports Assigned to Brige - None
but E3000 need to set Assigned to Brige - LAN or I lost access to it.
Also E3000 has some differences in Setup - Networking Tab regarding WAN (there is no such field for WR-841).
The Issue
LinkSys E3000 is connecting to main PPTP server. My bash script works ok by cron and
add required record to route but.
There is no pings to local LAN devices from Main site. It looks like some internal Firewall is exist inside E3000 or I missed sothing...
So any ideas what to check or what settings to add in E3000 to set-up system?
Joined: 08 May 2018 Posts: 16703 Location: Texas, USA
Posted: Mon Jul 21, 2025 17:38 Post subject:
And you stopped at the router database and did not pass GO. PPTP is insecure and not advised. WireGuard is probably a safer bet. So is a more current release.