MT300A PPTP Connection setup

Hello,

I am trying to setup a PPTP connection on a MT300A on v2.22 firmware.

I have gone into the advanced settings Networks/Interfaces and created a new interface.

I selected DHCP as the protocal, but was not sure which interface to select under “<span style=“color: #404040; font-family: ‘Helvetica Neue’, Helvetica, Arial, sans-serif; font-size: 13px; line-height: 18px; text-align: right;”>Cover the following interface”.</span>

<span style=“color: #404040; font-family: ‘Helvetica Neue’, Helvetica, Arial, sans-serif; font-size: 13px; line-height: 18px; text-align: right;”>After I saved, I was able to install the PPP package, change the protocol to PPTP and then enter the server and username and password.</span>

But the connection does not seem to be working.

Can you provide more detailed directions on setting up a PPTP connection after the package has been installed?

BTW, I am using Purevpn as my service. I tried the Openvpn setup (which worked OK) but the throughput on Openvpn isn’t enough to support the video I am trying to watch.

Thank you.
<div class=“cbi-value-field” style=“line-height: 1.5em; margin-left: 200px;”></div>

This is documented in the OpwnWrt WIKI here

https://wiki.openwrt.org/doc/howto/vpn.client.pptp

Thanks for the info Ranger,

I’ll check that out!

I compiled pptp and l2tp protocol in v2.24 which can be downloaded from GL.iNet download center

Thanks Alzhao,

 

I will download and try it!

Hi Alzhao,

I have downloaded 2.24 and installed it. I don’t see any options for PPTP in the normal GUI. Do you still need to go into advanced settings to setup? If so, could you post directions? Thank you.

Hi Alzhao,

Below is part of my syslog. Not sure if you can help with the configuration of the PPTP. Thanks in advance.

 

Mon Nov 21 11:31:26 2016 daemon.warn pppd[9132]: LCP: timeout sending Config-Requests

Mon Nov 21 11:31:26 2016 daemon.notice pppd[9132]: Connection terminated.

Mon Nov 21 11:31:26 2016 daemon.notice pppd[9132]: Modem hangup

Mon Nov 21 11:31:26 2016 daemon.info pppd[9132]: Exit.

Mon Nov 21 11:31:26 2016 daemon.notice netifd: Interface ‘PPTP’ is now down

Mon Nov 21 11:31:26 2016 daemon.notice netifd: Interface ‘PPTP’ is setting up now

Mon Nov 21 11:31:27 2016 daemon.info pppd[9191]: Plugin pptp.so loaded.

Mon Nov 21 11:31:27 2016 daemon.info pppd[9191]: PPTP plugin version 1.00

Mon Nov 21 11:31:27 2016 daemon.notice pppd[9191]: pppd 2.4.7 started by root, uid 0

Mon Nov 21 11:31:28 2016 daemon.info pppd[9191]: Using interface pptp-PPTP

Mon Nov 21 11:31:28 2016 daemon.notice pppd[9191]: Connect: pptp-PPTP <–> pptp (br1.pointtoserver.com)

Mon Nov 21 11:31:28 2016 kern.info kernel: [ 2313.470000] pptp-PPTP: renamed from ppp0

Mon Nov 21 11:31:34 2016 daemon.info dnsmasq-dhcp[2178]: DHCPINFORM(br-lan) 192.168.8.187 00:16:6f:0c:f9:af

Mon Nov 21 11:31:34 2016 daemon.info dnsmasq-dhcp[2178]: DHCPACK(br-lan) 192.168.8.187 00:16:6f:0c:f9:af T43

Mon Nov 21 11:31:36 2016 daemon.info dnsmasq-dhcp[2178]: DHCPINFORM(br-lan) 192.168.8.187 00:16:6f:0c:f9:af

Mon Nov 21 11:31:36 2016 daemon.info dnsmasq-dhcp[2178]: DHCPACK(br-lan) 192.168.8.187 00:16:6f:0c:f9:af T43

