Date: Wed, 8 Sep 1999 00:55:26 -0000 From: "Doug Young" <dougy@gargoyle.apana.org.au> To: "Pedro A M Vazquez" <vazquez@iqm.unicamp.br> Cc: <freebsd-questions@freebsd.org> Subject: Re: Dialin Setup Message-ID: <059101bef994$d8461460$827e03cb@apana.org.au> References: <055c01bef990$4311cf00$827e03cb@apana.org.au> <19990906232638.A63546@kalypso.iqm.unicamp.br>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the response Pedro :)
> I'm using user-ppp for both dial-ou/dial-in, for the later I've
> installed mgetty and added
>
>
Ahhhhh ..... so at least its possible to stop mgetty spewing out millions
of messages like mine did til I disabled it ..... maybe its like I figured
and it just wants to know its got a modem to keep it company.
I've got a permanent modem connection so I use ppp -ddial, but that
shouldn't be a problem
Looks like much of the following bit was something you wrote specially
as I've never seen anything like most of it in my system.
It appears you have made up a new file "ppp-pap-dialup"
& edited ppp.conf a bit, which raises a few questions
(1) Does your ISP use PAP ??
(2) Is it possible to have manual login for ISP, but PAP for clients ??
(3) Are the references to proxy, proxyall, nbns & ppp-secrets
only for client logins ??
(4) Why no references to modems other than the one on cuaa0 ??
++++++++++++++++++++++++++++++++++++++++++++++
> /AutoPPP/ - - /etc/ppp/ppp-pap-dialup
>
> to login config, where ppp-pap-dialup is
>
> #!/bin/sh
> TTY=`tty`
> IDENT=`basename $TTY`
> logger $TTY
> logger $IDENT
> exec /usr/sbin/ppp -direct $IDENT
>
>
> my ppp.conf has
>
> default:
> set device /dev/cuaa0
> enable proxy
> enable proxyall
> enable pap
> enable dns
> accept pap
> accept dns
> set log Phase Chat Connect TUN
> set timeout 300
> set dns 143.106.51.37 143.106.13.6
> set nbns 143.106.51.9 143.106.51.10
>
> cuaa0:
> set ifaddr 143.106.51.1 143.106.51.254 255.255.255.255
>
>
> and ppp.secret holds the login/password pair
>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > I've been given some stuff called PPP-KIT that apparently was prepared
by
>>a guy "danny@freebsd.org" who appears to come from Melbourne Australia
>>thats supposed to help with setting this stuff up so it works without the
user
> > having to be an expert (see the ReadMe file from the PPP-KIT below).
Since
> > there have been a few changes in the way FreeBSD does things over the
past
> > year or so,
> > and as I understand 3.3 is coming very shortly, I'd appreciate any
comments
> > as to
> >
> > (1) Are there are conflicts using user-ppp & kernel-ppp at same time
> >
> > (2) Is it possible to tell if the PPP-KIT is relevant to present
versions
> >
> > (3) Is there an advantage in using mgetty instead of getty .... and
if so
> > is it simply a matter of replacing references to getty or is
> > there other stuff that needs to be done to use mgetty
> >
> > +++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > PPPKIT - A kit for using FreeBSD as a PPP terminal server.
> >
> > This kit provides all you need to make a FreeBSD box into a PAP login
> > terminal server using the system password file for authentication.
> > Its home is <ftp://ftp.hilink.com.au/pub/FreeBSD/pppkit.tgz>;
> > Comments to <danny@freebsd.org>
> >
> > Useful stuff for everyone:
> >
> > 1. /bin/ppplogin.sh (should go in /usr/local/bin) which is a
> > login shell for ppp users, and a pppd starter for getty.
> > 2. /etc/gettytab - note the 'pp=' field in std.57600 & co.
> > 3. /etc/ppp/ppp.ports - ports and IP addresses for ppplogin.sh
> > 4. /etc/ppp/ppp.users - IP addresses for users with static IP addresses
> > 5. /etc/ppp/ppp.deny - unames of users not allowed to use PPP
> > 6. /etc/ppp/ppp.shells - allowed shells for a ppp session
> >
> > Installation
> > ------------
> >
> > * Make sure you have built a kernel with the appropriate number of ppp
> > interfaces.
> >
> > * copy etc/ppp/ppp.* to /etc/ppp and edit appropriately (see below)
> >
> > * Edit /etc/ppp/options to include your local DNS server IP address,
and
> > the keyword 'proxyarp' if you need it. You need proxyarp if the IP
> > addresses you have assigned to the modem ports really belong on your
> > ethernet as defined by the IP address/netmask of your ethernet
interface.
> >
> > * Install bin/ppplogin.sh into /usr/local/bin/ppplogin.sh. Edit the
> > entries
> > for std.57600, std.115200 and others in /etc/gettytab to have a tag
> > pp=/usr/local/bin/ppplogin.sh. See the supplied gettytab for an
example.
> >
> > * You should read ppplogin.sh to see what it does, and make any changes
you
> > feel you want to.
> >
> > * /etc/ppp/ppp.shells - this file defines which user shells are
acceptable
> > shells for PAP ppp logins using the system password file. It works
in a
> > similar manner to /etc/shells for ftp. If a user's shell is not
listed
> > in /etc/ppp/ppp.shells, pppd access is denied. You'll need to list
at
> > least /usr/local/bin/ppplogin.sh in this file.
> >
> > * /etc/ppp/ppp.deny lists the names of users who are not permitted to
> > use pppd via PAP authentication using the system password file.
> >
> > * If you want users to be able to log in using a login script and
normal
> > Unix Login:/Password: prompts, give them a shell of
> > /usr/local/bin/ppplogin.sh, otherwise, give them a shell of /pppok
and
> > list /pppok in /etc/ppp/ppp.shells. /pppok need not actually exist.
> > /usr/local/bin/ppplogin.sh does not give the user shell access to the
> > system, it simply starts pppd appropriately for the user when they
log
> > in.
> >
> > * /etc/ppp/ppp.users is used by /usr/local/bin/ppplogin.sh to give
static
> > IP addresses to some users when they log in via Login:/Password:, but
> > not when they log in via PAP. To assign a static IP via PAP login,
> > use /etc/ppp/pap-secrets
> >
> > Configuring Clients
> > -------------------
> > Win95
> > * Turn off "Bring up terminal window" switch in "Dial Up Networking".
> > The TCP/IP protocol must be installed. The "Client for Microsoft
> > Networks"
> > must be installed. In Control Panel:Network:TCP/IP:Bindings there
*must*
> > be an entry for "Client for Microsoft Networks" and this must be
checked
> > on.
> > When dialling, enter your username and password at the "Connect To"
info
> > box and dial. Everything should work fine. Under FreeBSD, you might
> > want
> > to run "tail -f /var/log/messages" while you test things.
> > Things work best for 95 if you turn off "Log on to Network",
> > NetBEUI and IPX/SPX
> >
> > Macintosh FreePPP
> > * Choose 'Direct' connection rather than 'Connection script'; enter the
> > username and password information into the appropriate boxes, and PAP
> > login will be performed.
> >
> >
> >
> >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
>
> --
> .sig: license expired, contact your vendor
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?059101bef994$d8461460$827e03cb>