r19327 breaks PPTP server

[tatsuya46]

Build(s) Affected: r19327 Unit(s) Affected: WNDR3700 v1, DIR-825 B1, (all?)

PPTP server simply does not work, its like its turned off the connecting client just gets an immediate disconnect error. Also the MTU/MRU settings do not stay on the GUI, enter in 1450 and apply settings and when the page reloads they are empty again.

[Paul]

Same problem on TP-LINK 1043ND v 1.8

[Paul]

Same problem on TP-LINK 1043ND v 1.8

[facsi]

This is broken since 18777.

[tatsuya46]

PPTP server was working in r18777 with WNDR3700 v1 & DIR-825 B1 (a reboot cleared up the MTU issue usually).

[facsi]

It only worked with no encryption and only on pcs. smartphones didnt work for me.

[tatsuya46]

Remains with r19342.

[nikboom]

Yes it stil not working in r19342. Unable to connct through pc or any other device even with encryption off on 1043nd Plz can this be fixed lossing a lot becoz of this

[mblmblmbl]

Is there an older build where PPTP worked ? Which one ? I need PPTP to connect safely from my smart phone, fixing this would be great !

[tatsuya46]

It was last working with r18777 for me on WNDR3700 v1. With all clients.

[mblmblmbl]

@tatsuya46: Thanks very much for telling me! I just flashed my WNDR3700v2 with r18777 and I can connect via VPN with my iPhone using PPTP and CHAP-Secrets for encryption. I nevertheless hope, PPTP will be fixed in upcoming releases !

[paul_damian]

TP-LINK 1043ND v 1.8, build 19342. PPTP Server still not working...

[dalmiroy2k]

I have the same problem with Linksys E3000 and DD-WRT v24-sp2 (06/08/12) big - build 19342, using iOS 5.11 Ipod Touch as client. Here's the log:

06-23-2012 20:10:43 Daemon.Info 192.168.0.1 Jun 23 20:10:23 pptpd[11241]: CTRL: Client 192.168.0.22 control connection finished 06-23-2012 20:10:43 Daemon.Debug 192.168.0.1 Jun 23 20:10:23 pptpd[11241]: CTRL: Reaping child PPP[11242] 06-23-2012 20:10:43 Daemon.Error 192.168.0.1 Jun 23 20:10:23 pptpd[11241]: CTRL: PTY read or GRE write failed (pty,gre)=(8,9) 06-23-2012 20:10:43 Daemon.Error 192.168.0.1 Jun 23 20:10:23 pptpd[11241]: GRE: read(fd=8,buffer=41fe54,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs 06-23-2012 20:10:43 Daemon.Info 192.168.0.1 Jun 23 20:10:22 pptpd[11241]: CTRL: Starting call (launching pppd, opening GRE) 06-23-2012 20:10:43 Daemon.Info 192.168.0.1 Jun 23 20:10:22 pptpd[11241]: CTRL: Client 192.168.0.22 control connection started

[wesli]

I can also confirm it. PPTP not working on DIR-825 B2 with r19342

[RalphMalph]

Also confirmed. pptp on 1043ND with r19342 is a no go. Please fix.

[darkvoid]

The error occurs because of an unknown option present in /tmp/options.pptpd.

The line in question is:

connections 64

A quick fix is including the following in your startup script on the Administration -> Commands tab.

sed -i '/connections/d' /tmp/pptpd/options.pptpd

This will delete the "connections" line from options.pptpd when your router starts and everything works fine then.

[RalphMalph]

Didnt work for me. Anyone else ?? Maybe a quick comment on my setup , please ?

• Router : 192.168.1.1
• PPTP Server IP: 192.168.1.2
• Client IP's : 192.168.1.200-220 (not in dhcp-range)
• Chap : user * password *
• NAT port forward : 1723 to 192.168.1.2
• NAT port forward : 1792 to 192.168.1.2

Replying to darkvoid:

The error occurs because of an unknown option present in /tmp/options.pptpd.

The line in question is:

connections 64

A quick fix is including the following in your startup script on the Administration -> Commands tab.

sed -i '/connections/d' /tmp/pptpd/options.pptpd

This will delete the "connections" line from options.pptpd when your router starts and everything works fine then.

[dalmiroy2k]

That fix didn't work either on my setup.

[wesli]

That fix work very well on my dlink dir-825.

Thank you very much darkvoid!

@RalphMalph? My setup is very close to yours:

• Router: 192.168.1.1
• PPTP Server IP: 192.168.1.100
• Client IP's: 192.168.1.101-110
• Chap: user * password *
• No NAT port forwarding!