[pptp-server] pptp client and poptop *SUCCESS*

[Terrelle Shaw]

Steve,
Umm to be honest. I just plugged and prayed.. (hahaha) i never saw that
part in pppd manpages..hell i skimmed thru it at best.. (shrug)

Glad it got worked tho.. :-)



On Tue, 15 Feb 2000, Cowles, Steve wrote:

> Terrelle,
> 
> Your post worked!!! Thank you. I can sleep now. But I must admit that the
> man pages on pppd are a little confusing... to say the least. From the man
> pages on the "name" parameter
> 
>        name name
>               Set the name of the local system for authentication
>               purposes to name.  This  is  a  privileged  option.
>               With  this  option,  pppd  will  use  lines  in the
>               secrets files which have name as the  second  field
>               when  looking for a secret to use in authenticating
>               the peer.  In addition, unless overridden with  the
>               user  option, name will be used as the name to send
>               to the peer when authenticating the local system to
>               the  peer.   (Note  that  pppd  does not append the
>               domain name to name.)
> 
> I guess what threw me, was the "local system" part of the first sentence.
> But yet in the options file we (you) are specifying the remote system which
> is then matched in the chap-secrets file. This corresponds to the second
> sentence. Kind of confusing. I was using the "remotename" parameter. <groan>
> 
> Anyway, after a little testing, I came up with the following options file
> which is a little more universal.
> 
> Thanks again (to everyone) who replied to this post.
> Steve Cowles
> 
> ================================
> /etc/ppp/options on client side
> lock
> auth
> +chap
> +chapms
> +chapms-v2
> mppe-40
> mppe-128
> mppe-stateless
> 
> /etc/ppp/chap-secrets
> scowles  * password *
> COWLES\\scowles  * password *
> 
> And then invoke pptp as follows
> pptp enterprise name enterpise user COWLES\\scowles
>   or
> pptp enterprise name enterpise user scowles
> 
> Basically, I'm specifying the name/user paramerters on the pptp command
> line. The server side options file I left alone. It is setup per the PopTop
> WEB Howto. Before attempting the pptp client nightmare, I was using my
> Laptop with NT workstation (SP6) so I needed the MS Domain name in my
> chap-secrets file. Either one of the above examples worked.
> 
> 
> -----Original Message-----
> From: Terrelle Shaw [mailto:hshaw at xytek.org]
> Sent: Tuesday, February 15, 2000 7:58 AM
> To: Stephen Tan
> Cc: 'pptp-server at lists.schulte.org'
> Subject: Re: [pptp-server] pptp client and poptop *SUCCESS*
> 
> 
> Hello all!
>     After searching through archives and playing around with my settings. I
> have FINALLY gotten pptp client ( 1.0.2) working. My setup.
> 
> PPTP Client:
> linux 2.2.14
> PPPD(2.3.10) #module
> ppp-driver in kernel ( 2.3.7) <--- this is default with Slackware 7.0
> pptp-client 1.0.2
> Other modules: slhc,ppp_deflate,bsd_comp
>     This client sits behind a linux masq/firewall which is running kernel
> 2.2.13 ( with ipv4 tunneling and gre compiled in)
> 
> PPTP Server:
> This server doubles as the VPN server and router/firewall(linux)
> Kernel 2.3.13
> Modules(ppp,slhc,ppp_deflate,ppp_mppe,bsd_comp)
> pptp-server(pptpd-1.0.0)
> pppd(2.3.10)
> 
> Resources:
> Here is my options file on the client side.. not much there:
> 
> name name_of_vpnserver
> user myusername
> password mypassword
> noauth
> lock
> defaultroute
> ( i have to setup a gateway route for the ppp0 interface when it gets
> established, i think its because of the last line of my options.. i'll work
> it out later)
> 
> Options file on the server:
> name name_of_vpnserver
> debug
> ms-dns 10.0.0.1
> ms-wins 10.0.0.106
> netmask 255.255.255.0
> proxyarp
> nodeflate
> bsdcomp 15,15
> auth
> +chap
> lock
> mppe-40
> #mpp-stateless
> +chapms
> +chapms-v2
> defaultroute
> 
> Here is my chap-secrets for the client:
> # Secrets for authentication using CHAP
> # client        server  secret                  IP addresses
> hshaw           *       mysecret               *
> 
> My chap-secrets on the server:
> # Secrets for authentication using CHAP
> # client        server  secret                  IP addresses
> hshaw           *       mysecret              *
> 
> The problem i was having about a week ago was that i hadn't started the
> modules first before trying to establish a connection.
> *duh!*
> 
> So right now i'm connected to my office Lan and my home lan via the pptp
> connection thru my ADSL modem.
> 
> I hope this helps someone in the future. I would gladly help anyone who
> wants to get there linux box setup with a similar setup.
> 
> Terrelle
> 
> 
> 
> 
> Stephen Tan wrote:
> {snip}
> 
> >
> > _______________________________________________
> > pptp-server maillist  -  pptp-server at lists.schulte.org
> > http://lists.schulte.org/mailman/listinfo/pptp-server
> > List services provided by www.schulte.org!
> 
> 
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> List services provided by www.schulte.org!
> 
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> List services provided by www.schulte.org!
>