Mon Nov 21 11:31:58 2016 daemon.warn pppd[9191]: LCP: timeout sending Config-Requests

Mon Nov 21 11:31:58 2016 daemon.notice pppd[9191]: Connection terminated.

Mon Nov 21 11:31:58 2016 daemon.notice pppd[9191]: Modem hangup

Mon Nov 21 11:31:58 2016 daemon.info pppd[9191]: Exit.

Mon Nov 21 11:31:58 2016 daemon.notice netifd: Interface ‘PPTP’ is now down

Mon Nov 21 11:31:58 2016 daemon.notice netifd: Interface ‘PPTP’ is setting up now

Mon Nov 21 11:31:58 2016 daemon.info pppd[9413]: Plugin pptp.so loaded.

Mon Nov 21 11:31:58 2016 daemon.info pppd[9413]: PPTP plugin version 1.00

Mon Nov 21 11:31:58 2016 daemon.notice pppd[9413]: pppd 2.4.7 started by root, uid 0

Mon Nov 21 11:32:00 2016 daemon.info pppd[9413]: Using interface pptp-PPTP

Mon Nov 21 11:32:00 2016 kern.info kernel: [ 2345.140000] pptp-PPTP: renamed from ppp0

Mon Nov 21 11:32:00 2016 daemon.notice pppd[9413]: Connect: pptp-PPTP <–> pptp (br1.pointtoserver.com)

@jraymond4321, yes you need to use luci. But I think you have done that.

I didn’t test pptp. so busy.

OP – FWIW, when I’ve used PPTP connection to some commercial providers (including PureVPN) with OpenWrt/LEDE, it wasn’t reliable enough to keep using it. It would work wonders for up to 8 hours on boot and then it would stall. I couldn’t figure out the way to troubleshoot it, so it wouldn’t stall from time to time so I just switched to OpenVPN (it’s slower but harder to crack).

BTW, here’s what’s required for PureVPN PPTP connection to work with a typical router setup on LEDE:

cat << 'EOF' > /etc/ppp/options.pptp

noipdefault

noauth

nobsdcomp

nodeflate

idle 0

maxfail 0

refuse-pap

refuse-eap

refuse-chap

refuse-mschap

EOF

 

uci set network.vpnc=interface

uci set network.vpnc.peerdns=0

uci set network.vpnc.dns=192.168.1.1

uci set network.vpnc.password=********

uci set network.vpnc.proto=pptp

uci set network.vpnc.server=cav.pointtoserver.com

uci set network.vpnc.username=*******

uci set network.vpnc.enabled=1

uci set network.vpnc.pppd_options=debug

uci set network.vpnc.pptpd_options=debug

uci add firewall zone

uci set firewall.@zone[-1]=zone

uci set firewall.@zone[-1].name=vpnc_fw

uci set firewall.@zone[-1].network=vpnc

uci set firewall.@zone[-1].input=REJECT

uci set firewall.@zone[-1].output=ACCEPT

uci set firewall.@zone[-1].forward=REJECT

uci set firewall.@zone[-1].masq=1

uci set firewall.@zone[-1].mtu_fix=1

uci add firewall forwarding

uci set firewall.@forwarding[-1]=forwarding

uci set firewall.@forwarding[-1].src=lan

uci set firewall.@forwarding[-1].dest=vpnc_fw

uci add firewall forwarding

uci set firewall.@forwarding[-1]=forwarding

uci set firewall.@forwarding[-1].src=guest

uci set firewall.@forwarding[-1].dest=vpnc_fw

uci commit


 

 

My two cents: I was easily able to configure a PPTP client on an MT300N running 2.264 firmware; the client connected to a PPTP server (1.28 version of Shibby) running on a Linksys E1200. I am using the connection to enter this post. Minor observation: I connected to the MT300N via wifi from my iMac. Originally, the iMac was connected via ethernet to my main router with a conventional DHCP connection to the internet. That caused pings from the iMac to the Shibby router to fail. Once I unplugged the iMac’s ethernet connection, all went well.