Re: pptp-based vpn
Quoting martin McCormick (martin.m@suddenlink.net):
> > If I'm reading this correctly, you've stated that the connection must
> > use MPPE (because of the 'require-mppe-128' command in
> > /etc/ppp/peers/ufreevpn), but the remote end has replied that MPPE is
> > not available. Because of this, pppd terminated the connection.
> >
> > I would suggest confirming the settings with your VPN provider.
> > Either you don't need MPPE, or they need to turn on support for it at
> > their end.
>
> First, thank you for the time in reading all that output.
>
> I re-read the instructions on the VPN provider's site and
> they do require that to be enabled.
>
> I think the mixup may be on what I am sending as
> credentials. Since the web site tells all callers to use the
> following credentials, I will quote them as anybody can go there
> and see the same things so I am not breaking any confidences:
>
> PPTP Server: ukvpn.ufreevpn.com
> Username: ufreevpn.com
> Password: free
>
> The important line in /etc/ppp/chap-secrets then reads:
>
> ufreevpn.com ukvpn.ufreevpn.com free
I think there's a fourth field missing there.
Anyway, what I just did is: install pptp-linux (which pulls in ppp)
and typed:
# pptpsetup --create work --server ukvpn.ufreevpn.com --username ufreevpn.com --password free --encrypt --start
It replied:
Using interface ppp0
Connect: ppp0 <--> /dev/pts/22
CHAP authentication succeeded
MPPE 128-bit stateless compression enabled
local IP address 10.162.0.129
remote IP address 10.162.0.1
ip r changed from:
default via 192.168.1.1 dev wlan0
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.15
to:
default via 192.168.1.1 dev wlan0
77.92.72.92 via 192.168.1.1 dev wlan0 src 192.168.1.15
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.15
I then added a route:
# route add -net xxx.0.0.0/8 ppp0
and now, any website whose address starts with xxx. brings up the
UFreeVPN.COM Service from UK
I Agree to use the Free VPN Service
page. I haven't tried to get beyond that, mainly because I believe I
have to open up a port on the router, which I'll try later.
chap-secrets was looked after automatically. The route is the only
thing I touched configurationwise. See if this approach works for you.
Cheers,
David.
Reply to: