I have a centos 5 pptp server. I can connect to it with no problem from iPhone , android, pc, Mac, etc.
However my ddwrt router won't connect to it. My ddwrt router connects fine to professional pptp services. So I assume the issue is my pptp server.
Likely there is some option in my pptpd.conf that will help resolve this.
Anybody have any idea?
EDIT
Sorry to lack those details.
I have monitored the logs and when the DD-WRT client attempts to connect it does not provide too much useful info:
Feb 7 12:22:40 la1 pptpd[3150]: CTRL: Client 190.53.138.114 control connection finished
Feb 7 12:24:58 la1 pptpd[3154]: CTRL: Client 190.53.138.114 control connection started
Feb 7 12:24:59 la1 pptpd[3154]: CTRL: Starting call (launching pppd, opening GRE)
Feb 7 12:24:59 la1 pppd[3155]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
Feb 7 12:24:59 la1 pppd[3155]: pppd 2.4.4 started by root, uid 0
Feb 7 12:24:59 la1 pppd[3155]: Using interface ppp0
Feb 7 12:24:59 la1 pppd[3155]: Connect: ppp0 <--> /dev/pts/3
Feb 7 12:25:05 la1 pppd[3155]: Modem hangup
Feb 7 12:25:05 la1 pppd[3155]: Connection terminated.
Feb 7 12:25:05 la1 pppd[3155]: Connect time 0.1 minutes.
Feb 7 12:25:05 la1 pppd[3155]: Sent 10 bytes, received 0 bytes.
Feb 7 12:25:05 la1 pppd[3155]: Exit.
Feb 7 12:25:05 la1 pptpd[3154]: CTRL: Client 190.53.138.114 control connection finished
Feb 7 12:25:10 la1 pptpd[3156]: CTRL: Client 190.53.138.114 control connection started
Feb 7 12:25:11 la1 pptpd[3156]: CTRL: Starting call (launching pppd, opening GRE)
Feb 7 12:25:11 la1 pppd[3157]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
Feb 7 12:25:11 la1 pppd[3157]: pppd 2.4.4 started by root, uid 0
Feb 7 12:25:11 la1 pppd[3157]: Using interface ppp0
Feb 7 12:25:11 la1 pppd[3157]: Connect: ppp0 <--> /dev/pts/3
Feb 7 12:25:27 la1 pppd[3157]: Modem hangup
Feb 7 12:25:27 la1 pppd[3157]: Connection terminated.
Feb 7 12:25:27 la1 pppd[3157]: Connect time 0.3 minutes.
Feb 7 12:25:27 la1 pppd[3157]: Sent 50 bytes, received 0 bytes.
Feb 7 12:25:27 la1 pppd[3157]: Exit.
Feb 7 12:25:27 la1 pptpd[3156]: CTRL: Client 190.53.138.114 control connection finished
Feb 7 12:25:30 la1 pptpd[3158]: CTRL: Client 190.53.138.114 control connection started
Feb 7 12:25:31 la1 pptpd[3158]: CTRL: Starting call (launching pppd, opening GRE)
Feb 7 12:25:31 la1 pppd[3159]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
Feb 7 12:25:31 la1 pppd[3159]: pppd 2.4.4 started by root, uid 0
Feb 7 12:25:31 la1 pppd[3159]: Using interface ppp0
Feb 7 12:25:31 la1 pppd[3159]: Connect: ppp0 <--> /dev/pts/3
"
It will repeat in that fashion. I do not see too much in there that provides a clue, it just seems to connect and drop. As I mentioned, I know the router is DD-WRT PPTP capable because it connects to commercial PPTP servers fine. I can't imagine what is different.
Here is my pptpd.conf file:
###############################################################################
# $Id: pptpd.conf,v 1.10 2006/09/04 23:30:57 quozl Exp $
#
# Sample Poptop configuration file /etc/pptpd.conf
#
# Changes are effective when pptpd is restarted.
###############################################################################
# TAG: ppp
# Path to the pppd program, default '/usr/sbin/pppd' on Linux
#
#ppp /usr/sbin/pppd
# TAG: option
# Specifies the location of the PPP options file.
# By default PPP looks in '/etc/ppp/options'
#
option /etc/ppp/options.pptpd
# TAG: debug
# Turns on (more) debugging to syslog
#
debug
# TAG: stimeout
# Specifies timeout (in seconds) on starting ctrl connection
#
# stimeout 10
# TAG: noipparam
# Suppress the passing of the client's IP address to PPP, which is
# done by default otherwise.
#
#noipparam
noipdefault mppe required
# TAG: logwtmp
# Use wtmp(5) to record client connections and disconnections.
#
logwtmp
# TAG: bcrelay <if>
# Turns on broadcast relay to clients from interface <if>
#
#bcrelay eth1
# TAG: delegate
# Delegates the allocation of client IP addresses to pppd.
#
# Without this option, which is the default, pptpd manages the list of
# IP addresses for clients and passes the next free address to pppd.
# With this option, pptpd does not pass an address, and so pppd may use
# radius or chap-secrets to allocate an address.
#
#delegate
# TAG: connections
# Limits the number of client connections that may be accepted.
#
# If pptpd is allocating IP addresses (e.g. delegate is not
# used) then the number of connections is also limited by the
# remoteip option. The default is 100.
#connections 100
# TAG: localip
# TAG: remoteip
# Specifies the local and remote IP address ranges.
#
# These options are ignored if delegate option is set.
#
# Any addresses work as long as the local machine takes care of the
# routing. But if you want to use MS-Windows networking, you should
# use IP addresses out of the LAN address space and use the proxyarp
# option in the pppd options file, or run bcrelay.
#
# You can specify single IP addresses seperated by commas or you can
# specify ranges, or both. For example:
#
# 192.168.0.234,192.168.0.245-249,192.168.0.254
#
# IMPORTANT RESTRICTIONS:
#
# 1. No spaces are permitted between commas or within addresses.
#
# 2. If you give more IP addresses than the value of connections,
# it will start at the beginning of the list and go until it
# gets connections IPs. Others will be ignored.
#
# 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,
# you must type 234-238 if you mean this.
#
# 4. If you give a single localIP, that's ok - all local IPs will
# be set to the given one. You MUST still give at least one remote
# IP for each simultaneous client.
#
# (Recommended)
#localip 192.168.0.1
#remoteip 192.168.0.234-238,192.168.0.245
# or
#localip 192.168.0.234-238,192.168.0.245
#remoteip 192.168.1.234-238,192.168.1.245
localip 172.16.36.1
remoteip 172.16.36.2-254
