It is currently running Firmware: DD-WRT v24-sp2 (05/27/13) mega
pptp server is enabled
My home network is 172.25.1.0/24
The routers address is 172.25.1.254
my vpn network is 10.5.9.0/24
and the vpn interface is 10.5.9.254
and my router is directly connected to my cable modem with a public IP address, obtained by way of DHCP.
I can vpn to my public IP address fine.
When I connect, though, I lose the ability to connect to the internet.
A default route of 0.0.0.0 is set for the ppp interface. If I disable obtaining routes for the vpn connection, then I am able to successfully connect to the vpn and i have internet connection fine.
Problem is, I don't have access to my home network of 172.25.1.0/24 until i manually add the route on any client with the following command:
Interesting, Can you explain what your goal is? Every time I setup PPTP VPN, its pretty easy and straight forward but I have my VPN clients directly connect to my internal subnet. So since my subnet is 192.168.0.0/24 I specify a range that DHCP doesn't hand out address too, so I can assign then to VPN clients. I figured the goal of VPN is to have access to your internal network, whats the point of having a whole nother /24 network and having to create routing rules when you can have the directly connected to the internal subnet?
the goal is to access the internal network and route internet traffic through internal gateway.
i haven't been able to connect to the vpn unless the vpn address is in a different subnet than my internal network, even if i give the vpn network a range of addresses outside of what dhcp issues
you may require adding a port forward rule to forward to itself.
"If you have followed the above steps and still cannot connect to the VPN, try forwarding the PPTP Port (1723) with TCP protocol to the LAN IP Address of your router (i.e. 192.168.1.1). Although it seems like this is a weird approach since you are using your router to forward to itself, it often times allows the VPN connection to succeed."
you may require adding a port forward rule to forward to itself.
"If you have followed the above steps and still cannot connect to the VPN, try forwarding the PPTP Port (1723) with TCP protocol to the LAN IP Address of your router (i.e. 192.168.1.1). Although it seems like this is a weird approach since you are using your router to forward to itself, it often times allows the VPN connection to succeed."
Nope.
pptpd isn't starting on the router now for some reason.
well, port 1723 isn't open anyway and I can't seem to get it up. config is broken somewhere. think i'm ready to just dmz to my linux box and just let that handle all this stuff
1) make sure you test first with CHAP auth with the list of user in the box provided. Make sure they are exactly as described username * password *. Start with a very basic username and pass no special characters.
2) Make sure you open the port 1723 on the firewall.
iptables -I INPUT -p tcp --dport 1723 -j ACCEPT
you can also use logaccept if you want the connections to be logged. I hope this helps get your pptp vpn working. Like I stated it should OK to use the local internal subnet, just make sure they aren't being handed out by DHCP. Also make sure the internal IP from where you are attempting to connect from doesn't have the same subnet as yours. Example if your internal subnet is 192.168.1.0/24. then when connecting from another places network make sure they are not using teh same 192.168.1.0/24 subnet else the vpn tunnel gets confused so to speak.
I can't remember exactly where the log files for pptp are but you can always use the find command to help look for it.
Example: find / -iname *pptp* (will look for all files with pptp in its name right from the root directory.
Else look in /var/log/messages for the default log information.
