On Tue, 2005-05-17 at 10:54 +1000, Michael Fox wrote: > > > >YourUserNameHERE REMOTE-PPTP-CHAP-HERE 'PPTP-Passwd' > > > >192.168.7.100 > > > > > > > > > > > Doh! somethings are so obvious that you just don't even think that's how > > > it's done. > > > > > > What sort of values go in "remote-pptp-chap-here"? > > > > Password from memory.. > > > > Oops ignore that... typically you put an * in that field... or atleast > thats what I have done, unless of course you want to do peer > authentication, then you can specify the peers hostname or something.
Multiple things utilising ppp can use that chap-secrets file for authentication, so you typically put a descriptor in there that defines that authentication line as unique (which /technically/ is meant to be the machines hostname, but I certainly don't use it like that) - for example, you only want pptpd to authenticate against a few defined passwords, instead of anything in that file (*). That's defined in the ppp options file (whether that's pptpd-options, or the pptp client config file) as 'name'. Right now I'm on a connection that both takes internal wireless connections via a poptop server, and has an external connection via wifi via a encrypted ppp connection (as I can't get ADSL at my current residence, but can link to a client up the road from me who can - ADSL2+ this week hopefully!). My internal usernames/passwords are tagged 'wireless', and the external link has a single password tagged 'extlink'. This is useful because I don't want to be able to authenticate using the internal passwords on the external connection, and vice-versa. R -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
